Any MCP client can read these docs directly. The docs server needs no account and no token, serves only the pages published on this site, and changes nothing.
Connect
The server speaks Streamable HTTP at one address:
https://api.overlane.app/docs-mcpIn a client that takes a URL, add it as a remote server with no authentication. With the Claude Code CLI:
claude mcp add --transport http overlane-docs https://api.overlane.app/docs-mcpTools
| Tool | Input | Returns |
|---|---|---|
search_docs |
query, optional limit (1 to 20, default 8) |
The best matching pages: path, URL, title, description and an excerpt |
read_page |
path, for example /cli/task-start/ |
The text of one page |
list_pages |
optional section (the first part of a path, such as cli), offset, limit |
Page paths, titles and descriptions, in order |
All three are read-only. Search is deterministic: it scores a page by how many words of the question appear in its title, description and text, and breaks ties by path, so the same question gives the same answer.
{ "name": "search_docs", "arguments": { "query": "how do I verify a webhook signature", "limit": 3 } }What the text is
Every answer carries a notice that page text is documentation to read. A client treats it as data and never follows instructions found in it. A page marked awaitingReview is written by an agent and not yet approved by a person.
Limits
Calls are limited per address, 120 a minute. A call over the limit is refused with status 429 and a Retry-After header, in the same error shape as the rest of the API. Browser clients can connect: the server answers cross-origin requests.
The MCP server agents use for their own project (tasks, memory, guardrails) is separate and needs a sign-in.