Doctree MCP Server

Most developer tooling work still happens through a UI a human drives. Doctree MCP MCP server moves it into the conversation instead. Agentic document retrieval over markdown, CSV, and JSONL — BM25 search + tree navigation via MCP. Inspired by PageIndex and Pagefind.

The short version

Restart the tool → ask "search the docs for X" or invoke the doc-read prompt.

The tools it exposes

The server publishes 14 tools. What each one is for:

• Skills — /doc-read · /doc-write · /doc-lint
• Mode — Use when
• CLI — init, lint, debug-index
• search_documents — BM25 keyword search + facet filters + glossary expansion (markdown · CSV · JSONL)
• get_tree — Table of contents — headings, word counts, summaries
• get_node_content — Full text of a specific section by node ID
• navigate_tree — A section plus all descendants in one call
• lookup_row — O(1) exact-key lookup for structured data rows (e.g. PROJ-44)
• find_similar — Duplicate detection with overlap ratios
• draft_wiki_entry — Scaffold: suggested path, inferred frontmatter, glossary hits
• write_wiki_entry — Validated write: path containment, schema, duplicate guards, dry-run
• Approach — Primitive

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: DOCS_ROOT, WIKI_WRITE, GLOSSARY_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Doctree MCP's toolset — Skills, Mode, CLI and 11 more — is a fair guide to whether it matches your workflow. It is maintained by joesaby; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Doctree MCP.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.