Remote connector (OAuth)
One URL — https://api.buildonto.dev/mcp — and a sign-in with your Onto account. No key to paste, nothing to install.
What connecting does
[02]In your client's connector settings — or with one command in Claude Code and Codex.
Its first call is refused with a
401pointing atapi.buildonto.dev's own OAuth metadata. The client registers itself there.You sign in to your Onto account on
app.buildonto.devand allow the client. That's the only step that needs you.The client swaps a one-time code (PKCE, S256) for an access token that lasts an hour and a refresh token that lasts 30 days, and renews them itself.
The same six tools as the local server, calling the same endpoints.
Connect your client
[03]Claude, Claude Code, Cursor, Codex and ChatGPT all connect by URL. Pick yours for the exact place it goes:
$ claude mcp add --scope user --transport http onto https://api.buildonto.dev/mcp- Run it in a terminal. Claude Code asks you to approve Onto on first use.
- Then ask Claude Code to “read example.com with onto”.
How sign-in works
[04]https://api.buildonto.dev — Onto's own; no third party/authorize, /token, /register (dynamic client registration), /revokeonto:readonto_sk_ API key as the Bearer tokenTest it with the Inspector
[05]To watch the whole flow — the 401, the sign-in, the tools — run the official MCP Inspector, set the transport to Streamable HTTP, paste the URL and connect:
npx @modelcontextprotocol/inspectorThen list the tools and call read_url with { "url": "https://stripe.com/pricing" }.
Remote or local
[06]onto_sk_ key in ONTO_API_KEY