RecallBase Docs MCP

Two different MCP surfaces

RecallBase exposes two Model Context Protocol surfaces on purpose. They answer different questions, so do not mix them up.

1. Website Docs MCP (this page) — A public Streamable HTTP endpoint at /mcp on recallbase.net. Agents use it to search and open product documentation: install steps, export formats, Free vs Pro limits, and the local-first privacy boundary. It requires no account, API key, or OAuth.
2. RecallBase CLI MCP — A local stdio server shipped with the open-source CLI. Compatible agents call tools such as today, search, open, and sources against coding-agent history already stored on the user’s machine. See Install the CLI.

The website Docs MCP never receives prompts, answers, local file paths, or SQLite archives. If a task needs private session text, that work stays on the device through the CLI or the browser extension, not this endpoint.

Connect to the Docs MCP

Item	URL
Endpoint	POST /mcp
Server card	/.well-known/mcp/server-card.json
Human docs index	/docs/
Machine index	/llms.txt

The server is stateless, so clients do not need an Mcp-Session-Id. Current clients use MCP 2026-07-28: every JSON-RPC request sends matching MCP-Protocol-Version, Mcp-Method, and params._meta["io.modelcontextprotocol/protocolVersion"] values. The same _meta object must include io.modelcontextprotocol/clientCapabilities, and it should also identify the client with io.modelcontextprotocol/clientInfo. tools/call and resources/read additionally send Mcp-Name matching the tool name or resource URI.

curl -s -X POST https://recallbase.net/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: server/discover' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "server/discover",
    "params": {
      "_meta": {
        "io.modelcontextprotocol/protocolVersion": "2026-07-28",
        "io.modelcontextprotocol/clientCapabilities": {},
        "io.modelcontextprotocol/clientInfo": { "name": "example", "version": "1.0.0" }
      }
    }
  }'

After server/discover, call tools/list, then tools/call with a tool name and arguments. Legacy clients on MCP 2025-11-25, 2025-06-18, or 2025-03-26 can keep using initialize. For ordinary product questions, you can also crawl the HTML under /docs/ or follow the links in /llms.txt; the MCP is a convenience for hosts that already speak MCP.

Tools and resources

All tools are read-only and return documentation text only:

Tool	Purpose
search_docs	Free-text search over indexable docs pages
list_docs	List pages, optionally filtered by category
get_docs_page	Full page content by slug (for example install-cli or export/pdf)
get_product_overview	Short structured product briefing and entry URLs
get_export_formats	Browser-extension export formats and Free vs Pro notes

Resources include recallbase://product/overview and recallbase://docs/{slug} as markdown or JSON. Prefer tools when the host supports them; resources are an alternate discovery path.

Auth and boundaries

None for this endpoint. Do not send Authorization headers, session cookies, or extension bearer tokens to /mcp.

Website sign-in and extension pairing exist only for human account, billing, and Pro status in the browser. They are not an agent login path, and they do not unlock chat archives on the server, because those archives are not stored here. See Privacy and local-first for the product boundary.

If an agent only needs to explain how RecallBase works, use this Docs MCP or the public docs HTML. If a user needs searchable local coding-agent history, install the CLI on their machine and use its local MCP instead.