Docs Mcp
Give your agent live, searchable Tandem documentation—install guides, SDKs, workflows, and setup steps—so you stop context-switching to tandem.ac while wiring agents.
Overview
ac.tandem/docs-mcp is a MCP server for the Build phase that surfaces Tandem install guides, SDKs, workflows, and agent setup documentation to your coding agent.
What is this MCP server?
- Remote MCP server scoped to official Tandem documentation and install guides
- Covers SDKs, workflows, and agent setup help for the Tandem platform
- Published from the frumu-ai/tandem monorepo with CI and registry publish pipelines
- npm @frumu/tandem-client and PyPI tandem-client companions for app code
- Mixed MIT/Apache-2.0 plus BUSL-1.1 licensing—check docs/LICENSING.md before production use
- Companion clients: @frumu/tandem-client (npm) and tandem-client (PyPI)
- Source repository: github.com/frumu-ai/tandem
Community signal: 107 GitHub stars.
What problem does it solve?
Builders integrating Tandem lose flow constantly opening tandem.ac and guessing which install or SDK page matches their current agent task.
Who is it for?
First-time Tandem setup, SDK integration questions, and workflow configuration while building agent-powered features on tandem.ac.
Skip if: Projects that do not use Tandem, or teams that need runtime execution APIs rather than documentation retrieval.
What do I get? / Deliverables
Once the docs MCP remote is connected, the agent can cite current Tandem guidance for installs, SDKs, and workflows inside the same session where you write code.
- In-session answers grounded in Tandem install and SDK documentation
- Faster agent configuration against documented workflows
- Reduced tab-switching to tandem.ac during implementation
Recommended MCP Servers
Journey fit
Documentation MCP servers land in build because solo builders pull authoritative setup and API guidance while implementing Tandem-based workflows, not while doing initial idea research. docs is the canonical shelf: the server’s purpose is retrieval of Tandem docs, install guides, SDK references, and agent configuration help from a remote MCP endpoint.
How it compares
Authoritative Tandem docs over MCP, not a trading/finance server or a bundled inference app runner.
Common Questions / FAQ
Who is ac.tandem/docs-mcp for?
Developers and solo builders implementing Tandem who want their AI coding agent to query official docs, SDKs, and setup guides without leaving the editor.
When should I use ac.tandem/docs-mcp?
Use it during build when you are installing Tandem, wiring SDKs, following documented workflows, or debugging agent configuration against tandem.ac guidance.
How do I add ac.tandem/docs-mcp to my agent?
Register the ac.tandem/docs-mcp remote in your MCP client per Tandem’s install documentation on tandem.ac, then enable the server and verify doc search tools appear.