Telodocs
OfficialThis server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Telodocs
Docs site + MCP server from a single docs/ folder.
Write Markdown. Telodocs runs the browser UI, search, and MCP tools (get_nav, list_docs, search_docs, glob, grep, read) — no NestJS app, no build step in your project.
npx telodocs new my-docs
cd my-docs
npx telodocs devDocs site: http://localhost:3000
MCP server: http://localhost:3000/mcp
What you get
After telodocs new:
my-docs/
├── docs/ # Markdown, docs.json, logo, favicon
├── AGENTS.md # instructions for AI agents writing docs
├── README.md
├── .env # settings + default API key (gitignored)
├── .env.example
└── .gitignoreSample pages under docs/:
docs/
├── docs.json
├── index.md
├── logo.svg
├── favicon.svg
├── guides/getting-started.md
└── conventions.mdTelodocs ships the server when you run telodocs dev or telodocs start — your repo stays docs-only.
Migrating from Mintlify
Telodocs reads a Mintlify-style docs/docs.json and supports .md / .mdx pages. When moving an existing site:
Put
docs.json, logo, and favicon underdocs/Use nested groups in
pagesfor collapsible sidebar sections (Mintlify format)Flat groups named
Parent — Childare auto-nested into a tree (common after Mintlify export)Use page slugs without extensions (e.g.
guides/getting-started)Only root
indexis the homepage — section indexes stay at/docs/.../index.mdxReplace Mintlify
<Card>components with<div class="docs-card-grid">/<a class="docs-card">
See template/AGENTS.md (copied into new projects) for step-by-step agent instructions.
Related MCP server: devdoc
Commands
Command | Description |
| Scaffold a docs-only project |
| Start server (development) |
| Start server (production) |
Run from the directory that contains docs/.
Customize the site
docs/docs.json— site name, logo, favicon, sidebar navigation (Mintlify-style)docs/*.md— pages with optional frontmatter (title,description,group)AGENTS.md— doc authoring guide for coding agents (agents.md compatible)
MCP client setup
MCP is open by default — no auth headers needed.
To require a key, set TELODOCS_MCP_AUTH=gated in .env and use TELODOCS_API_KEY as the bearer token.
Cursor
{
"mcpServers": {
"my-docs": {
"url": "http://localhost:3000/mcp",
"headers": {
"Authorization": "Bearer i-love-coding-agents"
}
}
}
}Omit headers while auth is open. Replace the token if you changed TELODOCS_API_KEY in .env.
Configuration
.env is created on telodocs new:
Variable | Default | Description |
|
| Used when auth is |
|
|
|
|
|
|
|
| HTTP port |
|
| Documentation directory |
|
| MCP endpoint path |
How it works
docs/ → telodocs server
├── /mcp ← coding agents
└── / ← humansLicense
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Turn a GitHub repo or docs site into agent-ready context: pack it or search it, over MCP.
Create guides as MCP servers to instruct coding agents to use your software (library, API, etc).
Read-only MCP server for the OrchestKit docs: full-text search + Markdown fetch. No auth.
Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers.
Related MCP Servers
- AlicenseAqualityDmaintenanceScrapes, stores, and searches documentation locally, enabling AI assistants to access and query documentation via MCP.114MIT
- AlicenseNot gradedqualityDmaintenanceA documentation MCP server that crawls websites and Git repositories, stores them as Markdown, and provides tools to search and retrieve documentation for local LLMs and AI agents.Apache 2.0
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.-
- AlicenseNot gradedqualityDmaintenanceServes documentation for Git repositories via MCP, providing tools to search docs, retrieve feature details, WIP status, and full context. Enables LLM agents to access human and LLM-optimized documentation through stdio or SSE transports.MIT