Use ReadyView from Claude and other MCP clients — under your own ReadyView role.

Server URL

https://api.readylinks.io/mcp

Claude (claude.ai / Claude Desktop)

Settings → Connectors → Add custom connector. Name it ReadyView, paste the server URL above, keep Authentication: Always required, and for OAuth client choose Use Anthropic's hosted client metadata (recommended; automatic registration works too). Leave managed authorization off and add no headers. You will be asked to sign in with your ReadyView account, choose read or read-and-write access, and approve.

Claude Code

claude mcp add --transport http readyview https://api.readylinks.io/mcp

Then run /mcp inside Claude Code to authenticate in the browser.

Scripts and other clients (API key)

Send the public API's credential on every request instead of running OAuth:

Authorization: Basic base64(<organization_id>:<api_key>)

Both values are on your ReadyView account page. API-key connections have full (read and write) scope, limited by your role like every API call.

What it can do

Every tool the ReadyView Network Assistant has: list sites and devices, read switch configuration and ports, telemetry, access points, floor plans, templates, work items; and — with write access — change ports and VLANs, configure wireless, claim and unclaim devices, reboot, upgrade firmware, manage members and templates, run CLI commands, capture packets. Changes preview first and act only when the plan is confirmed; destructive ones (deletes, factory resets, configuration CLI commands) are, by default, made from ReadyView's Network Assistant.

It also knows what the in-app assistant knows: get_readyview_guide is the assistant's field guide (the hardware, G.hn and fiber diagnosis, CLI, safe changes) and get_organization_briefing returns your organization's saved notes and playbooks. search_cli_guides and search_readylinks_docs answer command and wiring questions from the manuals and readylinks.io/docs.

Access and revocation

A connection is tied to one user and a scope (read-only, or read and write). It can work in every organization your account can: the organizations you belong to, or for ReadyLinks staff every organization. When that is more than one, you name the organization in your requests — find_organizations searches them (favorites and memberships first, with site, switch and member counts to tell duplicates apart) and every organization-scoped tool takes an organization id or exact name — and every result states the organization it came from. The connection never reaches further than your own account does, that is re-checked on every call (leaving an organization removes it within a minute), and it stops working the moment your API key is rotated. Revoke a connection with DELETE https://api.readylinks.io/mcp/oauth/connections/<id> (list them at GET https://api.readylinks.io/mcp/oauth/connections) or from the client.

Discovery

https://api.readylinks.io/.well-known/oauth-protected-resource/mcp
https://api.readylinks.io/.well-known/oauth-authorization-server