Skip to main content

docs-mcp

Server Details

Remote MCP server for Tandem docs, install guides, SDKs, workflows, and agent setup help.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Unhealthy
Last Tested: 2026-09-06 04:30
Transport: Streamable HTTP
URL
Repository: frumu-ai/tandem
GitHub Stars: 87

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

12 tool updatesApr 24, 2026

Changedanswer_how_to2 fields changed

addedInput schema / properties / docs_ref

Added value: +{
+  "description": "Docs channel or immutable ref. Defaults to stable.",
+  "type": "string"
+}

addedInput schema / properties / engine_version

Added value: +{
+  "description": "Optional Tandem engine version hint. Prefer stable docs for installed engines.",
+  "type": "string"
+}

Changedcompare_doc_page_refresh1 field changed

addedInput schema / properties / docs_ref

Added value: +{
+  "description": "Docs channel or immutable ref. Defaults to stable.",
+  "type": "string"
+}

Changedcompare_docs_index_refresh1 field changed

addedInput schema / properties / docs_ref

Added value: +{
+  "description": "Docs channel or immutable ref. Defaults to stable.",
+  "type": "string"
+}

Changedget_doc2 fields changed

addedInput schema / properties / docs_ref

Added value: +{
+  "description": "Docs channel or immutable ref. Defaults to stable.",
+  "type": "string"
+}

addedInput schema / properties / engine_version

Added value: +{
+  "description": "Optional Tandem engine version hint for compatibility checks.",
+  "type": "string"
+}

Changedget_start_path1 field changed

addedInput schema / properties / docs_ref

Added value: +{
+  "description": "Docs channel or immutable ref. Defaults to stable.",
+  "type": "string"
+}

Changedget_tandem_guide1 field changed

addedInput schema / properties / docs_ref

Added value: +{
+  "description": "Docs channel or immutable ref. Defaults to stable.",
+  "type": "string"
+}

Changedinvalidate_docs_cache1 field changed

addedInput schema / properties / docs_ref

Added value: +{
+  "description": "Optional docs ref to scope page/index cache invalidation.",
+  "type": "string"
+}

Changedrecommend_next_docs1 field changed

addedInput schema / properties / docs_ref

Added value: +{
+  "description": "Docs channel or immutable ref. Defaults to stable.",
+  "type": "string"
+}

Changedrefresh_doc_page1 field changed

addedInput schema / properties / docs_ref

Added value: +{
+  "description": "Docs channel or immutable ref. Defaults to stable.",
+  "type": "string"
+}

Changedrefresh_docs_index1 field changed

addedInput schema / properties / docs_ref

Added value: +{
+  "description": "Docs channel or immutable ref. Defaults to stable.",
+  "type": "string"
+}

Changedsearch_docs2 fields changed

addedInput schema / properties / docs_ref

Added value: +{
+  "description": "Docs channel or immutable ref. Defaults to stable. Use next, refs/<sha>, or releases/<version> only when explicitly needed.",
+  "type": "string"
+}

addedInput schema / properties / engine_version

Added value: +{
+  "description": "Optional Tandem engine version hint. If supplied without docs_ref, the MCP still defaults to stable unless a matching versioned docs ref is configured.",
+  "type": "string"
+}

Changedwarmup_docs_cache1 field changed

addedInput schema / properties / docs_ref

Added value: +{
+  "description": "Docs channel or immutable ref. Defaults to stable.",
+  "type": "string"
+}

11 tool updatesApr 2, 2026

Changedanswer_how_to3 fields changed

addedInput schema / properties / audience / description

Added value: +"Optional audience hint such as developer, desktop user, or operator."

addedInput schema / properties / limit / description

Added value: +"Maximum number of supporting docs recommendations to include."

addedInput schema / properties / task / description

Added value: +"The Tandem task or question that needs a docs-grounded answer."

Changedcompare_doc_page_refresh1 field changed

addedInput schema / properties / path / description

Added value: +"Docs path like /start-here/ or /sdk/python/ to compare before and after refresh."

Changedget_doc1 field changed
- addedInput schema / properties / path / description
```
Added value: +"Docs path like /sdk/python/ or a full Tandem docs URL."
```
Changedget_start_path1 field changed
- addedInput schema / properties / role / description
```
Added value: +"The user role to optimize the docs starting point for."
```
Changedget_tandem_guide1 field changed
- addedInput schema / properties / topic / description
```
Added value: +"Named Tandem learning guide to return."
```

Changedinvalidate_docs_cache2 fields changed

addedInput schema / properties / path / description

Added value: +"Required when target is page; identifies the specific docs path to invalidate."

addedInput schema / properties / target / description
```
Added value: +"Which cache area to invalidate."
```

Changedrecommend_next_docs3 fields changed

addedInput schema / properties / current_path / description

Added value: +"Current Tandem docs path the user has already read."

addedInput schema / properties / goal / description

Added value: +"Optional goal such as install Tandem, use the Python SDK, or build workflows."

addedInput schema / properties / limit / description

Added value: +"Maximum number of next-doc recommendations to return."

Changedrefresh_doc_page2 fields changed

addedInput schema / properties / force_refresh / description

Added value: +"Whether to bypass cache and force a network refresh attempt."

addedInput schema / properties / path / description

Added value: +"Docs path like /start-here/ or /sdk/python/ to refresh."

Changedrefresh_docs_index1 field changed
- addedInput schema / properties / force_refresh / description
```
Added value: +"Whether to bypass cache and force a network refresh attempt."
```

Changedsearch_docs3 fields changed

addedInput schema / properties / audience / description

Added value: +"Optional audience filter such as developer, desktop user, or operator."

addedInput schema / properties / limit / description

Added value: +"Maximum number of matching docs pages to return."

addedInput schema / properties / query / description

Added value: +"The Tandem question, task, or keyword query to search for."

Changedwarmup_docs_cache1 field changed
- addedInput schema / properties / force_refresh / description
```
Added value: +"Whether to bypass cache and force fresh upstream fetches first."
```

13 tool updatesApr 2, 2026
- First observedanswer_how_to
- First observedcompare_doc_page_refresh
- First observedcompare_docs_index_refresh
- First observedget_doc
- First observedget_docs_cache_status
- First observedget_start_path
- First observedget_tandem_guide
- First observedinvalidate_docs_cache
- First observedrecommend_next_docs
- First observedrefresh_doc_page
- First observedrefresh_docs_index
- First observedsearch_docs
- First observedwarmup_docs_cache

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Login with GitHub to comment

Related MCP Connectors

AurelianFlo A
com.aurelianflo
Remote MCP server for OFAC screening, EDD memos, exposure forecasts, queues, and reports.
Legal & Compliance Finance
112
supportsheep
io.github.pooriaarab
Remote MCP server for supportsheep: run AI interviews and manage support content for your blog.
Customer Support Content Management Systems Marketing
1
opencode
io.github.doc2mcp
MCP server for opencode documentation, generated by doc2mcp.
Documentation Access Developer Tools
24
Muninx MCP Server AOAuth
com.muninx
Remote MCP server for managing Muninx tickets, messages, ticket search, and support analytics.
Customer Support Project Management
2

Related MCP Servers

MCP Integration Bridge
Data Platforms App Automation
Randika97
F
license
Not graded
quality
C
maintenance
An MCP server that connects any two systems so an agent can explore both, map between them, and run real data transfers — then shows its working in a run folder you can audit afterwards.
Updated a month ago (2026-08-11 14:10 UTC)
1
-
MCP Store
Monitoring OS Automation Developer Tools
Meir83
A
license
Not graded
quality
C
maintenance
A comprehensive MCP server for IT, DBA, and developer tasks, enabling error resolution, task automation, performance monitoring, automated documentation, and configuration management.
Updated 20 days ago (2026-08-17 10:18 UTC)
5
ISC
Terminal MCP Server
Shell Access Command Line
charantek1styearbtech
A
license
Not graded
quality
C
maintenance
A production-ready MCP server for secure, session-based command execution, file manipulation, and system inspection via local terminal sessions.
Updated a month ago (2026-07-28 10:15 UTC)
14
ISC
ibmi-docs-mcp
Documentation Access Search Developer Tools
wyattmog
A
license
A
quality
C
maintenance
FastMCP server that lets agents search and fetch IBM i documentation via IBM Documentation's public APIs.
Updated 25 days ago (2026-08-12 16:21 UTC)
2
MIT

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation4/5

Most tools have distinct purposes, but there is some overlap between refresh and compare functions. For example, refresh_doc_page and compare_doc_page_refresh both handle page refreshes, which could cause confusion. However, their descriptions clarify differences in output (e.g., hashes vs. source reports), preventing major misselection.

Naming Consistency5/5

Tool names follow a consistent snake_case pattern with clear verb_noun structures, such as get_doc, search_docs, and invalidate_docs_cache. This predictability makes it easy for agents to understand and use the toolset without confusion over naming conventions.

Tool Count5/5

With 13 tools, the count is well-scoped for a documentation server, covering key operations like fetching, searching, caching, and guiding users. Each tool serves a specific function without redundancy, making the set comprehensive yet manageable for its purpose.

Completeness5/5

The toolset provides complete coverage for documentation management, including CRUD-like operations (e.g., get, search, refresh), caching control, and user guidance. There are no obvious gaps; agents can navigate, update, and optimize docs effectively without dead ends.

Resources