
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Lock your agent's context to your stack.
Define a Docfork Cabinet — Next.js 16 + Drizzle ORM + Better Auth — and every query returns only docs from your stack. No more bloated results. No more hallucinations.
Documentation context as precise as your dependency lockfile:
Cabinets — Lock your agent to a verified stack. Only your libraries. Fully isolated.
10,000+ libraries — Pre-chunked docs and code examples. ~200ms edge retrieval.
Team-ready — Share Cabinets and API keys across your org. Same context, every engineer.
Set a Cabinet:
Next.js 16+Drizzle ORM+Better Auth. Your agent only sees docs for your stack. No stray Express docs. No Prisma confusion.
Sign up at docfork.com — free: 1,000 requests/month, 5 team seats.
Run this command. See Claude Code MCP docs for more info.
claude mcp add docfork -- npx -y docfork --api-key YOUR_API_KEY
claude mcp add --header "DOCFORK_API_KEY: YOUR_API_KEY" --transport http docfork https://mcp.docfork.com/mcp
Add this to your OpenCode configuration file. See OpenCode MCP docs for more info.
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"docfork": {
"type": "remote",
"url": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_API_KEY",
},
"enabled": true,
},
},
}
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"docfork": {
"type": "local",
"command": ["npx", "-y", "docfork", "--api-key", "YOUR_API_KEY"],
"enabled": true,
},
},
}
Go to: Settings -> Cursor Settings -> MCP -> Add new global MCP server
Paste this into ~/.cursor/mcp.json. For project-scoped config, create .cursor/mcp.json in your project folder. See Cursor MCP docs for more info.
Since Cursor 1.0, click the buttons below to install instantly.
{
"mcpServers": {
"docfork": {
"url": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_API_KEY"
}
}
}
}
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
See OpenAI Codex for more information.
[mcp_servers.docfork]
args = ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
command = "npx"
startup_timeout_ms = 20_000
[mcp_servers.docfork]
url = "https://mcp.docfork.com/mcp"
http_headers = { "DOCFORK_API_KEY" = "YOUR_API_KEY" }
If you see startup timeout errors, try increasing startup_timeout_ms to 40_000.
Add this to your Antigravity MCP config file. See Antigravity MCP docs for more info.
{
"mcpServers": {
"docfork": {
"serverUrl": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_API_KEY"
}
}
}
}
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
Add this to your VS Code MCP config file. See VS Code MCP docs for more info.
"mcp": {
"servers": {
"docfork": {
"type": "http",
"url": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_API_KEY"
}
}
}
}
"mcp": {
"servers": {
"docfork": {
"type": "stdio",
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
You can configure the Docfork MCP server in Kilo Code using either the UI or by editing your project's MCP configuration file. Kilo Code supports two configuration levels: Global (mcp_settings.json) and Project-level (.kilocode/mcp.json).
https://mcp.docfork.com/mcpAuthorization, Value: Bearer YOUR_API_KEYCreate .kilocode/mcp.json:
{
"mcpServers": {
"docfork": {
"type": "streamable-http",
"url": "https://mcp.docfork.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
},
"alwaysAllow": [],
"disabled": false
}
}
}
See Kiro Model Context Protocol Documentation for details.
Kiro > MCP Servers+ Add button.{
"mcpServers": {
"Docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"],
"env": {},
"disabled": false,
"autoApprove": []
}
}
}
Save to apply.Add this to your Windsurf MCP config file. See Windsurf MCP docs for more info.
{
"mcpServers": {
"docfork": {
"serverUrl": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_API_KEY"
}
}
}
}
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
Add this to your Roo Code MCP configuration file. See Roo Code MCP docs for more info.
{
"mcpServers": {
"docfork": {
"type": "streamable-http",
"url": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_API_KEY"
}
}
}
}
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
Use the Add manually feature and fill in the JSON configuration. See Trae documentation for more details.
{
"mcpServers": {
"docfork": {
"url": "https://mcp.docfork.com/mcp"
}
}
}
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
Open Claude Desktop and navigate to Settings > Connectors > Add Custom Connector. Enter the name as Docfork and the remote MCP server URL as https://mcp.docfork.com/mcp.
Open Claude Desktop developer settings and edit your claude_desktop_config.json file. See Claude Desktop MCP docs for more info.
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
You can install Docfork through the Cline MCP Server Marketplace by searching for Docfork and clicking Install, or add it manually:
mcpServers:{
"mcpServers": {
"docfork": {
"url": "https://mcp.docfork.com/mcp",
"type": "streamableHttp",
"headers": {
"Authorization": "Bearer YOUR_API_KEY"
},
"alwaysAllow": ["search_docs", "fetch_doc"],
"disabled": false
}
}
}
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"],
"alwaysAllow": ["search_docs", "fetch_doc"],
"disabled": false
}
}
}
It can be installed via Zed Extensions or you can add this to your Zed settings.json. See Zed Context Server docs for more info.
{
"context_servers": {
"Docfork": {
"source": "custom",
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
To configure Docfork MCP in Augment Code, you can use either the graphical interface or manual configuration.
npx -y docfork@latestmcpServers array in the augment.advanced object"augment.advanced": {
"mcpServers": [
{
"name": "docfork",
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
]
}
See Gemini CLI Configuration for details.
~/.gemini/settings.jsonmcpServers object:{
"mcpServers": {
"docfork": {
"httpUrl": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_API_KEY",
"Accept": "application/json, text/event-stream"
}
}
}
}
Or, for a local server:
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
Run this command in your terminal. See Amp MCP docs for more info.
amp mcp add docfork https://mcp.docfork.com/mcp
amp mcp add docfork --header "DOCFORK_API_KEY=YOUR_API_KEY" https://mcp.docfork.com/mcp
See Qwen Coder MCP Configuration for details.
~/.qwen/settings.jsonmcpServers object:{
"mcpServers": {
"docfork": {
"httpUrl": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_API_KEY",
"Accept": "application/json, text/event-stream"
}
}
}
}
Or, for a local server:
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
See JetBrains AI Assistant Documentation for more details.
Settings -> Tools -> AI Assistant -> Model Context Protocol (MCP)+ Add.Command in the top-left corner and select the As JSON option{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
Apply to save changes.Use these alternatives to run the local Docfork MCP server with other runtimes.
{
"mcpServers": {
"docfork": {
"command": "bunx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
{
"mcpServers": {
"docfork": {
"command": "deno",
"args": ["run", "--allow-env=NO_DEPRECATION,TRACE_DEPRECATION", "--allow-net", "npm:docfork"]
}
}
}
Dockerfile:FROM node:18-alpine
WORKDIR /app
RUN npm install -g docfork
CMD ["docfork"]
docker build -t docfork .
{
"mcpServers": {
"docfork": {
"command": "docker",
"args": ["run", "-i", "--rm", "docfork"],
"transportType": "stdio"
}
}
}
Install the docfork.mcpb file and add it to your client. See MCP bundles docs for more info.
The configuration on Windows is slightly different. Use cmd to run npx:
{
"mcpServers": {
"docfork": {
"command": "cmd",
"args": ["/c", "npx", "-y", "docfork", "--api-key", "YOUR_API_KEY"],
"disabled": false,
"autoApprove": []
}
}
}
Add this to your Amazon Q Developer CLI configuration file. See Amazon Q Developer CLI docs for more details.
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
See Warp Model Context Protocol Documentation for details.
Settings > AI > Manage MCP servers.+ Add button.{
"Docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"],
"env": {},
"working_directory": null,
"start_on_launch": true
}
}
Save.Add the following configuration to Repository->Settings->Copilot->Coding agent->MCP configuration:
{
"mcpServers": {
"docfork": {
"type": "http",
"url": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_API_KEY"
},
"tools": ["search_docs", "fetch_doc"]
}
}
}
See the official GitHub documentation for more info.
Open ~/.copilot/mcp-config.json and add:
{
"mcpServers": {
"docfork": {
"type": "http",
"url": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_API_KEY"
},
"tools": ["search_docs", "fetch_doc"]
}
}
}
Or, for a local server:
{
"mcpServers": {
"docfork": {
"type": "local",
"command": "npx",
"tools": ["search_docs", "fetch_doc"],
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
See LM Studio MCP Support for more information.
Program (right side) > Install > Edit mcp.json.{
"mcpServers": {
"Docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
Save.See Visual Studio MCP Servers documentation for details.
{
"inputs": [],
"servers": {
"docfork": {
"type": "http",
"url": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_API_KEY"
}
}
}
}
Or, for a local server:
{
"mcp": {
"servers": {
"docfork": {
"type": "stdio",
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
}
Add this to your Crush configuration file. See Crush MCP docs for more info.
{
"$schema": "https://charm.land/crush.json",
"mcp": {
"docfork": {
"type": "http",
"url": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_API_KEY"
}
}
}
}
{
"$schema": "https://charm.land/crush.json",
"mcp": {
"docfork": {
"type": "stdio",
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
Open the "Settings" page, navigate to "Plugins," and enter:
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
See BoltAI's Documentation for more info.
Edit your Rovo Dev CLI MCP config by running: acli rovodev mcp
{
"mcpServers": {
"docfork": {
"url": "https://mcp.docfork.com/mcp"
}
}
}
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
{
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
See Qodo Gen docs for more details.
{
"mcpServers": {
"docfork": {
"command": "npx",
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"]
}
}
}
{
"mcpServers": {
"docfork": {
"url": "https://mcp.docfork.com/mcp"
}
}
}
See Local and Remote MCPs for Perplexity for more information.
Perplexity > SettingsConnectors.Add Connector.Advanced.Docfork{
"args": ["-y", "docfork", "--api-key", "YOUR_API_KEY"],
"command": "npx",
"env": {}
}
Save.Factory's droid supports MCP servers through its CLI. See Factory MCP docs for more info.
droid mcp add docfork https://mcp.docfork.com/mcp --type http --header "DOCFORK_API_KEY: YOUR_API_KEY"
droid mcp add docfork "npx -y docfork" --env DOCFORK_API_KEY=YOUR_API_KEY
Emdash is an orchestration layer for running multiple coding agents in parallel.
What Emdash provides: Global toggle: Settings → MCP → "Enable Docfork MCP". Per-workspace enable: The Docfork button in the ProviderBar.
What you still need to do: Configure your coding agent (Codex, Claude Code, Cursor, etc.) to connect to Docfork MCP. Emdash does not modify your agent's config.
See the Emdash repository for more information.
Docfork supports MCP OAuth specs. Change your endpoint to use OAuth:
- "url": "https://mcp.docfork.com/mcp"
+ "url": "https://mcp.docfork.com/mcp/oauth"
Note: OAuth is for remote HTTP connections only. View OAuth Guide →
use docforkAdd use docfork to any prompt:
Implement a secure authentication flow using Better Auth and Supabase. use docfork
Add a rule so Docfork stays active — skip the prompt suffix.
[!NOTE] Add Rule to Cursor (One-Click)
Copy rule:
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.
Now your AI fetches the latest docs automatically:
Add a Prisma schema for a multi-tenant SaaS and generate the client.
search_docsSearch documentation with context isolation. Set a Cabinet to restrict results to your approved stack.
| Parameter | Required | Description |
|---|---|---|
query | Yes | What you're building or debugging. Be specific. |
library | Yes | Library name (react) or exact owner/repo (facebook/react). |
tokens | No | Token budget for response size. "dynamic" or 100–10000. |
fetch_docFetch full Markdown content from a documentation URL when search chunks aren't enough.
| Parameter | Required | Description |
|---|---|---|
url | Yes | URL from search_docs results. Anchors and deep paths supported. |
owner/repo.Docfork is an open, community-driven catalogue. We review submissions but can't guarantee accuracy for every project. Spot an issue? Raise a GitHub issue or contact support.
MIT
FAQs
Up-to-date code documentation for AI agents.
The npm package docfork receives a total of 264 weekly downloads. As such, docfork popularity was classified as not popular.
We found that docfork demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.