Documentation MCP server
Search and read this documentation from your AI client. Public, read-only, no credential.
This portal runs a small MCP server over its own pages. Point an AI client at it and the assistant can search the documentation and read a page, instead of loading everything or guessing a URL.
It is not the Digitalyser.io product server. It carries no project data, takes no credential and cannot change anything. To act on a project, use the product MCP server.
The endpoint
https://developers.digitalyser.io/mcpStreamable HTTP, no sign-in. Add it to Claude Code with:
claude mcp add --transport http digitalyser-docs https://developers.digitalyser.io/mcpOther clients: add a remote MCP server with that URL.
What the assistant sees
Two tools, both read-only:
| Tool | Input | Returns |
|---|---|---|
search_docs | query (2–200 characters), limit (1–10, default 5) | The best-matching pages, each with its title, its path and a short snippet |
get_page | path, as returned by search_docs — for example /docs/guides/limits | The page as markdown, exactly as served at /llms.mdx/…/content.md |
A malformed call — a limit of 11, a path the server does not know — comes back as a tool error
that names the field. It is never silently corrected.
Same content as the site
The server reads the pages the site publishes, from the same build. A page you can read here is a page the assistant reads there, and the build refuses to publish if the two differ.
If you would rather load everything at once, /llms-full.txt holds the whole
documentation in one file, and /llms.txt is its index.
Good to know
- Rate limit. The endpoint limits each client address. A refused call returns
429with aRetry-Afterheader; wait for it, as for any other rate limit. - Origin. Requests from a web page on another origin are refused with
403. Command-line and desktop clients send noOriginand are not affected. - No sessions. Every call stands alone, so there is nothing to keep alive and nothing to resume.