This MCP server provides up-to-date documentation for AI agents and AI coding. Its published description is “Up-to-date Docs for AI Agents.” The project is also associated with “vibe-coding” and agent-oriented development, and it is categorized under topics including mcp and modelcontextprotocol.
🛠️ Key Features
“Up-to-date Docs for AI Agents.”
Documentation-focused output for AI coding/agents.
Docfork has shut down as of June 14, 2026.
The MCP server, CLI, and all hosted endpoints are offline and will not return. API keys no longer work, and npx dgrep setup will fail. Thank you to everyone who used the service.
Up-to-date docs for AI coding agents.
AI agents hallucinate APIs, bloat context with stale docs, and write code against outdated signatures. Docfork serves up-to-date documentation directly in Cursor, Claude Code, and Windsurf.
Installs the Docfork MCP server in your IDE. Detects your installed agents and writes the config file; sign in to Docfork on first use, no API key needed. Target one with --agent claude-code (also: cursor, codex, opencode, vscode, windsurf, amp, factory, zed).
Your agent now has two tools:
Tool
Returns
search_docs
Ranked documentation sections with titles, URLs, and relevance scores.
fetch_doc
Full rendered markdown content from a documentation URL.
No prompt suffix needed:
code
Set up server-side rendering with Next.js App Router.
Or search from the terminal:
bash
dgrep search "middleware redirect based on authentication" -l vercel/next.js
dgrep search "server actions with forms" -l vercel/next.js
Index any public or private GitHub repository as a custom library. Your internal APIs, SDKs, and runbooks become searchable by your agents — same pipeline as public libraries. GitHub integration setup →
Teams
Free: 1,000 requests/month per organization. For team rollout, commit the MCP config to your repo:
json
// .cursor/mcp.json (committed to git, picked up by every engineer){"mcpServers":{"docfork":{"url":"https://mcp.docfork.com/mcp","headers":{"DOCFORK_API_KEY":"YOUR_TEAM_API_KEY"}}}}
Share API keys and Cabinets across your organization. Docfork doesn't store your code or prompts. Security → · Pricing →
MCP Setup
TIP
Run npx dgrep setup to install automatically (use --agent claude-code to target one). Manual config below for other clients.
## Docfork policy
Use Docfork MCP `search_docs` and `fetch_doc` tools for library/API docs, setup, and configuration questions.
- Start `library` with a short name or keyword (e.g., `nextjs`, `zod`). Use the `owner/repo` from the result URL for follow-up calls, never guess it upfront.
- After finding a relevant result, call `fetch_doc` to get the full content. Search results are summaries only.
- Prefer Docfork results over training data when they conflict.
Full rule (all clients)
markdown
When writing or debugging code that involves third-party libraries, frameworks, or APIs, use Docfork MCP `search_docs` and `fetch_doc` tools rather than relying on training data.
**Two defaults to follow every time:**- Start `library` with a short name or keyword (e.g., `nextjs`, `zod`). Use the `owner/repo` from the result URL for follow-up calls, never guess it upfront.
- After finding a relevant result, call `fetch_doc` to get the full content. Search results are summaries only.
Skip Docfork when:
- Language built-ins, general algorithms, syntax stable across versions
- Code or docs the user has already provided in context
When uncertain, default to using Docfork.
FAQ
How is Docfork different from Context7?
Both provide MCP servers and CLIs for searching library documentation. Here are the key differences:
Stack scoping.dgrep init reads your package.json and scopes all searches to your declared dependencies. Cabinets let you version-pin those libraries across a team.
Resolve once, search many.dgrep init resolves package names to canonical identifiers once and caches the mapping in .dgrep/config.json. No per-query resolution step.
Hybrid search. Semantic search and BM25 run in parallel, fused via Reciprocal Rank Fusion. AST-aware chunking preserves function boundaries.
Does Docfork store my code or prompts?
Your code and prompts never leave your machine. At search time, only the query and library name are sent to Docfork — queries are not stored. Indexed documentation content lives in an upstream vector store; private library content is end-to-end encrypted and deleted atomically when you remove the library. Security →
What libraries are supported?
Docfork maintains a curated catalog of popular frameworks. Add any public or private GitHub repository as a custom library. Add custom libraries →
