A public MCP server for Tandem docs.
Connect this remote server in your MCP client to give agents direct access to Tandem documentation. It helps them find install guides, SDK docs, workflow docs, and headless guidance without guessing.
This page exists for discovery and connection. Agents use it to read Tandem docs. Humans use it to connect the remote MCP endpoint in their client.
Remote MCP endpoint
Connect your client here to give agents live access to Tandem authority-layer docs over HTTPS.
Metadata
Use this manifest when a client or registry wants discovery metadata first.
Freshness tools
Use these when you want cache, warmup, and refresh checks for docs freshness before relying on agent answers.
What this MCP is for
It gives agents a direct path into Tandem docs for runtime authority, scoped tools, memory, approvals, deployment, and audit trails, while giving humans a clear endpoint and manifest.
For agents
Give agents direct access to Tandem docs so they stay grounded in published guidance for tools, memory, approvals, deployment, and audit evidence.
For humans
Connect the remote endpoint in your MCP client when an agent is helping set up Tandem locally, hosted, or inside customer infrastructure.
For discovery
The endpoint and manifest are public so crawlers, agents, and operators can discover Tandem authority-layer docs cleanly.
How to connect this MCP
This is a remote MCP server. Add the public endpoint to your client and let the client connect over HTTPS.
1. Add the remote endpoint
In an MCP client that supports remote servers, add the remote URL as the server URL.
2. Use the manifest when requested
If your client asks for discovery metadata first, use the manifest URL.
3. Confirm the connection
After connecting, list tools or run a small docs search to make sure the server is reachable.
Connection URLs
Generic client shape
Clients use different config formats, but a remote MCP connection usually looks like this.
{
"mcpServers": {
"tandem-docs": {
"url": "https://tandem.ac/mcp"
}
}
}Quick check
If you want a fast confidence check, try these exact requests and make sure they return JSON.
curl https://tandem.ac/mcp
curl https://tandem.ac/.well-known/mcp/server.json
curl 'https://tandem.ac/mcp/docs/search?q=python%20sdk&limit=3'Why this page exists
Agents and operators should be able to discover the remote MCP, understand what it is for, and connect it without having to infer the setup from a hidden API route.
Use the docs server to find setup, first run, engine command, and deployment-mode guidance.
Covers the Python SDK and TypeScript SDK with workflow and runtime-authority guidance.
Connect workflow docs, headless deployment, protocol references, approval patterns, and audit/evidence guidance.
Helpful guide endpoints
These endpoints are useful when an agent needs a focused path instead of broad search.
Find Tandem install docs
Point agents at setup and first-run docs for local, headless, hosted, and customer-infrastructure deployment paths.
Find Python SDK docs
Use the Python SDK guide for integrations, automation patterns, and engine prerequisites.
Find TypeScript SDK docs
Use the TypeScript SDK guide for integration details and related workflow references.
Find authority-layer workflow docs
Use the workflow guide when agents need scoped execution, approvals, artifacts, and orchestration references.
Find headless runtime docs
Use the headless guide for service deployment, protocol details, API usage, and runtime operation.
Example HTTP calls
You can inspect the remote server directly over HTTP before connecting it in a client.
Repo docs
The repo also includes implementation, usage, and publishing notes for the Tandem Docs MCP.
Return paths
Go back to the main Tandem product page or published docs when you are done connecting the server.