Installing via Smithery

To install Docfork MCP Server for any client automatically via Smithery:

npx -y @smithery/cli@latest install @docfork/mcp --client <CLIENT_NAME> --key <YOUR_SMITHERY_KEY>

You can find your Smithery key in the Smithery.ai webpage.

Go to: Settings -> Cursor Settings -> Tools & Integrations -> Add a custom MCP server

Pasting the following config into your Cursor ~/.cursor/mcp.json file is the recommended approach. You can also install in a specific project by creating .cursor/mcp.json in your project folder. See Cursor MCP docs for more info.

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 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 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 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": []
    }
  }
}

Install in Augment Code

To configure Docfork MCP in Augment Code, follow these steps:

1. Press Cmd/Ctrl Shift P or go to the hamburger menu in the Augment panel
2. Select Edit Settings
3. Under Advanced, click Edit in settings.json
4. Add the server configuration to the mcpServers array in the augment.advanced object

"augment.advanced": {
    "mcpServers": [
        {
            "name": "docfork",
            "command": "npx",
            "args": ["-y", "docfork"]
        }
    ]
}

Once the MCP server is added, restart your editor. If you receive any errors, check the syntax to make sure closing brackets or commas are not missing.

Install in Roo Code

Add this to your Roo Code MCP configuration file. See Roo Code MCP docs for more info.

Roo Code Remote Server Connection

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

Roo Code Local Server Connection

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

Use the Add manually feature and fill in the JSON configuration information for that MCP server. For more details, visit the Trae documentation.

Trae Remote Server Connection

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

Trae Local Server Connection

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

You can configure Docfork MCP in Visual Studio 2022 by following the Visual Studio MCP Servers documentation.

Add this to your Visual Studio MCP config file (see the Visual Studio docs for details):

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

Or, for a local server:

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

For more information and troubleshooting, refer to the Visual Studio MCP Servers documentation.

See Gemini CLI Configuration for details.

1. Open the Gemini CLI settings file. The location is ~/.gemini/settings.json (where ~ is your home directory).
2. Add the following to the mcpServers object in your settings.json file:

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

Or, for a local server:

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

If the mcpServers object does not exist, create it.

Add this to your Crush configuration file. See Crush MCP docs for more info.

Crush Remote Server Connection (HTTP)

{
  "$schema": "https://charm.land/crush.json",
  "mcp": {
    "docfork": {
      "type": "http",
      "url": "https://mcp.docfork.com/mcp"
    }
  }
}

Crush Remote Server Connection (SSE)

{
  "$schema": "https://charm.land/crush.json",
  "mcp": {
    "docfork": {
      "type": "sse",
      "url": "https://mcp.docfork.com/sse"
    }
  }
}

Crush Local Server Connection

{
  "$schema": "https://charm.land/crush.json",
  "mcp": {
    "docfork": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "docfork"]
    }
  }
}

You can easily install Docfork through the Cline MCP Server Marketplace by following these instructions:

1. Open Cline.
2. Click the hamburger menu icon (☰) to enter the MCP Servers section.
3. Use the search bar within the Marketplace tab to find Docfork.
4. Click the Install button.

To configure Docfork MCP in Zencoder, follow these steps:

1. Go to the Zencoder menu (...)
2. From the dropdown menu, select Agent tools
3. Click on the Add custom MCP
4. Add the name and server configuration from below, and make sure to hit the Install button

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

Once the MCP server is added, you can easily continue using it.

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@latest"]
    }
  }
}

See Qodo Gen docs for more details.

1. Open Qodo Gen chat panel in VSCode or IntelliJ.
2. Click Connect more tools.
3. Click + Add new MCP.
4. Add the following configuration:

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

See JetBrains AI Assistant Documentation for more details.

1. In JetBrains IDEs go to Settings -> Tools -> AI Assistant -> Model Context Protocol (MCP)
2. Click + Add.
3. Click on Command in the top-left corner of the dialog and select the As JSON option from the list
4. Add this configuration and click OK

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

1. Click Apply to save changes.
2. The same way docfork could be added for JetBrains Junie in Settings -> Tools -> Junie -> MCP Settings

See Warp Model Context Protocol Documentation for details.

1. Navigate Settings > AI > Manage MCP servers.
2. Add a new MCP server by clicking the + Add button.
3. Paste the configuration given below:

{
  "Docfork": {
    "command": "npx",
    "args": ["-y", "docfork"],
    "env": {},
    "working_directory": null,
    "start_on_launch": true
  }
}

1. Click Save to apply the changes.

Add this to your Opencode configuration file. See Opencode MCP docs docs for more info.

Opencode Remote Server Connection

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

Opencode Local Server Connection

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

Using Docfork with Copilot Coding Agent

Add the following configuration to the mcp section of your Copilot Coding Agent configuration file Repository->Settings->Copilot->Coding agent->MCP configuration:

{
  "mcpServers": {
    "docfork": {
      "type": "http",
      "url": "https://mcp.docfork.com/mcp",
      "tools": ["get-library-docs"]
    }
  }
}

For more information, see the official GitHub documentation.

See Kiro Model Context Protocol Documentation for details.

1. Navigate Kiro > MCP Servers
2. Add a new MCP server by clicking the + Add button.
3. Paste the configuration given below:

{
  "mcpServers": {
    "Docfork": {
      "command": "npx",
      "args": ["-y", "docfork"],
      "env": {},
      "disabled": false,
      "autoApprove": []
    }
  }
}

1. Click Save to apply the changes.

See OpenAI Codex for more information.

Add the following configuration to your OpenAI Codex MCP server settings:

[mcp_servers.docfork]
args = ["-y", "docfork"]
command = "npx"

See LM Studio MCP Support for more information.

One-click install:

Manual set-up:

1. Navigate to Program (right side) > Install > Edit mcp.json.
2. Paste the configuration given below:

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

1. Click Save to apply the changes.
2. Toggle the MCP server on/off from the right hand side, under Program, or by clicking the plug icon at the bottom of the chat box.

See Local and Remote MCPs for Perplexity for more information.

1. Navigate Perplexity > Settings
2. Select Connectors.
3. Click Add Connector.
4. Select Advanced.
5. Enter Server Name: Docfork
6. Paste the following JSON in the text area:

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

1. Click Save.

The Docfork MCP server supports the following environment variables:

• DEFAULT_MINIMUM_TOKENS: Set the minimum token count for documentation retrieval (default: 10000)

For HTTP/SSE Transport Only

The following environment variables are only relevant when running the server as an HTTP/SSE service (not for standard npx usage):

• MCP_TRANSPORT: Set the transport type for MCP communication (default: stdio, options: streamable-http, stdio, sse)
• PORT: Set the port number for HTTP/SSE transport (default: 3000, only used when MCP_TRANSPORT is streamable-http or sse)

Standard node server configuration (most common):

{
  "mcpServers": {
    "docfork": {
      "command": "npx",
      "args": ["-y", "docfork@latest"],
      "env": {
        "DEFAULT_MINIMUM_TOKENS": "10000"
      }
    }
  }
}

HTTP/SSE server configuration (for custom deployments):

These environment variables are used when you're running your own instance of the Docfork server, not when connecting to remote servers. For remote server connections, use the URL-based configurations shown earlier in this README (e.g., "url": "https://mcp.docfork.com/mcp").

If you're self-hosting and want to run the server with HTTP/SSE transport:

# Set environment variables and run
MCP_TRANSPORT=streamable-http PORT=3000 npx -y docfork@latest

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

npx -y @modelcontextprotocol/inspector npx docfork

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.

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"]
    }
  }
}

Use the --experimental-fetch flag to bypass TLS-related problems:

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

1. Try adding @latest to the package name
2. Use bunx as an alternative to npx
3. Consider using deno as another alternative
4. Ensure you're using Node.js v18 or higher for native fetch support