fonto-docs-mcp

An MCP server that makes the Fonto XML documentation accessible to AI tools like Claude Code, Cursor, and Claude Desktop. Live at fonto-docs.elliat.nl.

The Fonto docs are rendered by a JavaScript SPA, which makes them impossible for AI to read directly. This server fetches the underlying XML and converts it to clean, readable Markdown on demand.

What is MCP?

MCP (Model Context Protocol) is a standard way to give AI assistants access to external tools. Once you connect this server to your AI tool, it gains access to these tools and resources:

Tool	What it does
`search_fonto_docs`	Search by keyword — returns matching pages with titles, descriptions, and slugs
`get_fonto_page`	Fetch the full content of a page by its slug
`list_pages`	List all pages matching a keyword, with full section hierarchy — useful for discovery

Resource	What it contains
`fonto://catalog`	All ~2000 pages with real titles, product grouping, and ancestry paths

You can then ask things like "How does addDocumentChangeCallback work?" and the AI will look it up in the live Fonto docs.

Connect to your AI tool

The server is already running at https://fonto-docs.elliat.nl/mcp — you just need to point your tool at it.

Claude Code (CLI)

claude mcp add --transport http fonto-docs https://fonto-docs.elliat.nl/mcp

Cursor

Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json globally):

{
  "mcpServers": {
    "fonto-docs": {
      "type": "http",
      "url": "https://fonto-docs.elliat.nl/mcp"
    }
  }
}

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "fonto-docs": {
      "type": "http",
      "url": "https://fonto-docs.elliat.nl/mcp"
    }
  }
}

Usage examples

Once connected, ask your AI assistant:

"Search the Fonto docs for documentsManager"
"Get the Fonto docs page for clearundostackfordocument-f0187fade723"
"How does addDocumentChangeCallback work according to the Fonto docs?"
"List all pages in the configure section"
"What upgrade guides are available?"

HTTP API

The server also exposes a plain HTTP API if you want to use it without MCP:

GET /search?q={query} — search pages by keyword
GET /page/{slug} — fetch a page as Markdown
GET /catalog — full page catalog grouped by section; add ?section={keyword} to filter

How it works

The Fonto documentation site stores its content as XML at predictable URLs under /static/xml/. This server fetches those XML files directly and converts them to Markdown, bypassing the JavaScript rendering. Page content is never cached — every get_fonto_page call goes to documentation.fontoxml.com live. The page catalog (used by list_pages and fonto://catalog) is fetched once from the Fonto search index on first use and held in memory for the lifetime of the process.

Self-hosting

npm install
npm start        # runs on port 8080 by default
PORT=3000 npm start

Contributing

PRs welcome. The XML-to-Markdown conversion in src/fonto.js handles two formats:

DITA guide pages — <topic>, <body>, <section> structure
API reference pages — custom <type>, <members>, <description> structure

If you find pages that don't convert well, open an issue with the slug.

License

MIT

Fonto Docs