Doc Bridge — MCP server for Claude Code: doc routing for agents
Turns repo docs into a routing contract for a coding agent: where to start reading, which paths it may touch, which check proves the change. Useful when the agent keeps editing the wrong package.
claude mcp add doc-bridge -- npx -y @agentskit/doc-bridgeWhat Doc Bridge does
Doc Bridge reads your repository documentation, the ownership map and the human docs site, then hands back an AgentHandoff — a starting file, a list of editRoots, the check commands, and a link to the human guide. It runs both ways. ak-docs index and ak-docs query --agent push docs toward the agent; ak-docs memory ingest walks .agent-memory/** and .cursor/rules/*.mdc, sorts what belongs in project docs, and drafts a promotion you review, with promote --pr opening it as a pull request.
The core needs no LLM and no API key. A separate command, ak-docs audit documentation, compares what the docs claim against the observed project graph and reports missing coverage, stale relations, contradictions and exact duplicates. It leaves semantic correctness and redundant prose marked not-analyzed until a person or a configured agent looks at them.
Node.js 22 or newer and TypeScript 5.8+ are required. Install runs through npx, so there is nothing to build first. The same contract is reachable from the terminal, MCP, CI and an optional chat surface.
What it helps with
- figure out which file an agent should read first
- cap the packages an agent is allowed to edit
- pick the check that proves a change is correct
- locate the human guide that explains a rule
- compare declared docs against the real project graph
Example prompts for the agent
- Index the repo docs and tell me where an agent should start reading
- Give me a handoff for editing the
authpackage: editRoots and checks - Ingest
.agent-memoryand suggest what should become project documentation
How to install Doc Bridge
Platform CLI
claude mcp add doc-bridge -- npx -y @agentskit/doc-bridgePlatform CLI
codex mcp add doc-bridge -- npx -y @agentskit/doc-bridgeConfig file
{
"mcpServers": {
"doc-bridge": {
"command": "npx",
"args": [
"-y",
"@agentskit/doc-bridge"
]
}
}
}Config file
{
"servers": {
"doc-bridge": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@agentskit/doc-bridge"
]
}
}
}Platform CLI
gemini mcp add doc-bridge npx -y @agentskit/doc-bridgeStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Doc Bridge
How do I install Doc Bridge in Claude Code?
Run claude mcp add doc-bridge -- npx -y @agentskit/doc-bridge.
What does Doc Bridge do?
It builds a routing contract out of your repo docs: a starting file, the edit roots, the check commands and a pointer to the human guide. It also reconciles docs against the project graph and promotes agent memory into project documentation.
Does Doc Bridge need an API key?
No. The core is deterministic and runs without an LLM. A key only comes into play if you put a chat surface on top of that layer.
