MCP server
Give any MCP client six Onto tools — read, score, map, batch and extract. Connect by URL with an OAuth sign-in, or run it locally with npx.
What a tool call does
[02]Your agent has no reader of its own for the page — so it looks at the tools it has.
One of Onto's six, with arguments — here
read_urland the URL.Over the connector URL, signed in with OAuth — or through the local
npxserver with youronto_sk_key.Each tool calls its
/v1endpoint, so the credits are the API's, charged once.The agent reads the clean page and answers from it.
Install it
[03]$ 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”.
Step-by-step for every client is on Set up your client.
Two ways to connect
[04]https://api.buildonto.dev/mcpnpx -y @ontosdk/mcp@latestonto_sk_ key in ONTO_API_KEYBoth expose the same six tools and bill the same account. Details on the remote connector and the local server's configuration.
The six tools
[05]read_urlThe page as Markdown, with its size, reduction and cache state/v1/read1read_and_scoreMarkdown plus the score, grade and hallucination risk/v1/read-and-score1score_urlJust the score, and why — penalties and recommendations/v1/scorefreeextract_dataThe JSON-LD, OpenGraph and meta the page declares/v1/extract1map_siteA site's URLs, from its sitemap or its start page's links/v1/map1batchUp to 50 URLs — or a site — read, scored or extracted/v1/batch1 per URLInputs and outputs for each are on the Tools reference.
MCP or the API
[06]Same endpoints, same credits, same errors — MCP is a transport. Use it when an agent you don't write should read the web; call the Read API yourself when you control the code and want retries, caching and batching on your terms.