# Doc Bridge

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.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 10
- Author: AgentsKit-io
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/AgentsKit-io/doc-bridge
- Updated: 2026-10-24
- HTML: https://affpapa.org/en/nevibecode/mcp/doc-bridge

## What it 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.

## Requirements
- Needs: Node.js (commands run via npx)

## Install

### Claude Code (native platform)

**Platform CLI**
```bash
claude mcp add doc-bridge -- npx -y @agentskit/doc-bridge
```

### Codex

**Platform CLI**
```bash
codex mcp add doc-bridge -- npx -y @agentskit/doc-bridge
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "doc-bridge": {
            "command": "npx",
            "args": [
                "-y",
                "@agentskit/doc-bridge"
            ]
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "doc-bridge": {
            "type": "stdio",
            "command": "npx",
            "args": [
                "-y",
                "@agentskit/doc-bridge"
            ]
        }
    }
}
```

### Gemini CLI

**Platform CLI**
```bash
gemini mcp add doc-bridge npx -y @agentskit/doc-bridge
```

## When to use it
- 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
- Index the repo docs and tell me where an agent should start reading
- Give me a handoff for editing the `auth` package: editRoots and checks
- Ingest `.agent-memory` and suggest what should become project documentation

## Similar
- [REA](https://affpapa.org/en/nevibecode/mcp/rea.md) — MCP server · ★ 386989
- [GitHub](https://affpapa.org/en/nevibecode/mcp/github.md) — MCP server · ★ 33918
- [Netdata](https://affpapa.org/en/nevibecode/mcp/netdata.md) — MCP server · ★ 81115
- [browser-use](https://affpapa.org/en/nevibecode/mcp/browser-use.md) — MCP server · ★ 119160
- [Codebase Memory](https://affpapa.org/en/nevibecode/mcp/codebase-memory.md) — MCP server · ★ 47392
- [mcp-server](https://affpapa.org/en/nevibecode/mcp/mcp-server.md) — MCP server · ★ 43872

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md