Documentation MCP Server
Connect AI editors to the TelemetryOS documentation via MCP
What is the Documentation MCP Server?
The TelemetryOS Documentation MCP Server provides read-only, programmatic access to TelemetryOS documentation through the Model Context Protocol (MCP). It is a public endpoint for AI coding tools that need grounded documentation context, and it does not require account authentication.
Documentation MCP is docs-only. It does not expose account data or perform account actions.
Documentation MCP vs. Platform MCP
The Documentation MCP and Platform MCP Server are complementary:
| Server | Endpoint | Purpose |
|---|---|---|
| Documentation MCP | https://docs.telemetryos.com/mcp | Read-only access to TelemetryOS docs and API reference content. Public and anonymous. |
| Platform MCP | https://mcp.telemetryos.com/mcp | Act on a TelemetryOS account. Requires an MCP token with scoped permissions. |
Use Documentation MCP to ground answers in docs. Use Platform MCP when an agent needs to take actions in an account.
Endpoint
Documentation MCP endpoint:
https://docs.telemetryos.com/mcpThe endpoint is public and anonymous. No Authorization header is required.
What it provides
- Documentation search across TelemetryOS docs content
- Structured retrieval of documentation pages for agent context
- Access to API reference material sourced from the TelemetryOS OpenAPI specification
- Reliable grounding for code examples and implementation guidance based on published docs
Connecting a Client
Add to .mcp.json:
{
"mcpServers": {
"telemetryos-documentation": {
"type": "http",
"url": "https://docs.telemetryos.com/mcp"
}
}
}No token or credentials are needed for this endpoint.
Verifying the Connection
After configuration, open a new chat in your client and test with prompts such as:
- "How do I authenticate with the TelemetryOS API?"
- "Show me the API reference for listing devices."
- "Create a TypeScript example for uploading media with TelemetryOS."
Expected behavior:
- The agent answers using TelemetryOS documentation context retrieved through MCP.
- Responses should reference relevant TelemetryOS docs content.
- Account-changing requests should be redirected to the Platform MCP Server.
Relationship to Ask AI and LLMs.txt
TelemetryOS has three complementary AI surfaces: Ask AI is the on-site assistant for documentation readers, Documentation MCP is the integration surface for editor-based agents such as Claude Code and Codex, and LLMs.txt is the crawlable navigation index both systems can use to discover documentation structure.
Updated about 1 month ago