Tandem Docs MCP Server for Claude

Overview

Tandem Docs MCP (ac.tandem/docs-mcp) is a public remote Model Context Protocol server that exposes published Tandem documentation to MCP clients. It helps agents and operators find install guides, SDK references, workflow docs, and headless deployment guidance for the Tandem governed runtime without guessing URLs.

Source and runtime context live in frumu-ai/tandem. Connection docs and manifest metadata are at tandem.ac/docs-mcp.

Features

• Search the published Tandem docs index with audience and version hints.
• Fetch and normalize individual docs pages by path or URL.
• Recommend starting paths for desktop users, server admins, and developers.
• Suggest next docs to read after a current page, optionally biased toward a goal.
• Answer how-to questions by synthesizing relevant published docs.
• Return structured learning guides for install-engine, Python SDK, TypeScript SDK, workflows, and headless deploy.
• Inspect, refresh, warm, invalidate, and compare docs cache state for freshness checks.

Validated tools on the live endpoint include search_docs, get_doc, get_start_path, recommend_next_docs, answer_how_to, get_tandem_guide, warmup_docs_cache, get_docs_cache_status, refresh_docs_index, refresh_doc_page, invalidate_docs_cache, compare_docs_index_refresh, and compare_doc_page_refresh.

Use Cases

• Ask Claude how to install the Tandem engine locally or headlessly before editing config.
• Pull the Python or TypeScript SDK docs path when wiring automations.
• Get a guided next-read list after finishing the Tandem quickstart.
• Verify docs freshness with cache status tools before trusting agent answers.
• Help an external agent configure Tandem MCP connectors using published authority-layer guidance.

Installation

Claude (Connectors)

1. Open Settings → Connectors and add a custom remote MCP server.
2. Enter the MCP URL: https://tandem.ac/mcp.
3. Enable the connector; no API key is required for the public docs server.
4. Run a small docs search to confirm connectivity.

Claude Code

claude mcp add --transport http tandem-docs https://tandem.ac/mcp
claude mcp list

Other MCP clients

Add a remote streamable HTTP connector pointing at the Tandem docs endpoint. Discovery manifest: https://tandem.ac/.well-known/mcp/server.json.

Configuration

{
  "mcpServers": {
    "tandem-docs": {
      "url": "https://tandem.ac/mcp",
      "type": "http"
    }
  }
}

The public docs MCP server requires no authentication headers.

Examples

Install guidance

Use Tandem Docs MCP to find the best starting docs path for a developer installing the headless engine.

SDK lookup

Search Tandem docs for Python SDK workflow examples and fetch the most relevant page.

Freshness check

Check the Tandem docs cache status, then refresh the install-engine guide if needed.

Security

• Docs MCP is read-oriented, but cache-management tools can change server-side cache state.
• Treat returned documentation as guidance, not an authorization decision for production agent actions.
• Avoid submitting internal URLs, credentials, or customer data in doc search queries.

Troubleshooting

Connector timeout

Retry after a few seconds; the remote service may be cold-starting or refreshing its docs index.

Stale answers

Use get_docs_cache_status, refresh_docs_index, or refresh_doc_page before relying on older cached content.

Version mismatch

Pass an engine_version hint or a specific docs_ref when your installed Tandem version differs from stable docs.

Unknown doc path

Start with search_docs or get_start_path instead of guessing paths manually.

Duplicate Check

No existing Tandem Docs MCP or ac.tandem/docs-mcp entry was found in content/mcp/. This differs from generic documentation MCP servers because it targets Tandem's governed runtime docs—authority projection, approvals, memory, MCP connectors, and audit evidence—not general web search.