Docfork: 🌿 Fresh docs for your AI Code Editor

@latest docs for 9000+ libraries in your AI code editor, with a single MCP.

🛠️ Get Started in Seconds

📋 Requirements

• Node.js ≥ v18
• Cursor/Windsurf/Claude Desktop (any MCP client)

⚡ Quick Setup (Cursor)

1. Settings -> Cursor Settings -> MCP Tools
2. Add New MCP Server
3. Or configure per-project via .cursor/mcp.json

Recommended Setup: Add this to your global ~/.cursor/mcp.json (or per-project in ./.cursor/mcp.json):

Cursor Remote Server Connection

{
  "mcpServers": {
    "docfork": {
      "url": "https://mcp.docfork.com/mcp"
    }
  }
}

Cursor Local Server Connection

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

{
  "mcpServers": {
    "docfork": {
      "command": "bunx",
      "args": ["-y", "docfork"]
    }
  }
}

{
  "mcpServers": {
    "docfork": {
      "command": "deno",
      "args": ["run", "--allow-env", "--allow-net", "npm:docfork"]
    }
  }
}

Install in Windsurf

Add this to your Windsurf MCP config. See Windsurf MCP docs for more info.

Windsurf Remote Server Connection

{
  "mcpServers": {
    "docfork": {
      "serverUrl": "https://mcp.docfork.com/sse"
    }
  }
}

Windsurf Local Server Connection

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

Install in VS Code

Add this to your VS Code MCP config. See VS Code MCP docs for more info.

VS Code Remote Server Connection

{
  "mcpServers": {
    "docfork": {
      "type": "http",
      "url": "https://mcp.docfork.com/mcp"
    }
  }
}

VS Code Local Server Connection

{
  "servers": {
    "docfork": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "docfork"]
    }
  }
}

Install in Zed

One-click install: → Get the Docfork Extension

Or Manual config (for power users):

{
  "context_servers": {
    "docfork": {
      "command": {
        "path": "npx",
        "args": ["-y", "docfork"]
      },
      "settings": {}
    }
  }
}

Install in Claude Code

Run this command. See Claude Code MCP docs for more info.

Claude Code Remote Server Connection

claude mcp add --transport sse docfork https://mcp.docfork.com/sse

Claude Code Local Server Connection

claude mcp add docfork -- npx -y docfork

Install in Claude Desktop

Add this to your Claude Desktop claude_desktop_config.json file. See Claude Desktop MCP docs for more info.

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

Install in BoltAI

Open the "Settings" page of the app, navigate to "Plugins," and enter the following JSON:

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

More info is available on BoltAI's Documentation site. For BoltAI on iOS, see this guide.

Using Docker

If you prefer to run the MCP server in a Docker container:

1. Build the Docker Image:

   First, create a Dockerfile in the project root (or anywhere you prefer):

   Click to see Dockerfile content

   FROM node:18-alpine
   
   WORKDIR /app
   
   # Install the latest version globally
   RUN npm install -g docfork
   
   # Expose default port if needed (optional, depends on MCP client interaction)
   # EXPOSE 3000
   
   # Default command to run the server
   CMD ["docfork"]
   

   Then, build the image using a tag (e.g., docfork-mcp). Make sure Docker Desktop (or the Docker daemon) is running. Run the following command in the same directory where you saved the Dockerfile:

   docker build -t docfork .
   

2. Configure Your MCP Client:

   Update your MCP client's configuration to use the Docker command.

   Example for a cline_mcp_settings.json:

   {
     "mcpServers": {
       "docfork": {
         "autoApprove": [],
         "disabled": false,
         "timeout": 60,
         "command": "docker",
         "args": ["run", "-i", "--rm", "docfork-mcp"],
         "transportType": "stdio"
       }
     }
   }
   

   Note: This is an example configuration. Please refer to the specific examples for your MCP client (like Cursor, VS Code, etc.) earlier in this README to adapt the structure (e.g., mcpServers vs servers). Also, ensure the image name in args matches the tag used during the docker build command.

Install in Windows

The configuration on Windows is slightly different compared to Linux or macOS (Cline is used in the example). The same principle applies to other editors; refer to the configuration of command and args.

{
  "mcpServers": {
    "github.com/docfork/mcp": {
      "command": "cmd",
      "args": ["/c", "npx", "-y", "docfork@latest"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

Available Tools

Docfork MCP provides the following tool that LLMs can use:

• search: Searches the library and returns its documentation.
  • libraryName (required): The name of the library to search for
  • topic (required): Focus the docs on a specific topic (e.g., "routing", "hooks")
  • tokens (optional, default 10000, max 50000): Max number of tokens to return. Values less than the configured DEFAULT_MINIMUM_TOKENS value or the default value of 10000 are automatically increased to that value.

Development

Clone the project and install dependencies:

bun i

Build:

bun run build

Local Configuration Example

{
  "mcpServers": {
    "docfork": {
      "command": "npx",
      "args": ["tsx", "/path/to/folder/docfork/src/index.ts"]
    }
  }
}

Testing with MCP Inspector

npx -y @modelcontextprotocol/inspector npx docfork

Troubleshooting

Module Not Found Errors

If you encounter ERR_MODULE_NOT_FOUND, try using bunx instead of npx:

{
  "mcpServers": {
    "docfork": {
      "command": "bunx",
      "args": ["-y", "docfork"]
    }
  }
}

This often resolves module resolution issues in environments where npx doesn't properly install or resolve packages.

ESM Resolution Issues

For errors like Error: Cannot find module 'uriTemplate.js', try the --experimental-vm-modules flag:

{
  "mcpServers": {
    "docfork": {
      "command": "npx",
      "args": ["-y", "--node-options=--experimental-vm-modules", "docfork"]
    }
  }
}

Troubleshooting Common MCP Client Errors

1. Append @latest to the package name to pull the newest release.
2. Swap npx for bunx if the command stalls or fails.
3. Prefer Deno as a drop-in alternative when you hit bundler issues.
4. Verify you’re on Node.js v18+ so fetch is available natively.

⚠️ Disclaimer

Docfork is an open, community-driven catalogue. Although we review submissions, we make no warranties—express or implied—about the accuracy, completeness, or security of any linked documentation or code. Projects listed here are created and maintained by their respective authors, not by Docfork.

If you spot content that is suspicious, inappropriate, or potentially harmful, please contact us.

By using Docfork, you agree to do so at your own discretion and risk.