What the docs MCP server does
The MCP server lets your assistant search these docs and read pages on demand. It’s read-only documentation knowledge—it can’t access your account, keys, or funds, and it can’t move assets. To take actions, your integration calls the REST API with your own scoped keys.Opening
https://docs.anchorage.com/authed/mcp directly in a browser returns 401 Unauthorized. That endpoint is not a web page — it is an MCP transport, and authentication is browser-based OAuth triggered by your MCP client, not a token you paste in.Add the URL to an MCP client that supports OAuth (Claude Desktop, Claude Code, Cursor, VS Code, ChatGPT). When the client first connects, it opens a browser window to sign in with your Anchorage Digital account. There are no client IDs, secrets, or long-lived tokens to configure. If your client doesn’t open a sign-in window, it doesn’t support OAuth — use https://docs.anchorage.com/mcp instead.Quick install
The fastest path is the one-line installer, which detects your installed tools:Set up by tool
Claude Code
Claude Desktop and Claude web
1
Open connector settings
In Settings, select Connectors, then select Add custom connector.
2
Add the server
Enter a name and the URL
https://docs.anchorage.com/mcp, then save.Cursor
Add the server tomcp.json:
VS Code (GitHub Copilot)
Add the server to.vscode/mcp.json:
ChatGPT and other clients
In any client that supports custom MCP connectors, add a new connector with the URLhttps://docs.anchorage.com/mcp. To include documentation restricted to your account, use https://docs.anchorage.com/authed/mcp and sign in when prompted.
The docs MCP server provides documentation only. It never has access to your API keys or the ability to move assets. See AI security and guardrails.