docforge
docforge indexes your Confluence spaces and local git repositories, embeds the content, and serves it over MCP so Claude Code, Cursor, Copilot, and any MCP-capable assistant can search your team’s knowledge without your data leaving your infrastructure.
docforge doesn’t replace your AI assistant. It feeds it — turning Claude Code, Cursor, Copilot, and anything else that speaks MCP into tools that actually know your team’s docs and code.
Why docforge
Section titled “Why docforge”| Tool | Self-hosted | Integration | Confluence + code | Footprint | Complements AI assistants? |
|---|---|---|---|---|---|
| docforge | ✓ | MCP server | ✓ (Confluence + local git) | Minimal (PG + 1 container) | ✓ (any MCP client) |
| Atlassian Rovo MCP | ✗ (Cloud-only) | MCP server | Confluence only (Cloud) | SaaS | ✓ |
| zilliztech/claude-context | ✓ | MCP server | Code only | Minimal | ✓ |
| Onyx | ✓ | MCP + chat UI | ✓ (50+ connectors) | Heavy (Standard) / Minimal (Lite) | ✓ (+ its own UI) |
| Cursor codebase index + @Docs | ✗ | Proprietary | Code + public web docs | SaaS | — (built into Cursor only) |
| Copilot Spaces | ✗ | Proprietary (MCP for actions) | Code + attachments | SaaS | — (built into Copilot only) |
| Sourcegraph Cody | ✓ (Enterprise) | OpenCtx / MCP | ✓ (via OpenCtx) | Heavy (Sourcegraph platform) | — (built into Cody only) |
| LangChain / LlamaIndex DIY | ✓ | Whatever you build | You wire it | Depends | Depends |
docforge is the narrow, focused option: minimal footprint, MCP-native so it works with every assistant, and combines Confluence + code out of the box. It competes on being small, legible, vendor-neutral, and self-hosted — four properties no commercial option offers together.
When docforge fits
Section titled “When docforge fits”- You run Confluence Data Center/Server, or you want to self-host.
- Your team uses MCP-capable assistants (Claude Code, Cursor with MCP, Copilot with MCP).
- You want Confluence + git repos indexed together with one tool.
- Operational simplicity matters — one Postgres, one container, MIT-licensed code you can audit in an afternoon.
When docforge is the wrong choice
Section titled “When docforge is the wrong choice”- You need 50+ connectors (Slack, Jira, Gmail, Drive, Notion) → use Onyx or Glean.
- You need per-document ACLs enforced at query time → not yet supported; use Onyx.
- You need a chat UI for non-developers → docforge has no UI.
- You’re on Atlassian Cloud and happy with SaaS → Atlassian Rovo MCP is free and official.
- You need SSO / SCIM / RBAC → out of scope.
- Very large corpora (>100K pages/chunks) → hybrid retrieval is on the roadmap, not shipped.
- Near-real-time updates → ingest is batch; no webhook sync.
For the full trust model, accepted risks, and assumptions docforge makes about its operating environment, see the threat model.