Docfork MCP - Up-to-date Docs for AI Agents.

⚡ Why Docfork?

Standard AI models (Claude 4.5, GPT-5.1) have a knowledge cutoff. They don't know about the framework changes released last week.

The Problem:

• ❌ AI hallucinates syntax from year-old docs.
• ❌ AI guesses APIs that don't exist.
• ❌ Valuable coding time is lost debugging deprecated patterns.

The Solution:

• ✅ Live Sync: We pull documentation from the source automatically.
• ✅ Private Cabinets: Scope your search to your specific tech stack (Next.js + Supabase + Tailwind), avoiding generic results.
• ✅ Team Ready: Share context with your whole organization.

🚀 Quick Start

1. Get your Free API Key

Go to app.docfork.com.

• Free Tier: 1,000 requests/month org-wide (2x industry standard).
• Team: 5 free seats included.
• Pro Tier & Private Docs: Coming soon 🚀

2. Install MCP

1. Click the button below:

2. Or manually add to Cursor Settings > Tools & MCP > New MCP Server:

Remote (Recommended):

{
  "mcpServers": {
    "docfork": {
      "url": "https://mcp.docfork.com/mcp",
      "headers": {
        "DOCFORK_API_KEY": "YOUR_API_KEY"
      }
    }
  }
}

Local:

{
  "mcpServers": {
    "docfork": {
      "command": "npx",
      "args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
    }
  }
}

Remote:

claude mcp add --transport http docfork https://mcp.docfork.com/mcp --header "DOCFORK_API_KEY: YOUR_API_KEY"

Local:

claude mcp add docfork -- npx -y docfork --api-key YOUR_API_KEY

Remote:

{
  "mcp": {
    "docfork": {
      "type": "remote",
      "url": "https://mcp.docfork.com/mcp",
      "headers": {
        "DOCFORK_API_KEY": "YOUR_API_KEY"
      },
      "enabled": true
    }
  }
}

Local:

{
  "mcp": {
    "docfork": {
      "type": "local",
      "command": ["npx", "-y", "docfork", "--api-key", "YOUR_API_KEY"],
      "enabled": true
    }
  }
}

See Installation for Other MCP Clients (VS Code, Windsurf, Claude Desktop, etc.) →

3. Usage

Just tell your AI to use docfork:

Create a basic Next.js app with the App Router. use docfork

🛡️ The Docfork Difference: Cabinets

Unlike other tools that search the "entire internet" and return bloated results, Docfork lets you create Cabinets.

Cabinets are curated, private indexes specific to your project stack.

1. Create a Cabinet in your Dashboard.
2. Add the libraries you need.
3. Add the DOCFORK_CABINET header to your MCP config.

{
  "mcpServers": {
    "docfork": {
      "url": "https://mcp.docfork.com/mcp",
      "headers": {
        "DOCFORK_API_KEY": "YOUR_API_KEY",
        "DOCFORK_CABINET": "general"
      }
    }
  }
}

Now your AI knows you mean Better Auth, not Firebase or Auth0, because it's locked to your Cabinet.

💡 Pro Tips

Set & Forget: Auto-Invoke Docfork

Add a Rule to make your AI automatically fetch documentation whenever you mention a library:

Add Rule to Cursor (One-Click)

Manual Setup (Copy & Paste) If you prefer manual configuration, add a rule to your MCP client to auto-invoke Docfork for code-related questions:

You have access to the docfork MCP server. To ensure the code you write is accurate and up-to-date, you must follow these requirements:

1. Auto-Invoke: Always use `docfork_search_docs` when asked for library implementation, API setup, or debugging.
2. Context Strategy:
   - Search: Call `docfork_search_docs`. Review the `content` snippets in the results.
   - Read: Only call `docfork_read_url` if the search snippets are incomplete or you need the full file context for a complex implementation.
   - Identity: Use the `docforkIdentifier` in follow-up searches to narrow results to a specific library.

If you are unsure of a library's latest syntax, search with docfork first.

🔨 Available Tools

Docfork provides two high-performancetools optimized for AI agents:

[!TIP] Identity First: Always use the docforkIdentifier in your searches (e.g., vercel/next.js) for 10x more accurate results within a specific library.

📖 Documentation

Find specific guides and technical resources at docs.docfork.com:

Installation

• Quick Start & Major IDEs – Setup for Cursor, VS Code, Windsurf, & Claude.
• All Supported Clients – Configuration reference for Zed, BoltAI, Docker, and 30+ others.

Features & Guides

• Cabinet Scoping - How to create project-specific documentation silos.
• Rules – Automate Docfork behavior using project-level rules.
• Troubleshooting – Fix common connection or auth issues.

📰 Media & Resources

Keep up with the changelog and community discussions:

• Official Changelog – We ship weekly.
• The Docfork Blog – Read our latest posts and updates.
• X (Twitter) – Follow for @latest updates.

Star History

⚠️ Disclaimer

Docfork is an open, community-driven catalogue. While we review submissions, we cannot guarantee accuracy for every project listed. If you spot an issue, raise a GitHub issue or contact support.

License

MIT