MCP server

These docs are served over the Model Context Protocol so an agent can search and read them as tools instead of scraping HTML.

https://docs.flambe.dev/api/mcp

Tools

Tool	What it does
`search`	Full-text search across every page. Returns matching sections with their URLs.
`list_pages`	Lists every page with its title and description — a cheap way to orient.
`get_page`	Fetches one page's full Markdown.

They are backed by the same search index and Markdown the website renders, so there is no second copy that can drift.

Connecting

Claude Code

claude mcp add --transport http flambe-docs https://docs.flambe.dev/api/mcp

Claude Desktop and other clients

Add it to the client's MCP configuration:

config.json

{
  "mcpServers": {
    "flambe-docs": {
      "type": "http",
      "url": "https://docs.flambe.dev/api/mcp"
    }
  }
}

Cursor, Windsurf, and Zed

All three read the same shape — point an HTTP MCP server at the URL above. No API key is required; the docs are public.

Verifying it works

curl -sS https://docs.flambe.dev/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

You should get back the three tools above.

When not to use it

The MCP server is for reading the documentation. It does not call the Flambe API — there is no create_recipe tool here, and it holds no credentials.

To have an agent actually use the API, give it the OpenAPI spec and a token. The spec is generated from the same source as this reference and is verified against the running server on every build, so it is safe to generate a client from.