Official Registry metadata
docs-mcp
Remote MCP server for Tandem docs, install guides, SDKs, workflows, and agent setup help.
55Recommendation
Configure in your coding agent
Copy this metadata-derived example, review it, and add secrets only through environment variables on your own machine.
~/.codex/config.toml or codex mcp addRun this command locally. Review package commands before confirming execution.
codex mcp add 'ac-tandem-docs-mcp-c85904e3' --url 'https://tandem.ac/mcp'
.mcp.jsonAdd this entry to the project-level mcpServers object.
{
"mcpServers": {
"ac-tandem-docs-mcp-c85904e3": {
"type": "http",
"url": "https://tandem.ac/mcp"
}
}
}.cursor/mcp.jsonKeep secret values as environment-variable references.
{
"mcpServers": {
"ac-tandem-docs-mcp-c85904e3": {
"type": "http",
"url": "https://tandem.ac/mcp"
}
}
}.vscode/mcp.jsonReview the generated server entry before enabling it.
{
"servers": {
"ac-tandem-docs-mcp-c85904e3": {
"type": "http",
"url": "https://tandem.ac/mcp"
}
}
}~/.gemini/settings.jsonAdd this entry to mcpServers and keep trust disabled initially.
{
"mcpServers": {
"ac-tandem-docs-mcp-c85904e3": {
"httpUrl": "https://tandem.ac/mcp",
"trust": false
}
}
}Stacklane does not install, connect to, execute, or security-certify MCP servers. Metadata and risk signals are automated discovery aids.
Declared requirements
Risk signals
- No elevated requirement declared in registry metadata