{"id":29114721,"url":"https://github.com/docfork/docfork-mcp","last_synced_at":"2025-12-30T06:43:22.403Z","repository":{"id":297536711,"uuid":"996770457","full_name":"docfork/docfork-mcp","owner":"docfork","description":"Up-to-date Documentation for AI Agents.","archived":false,"fork":false,"pushed_at":"2025-12-23T15:05:19.000Z","size":5018,"stargazers_count":348,"open_issues_count":1,"forks_count":22,"subscribers_count":2,"default_branch":"main","last_synced_at":"2025-12-25T03:01:31.880Z","etag":null,"topics":["documentation","mcp","mcp-server","modelcontextprotocol","vibe-coding"],"latest_commit_sha":null,"homepage":"https://docfork.com","language":"TypeScript","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/docfork.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2025-06-05T12:44:12.000Z","updated_at":"2025-12-24T23:15:49.000Z","dependencies_parsed_at":null,"dependency_job_id":"17b36fac-bcb5-4d4a-bf99-847742f8d4c0","html_url":"https://github.com/docfork/docfork-mcp","commit_stats":null,"previous_names":["docfork/mcp","docfork/docfork-mcp"],"tags_count":23,"template":false,"template_full_name":null,"purl":"pkg:github/docfork/docfork-mcp","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/docfork%2Fdocfork-mcp","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/docfork%2Fdocfork-mcp/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/docfork%2Fdocfork-mcp/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/docfork%2Fdocfork-mcp/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/docfork","download_url":"https://codeload.github.com/docfork/docfork-mcp/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/docfork%2Fdocfork-mcp/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":28054223,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","status":"online","status_checked_at":"2025-12-26T02:00:06.189Z","response_time":55,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["documentation","mcp","mcp-server","modelcontextprotocol","vibe-coding"],"created_at":"2025-06-29T11:06:36.353Z","updated_at":"2025-12-26T12:00:49.404Z","avatar_url":"https://github.com/docfork.png","language":"TypeScript","readme":"![Cover](public/cover.png)\n\n# Docfork MCP - Up-to-date Documentation for AI Agents.\n\n[![smithery badge](https://smithery.ai/badge/@docfork/mcp)](https://smithery.ai/server/@docfork/mcp) [![Website](https://img.shields.io/badge/Website-docfork.com-%23088DCC)](https://docfork.com) [![NPM Version](https://img.shields.io/npm/v/docfork?color=red)](https://www.npmjs.com/package/docfork) [![MIT licensed](https://img.shields.io/npm/l/docfork)](./LICENSE)\n\n[![Install MCP Server](https://cursor.com/deeplink/mcp-install-light.svg)](https://cursor.com/en/install-mcp?name=docfork\u0026config=eyJ1cmwiOiJodHRwczovL21jcC5kb2Nmb3JrLmNvbS9tY3AifQ%3D%3D) [\u003cimg alt=\"Install in VS Code (http)\" src=\"https://img.shields.io/badge/Install%20in%20VS%20Code-0098FF?style=for-the-badge\u0026logo=visualstudiocode\u0026logoColor=white\"\u003e](https://insiders.vscode.dev/redirect?url=vscode%3Amcp%2Finstall%3F%7B%22name%22%3A%22docfork%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22http%3A%2F%2Fmcp.docfork.com%2Fmcp%22%7D)\n\n## ❌ The Problem: Expired Knowledge\n\n- Out of date code examples \u0026 stale data from year-old model training\n- Hallucinated syntax \u0026 APIs\n- Old or mismatched versions\n\n## ✅ The Solution: Up-to-date docs at warp speed\n\n- Always in sync with the latest version of docs\n- Accurate descriptions and code examples\n- Sub-second retrieval results (500ms @ p95) in your AI code editor\n\nDocfork MCP pulls @latest documentation and code examples straight from the source - and adds them right into your context.\n\nJust tell Cursor to **`use docfork`**:\n\n```txt\nCreate a basic Next.js app with the App Router. use docfork\n```\n\n## 🛠️ Installation\n\n### 📋 Requirements\n\n- Node.js ≥ v18\n- Cursor/Windsurf/Claude Desktop (any MCP client)\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstalling via Smithery\u003c/b\u003e\u003c/summary\u003e\n\n### Installing via Smithery\n\nTo install Docfork MCP Server for any client automatically via [Smithery](https://smithery.ai/server/@docfork/mcp):\n\n```bash\nnpx -y @smithery/cli@latest install @docfork/mcp --client \u003cCLIENT_NAME\u003e --key \u003cYOUR_SMITHERY_KEY\u003e\n```\n\nYou can find your Smithery key in the [Smithery.ai webpage](https://smithery.ai/server/@docfork/mcp).\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Cursor\u003c/b\u003e\u003c/summary\u003e\n  \nGo to: `Settings` -\u003e `Cursor Settings` -\u003e `Tools \u0026 Integrations` -\u003e `Add a custom MCP server`\n\nPasting 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](https://docs.cursor.com/context/model-context-protocol) for more info.\n\n#### Cursor Remote Server Connection\n\n[![Install MCP Server](https://cursor.com/deeplink/mcp-install-light.svg)](https://cursor.com/en/install-mcp?name=docfork\u0026config=eyJ1cmwiOiJodHRwczovL21jcC5kb2Nmb3JrLmNvbS9tY3AifQ%3D%3D)\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"url\": \"https://mcp.docfork.com/mcp\"\n    }\n  }\n}\n```\n\n#### Cursor Local Server Connection\n\n[![Install MCP Server](https://cursor.com/deeplink/mcp-install-light.svg)](https://cursor.com/en/install-mcp?name=docfork\u0026config=eyJjb21tYW5kIjoibnB4IC15IGRvY2ZvcmsiLCJhcmdzIjpbIi15IiwiZG9jZm9yayJdfQ%3D%3D)\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003eAlternative: Use Bun\u003c/summary\u003e\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"bunx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003eAlternative: Use Deno\u003c/summary\u003e\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"deno\",\n      \"args\": [\"run\", \"--allow-env\", \"--allow-net\", \"npm:docfork\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Claude Code\u003c/b\u003e\u003c/summary\u003e\n\n### Install in Claude Code\n\nRun this command. See [Claude Code MCP docs](https://docs.anthropic.com/en/docs/agents-and-tools/claude-code/tutorials#set-up-model-context-protocol-mcp) for more info.\n\n#### Claude Code Remote Server Connection\n\n```sh\nclaude mcp add --transport sse docfork https://mcp.docfork.com/sse\n```\n\n#### Claude Code Local Server Connection\n\n```sh\nclaude mcp add docfork -- npx -y docfork\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Claude Desktop\u003c/b\u003e\u003c/summary\u003e\n\n### Install in Claude Desktop\n\nAdd this to your Claude Desktop `claude_desktop_config.json` file. See [Claude Desktop MCP docs](https://modelcontextprotocol.io/quickstart/user) for more info.\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Windsurf\u003c/b\u003e\u003c/summary\u003e\n\n### Install in Windsurf\n\nAdd this to your Windsurf MCP config. See [Windsurf MCP docs](https://docs.windsurf.com/windsurf/mcp) for more info.\n\n#### Windsurf Remote Server Connection\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"serverUrl\": \"https://mcp.docfork.com/sse\"\n    }\n  }\n}\n```\n\n#### Windsurf Local Server Connection\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in VS Code\u003c/b\u003e\u003c/summary\u003e\n\n### Install in VS Code\n\nAdd this to your VS Code MCP config. See [VS Code MCP docs](https://code.visualstudio.com/docs/copilot/chat/mcp-servers) for more info.\n\n#### VS Code Remote Server Connection\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.docfork.com/mcp\"\n    }\n  }\n}\n```\n\n#### VS Code Local Server Connection\n\n```json\n{\n  \"servers\": {\n    \"docfork\": {\n      \"type\": \"stdio\",\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Zed\u003c/b\u003e\u003c/summary\u003e\n\n### Install in Zed\n\nOne-click install:\n→ Get the [Docfork Extension](https://zed.dev/extensions?query=Docfork\u0026filter=context-servers)\n\nOr Manual config (for power users):\n\n```json\n{\n  \"context_servers\": {\n    \"docfork\": {\n      \"command\": {\n        \"path\": \"npx\",\n        \"args\": [\"-y\", \"docfork\"]\n      },\n      \"settings\": {}\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in BoltAI\u003c/b\u003e\u003c/summary\u003e\n\n### Install in BoltAI\n\nOpen the \"Settings\" page of the app, navigate to \"Plugins,\" and enter the following JSON:\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\nMore info is available on [BoltAI's Documentation site](https://docs.boltai.com/docs/plugins/mcp-servers). For BoltAI on iOS, [see this guide](https://docs.boltai.com/docs/boltai-mobile/mcp-servers).\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eUsing Docker\u003c/b\u003e\u003c/summary\u003e\n\n### Using Docker\n\nIf you prefer to run the MCP server in a Docker container:\n\n1. **Build the Docker Image:**\n\n   First, create a `Dockerfile` in the project root (or anywhere you prefer):\n\n   \u003cdetails\u003e\n   \u003csummary\u003eClick to see Dockerfile content\u003c/summary\u003e\n\n   ```Dockerfile\n   FROM node:18-alpine\n\n   WORKDIR /app\n\n   # Install the latest version globally\n   RUN npm install -g docfork\n\n   # Expose default port if needed (optional, depends on MCP client interaction)\n   # EXPOSE 3000\n\n   # Default command to run the server\n   CMD [\"docfork\"]\n   ```\n\n   \u003c/details\u003e\n\n   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`:\n\n   ```bash\n   docker build -t docfork .\n   ```\n\n2. **Configure Your MCP Client:**\n\n   Update your MCP client's configuration to use the Docker command.\n\n   _Example for a cline_mcp_settings.json:_\n\n   ```json\n   {\n     \"mcpServers\": {\n       \"docfork\": {\n         \"autoApprove\": [],\n         \"disabled\": false,\n         \"timeout\": 60,\n         \"command\": \"docker\",\n         \"args\": [\"run\", \"-i\", \"--rm\", \"docfork-mcp\"],\n         \"transportType\": \"stdio\"\n       }\n     }\n   }\n   ```\n\n   _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._\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Windows\u003c/b\u003e\u003c/summary\u003e\n\n### Install in Windows\n\nThe 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`.\n\n```json\n{\n  \"mcpServers\": {\n    \"github.com/docfork/mcp\": {\n      \"command\": \"cmd\",\n      \"args\": [\"/c\", \"npx\", \"-y\", \"docfork@latest\"],\n      \"disabled\": false,\n      \"autoApprove\": []\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Augment Code\u003c/b\u003e\u003c/summary\u003e\n\n### Install in Augment Code\n\nTo configure Docfork MCP in Augment Code, follow these steps:\n\n1. Press Cmd/Ctrl Shift P or go to the hamburger menu in the Augment panel\n2. Select Edit Settings\n3. Under Advanced, click Edit in settings.json\n4. Add the server configuration to the `mcpServers` array in the `augment.advanced` object\n\n```json\n\"augment.advanced\": {\n    \"mcpServers\": [\n        {\n            \"name\": \"docfork\",\n            \"command\": \"npx\",\n            \"args\": [\"-y\", \"docfork\"]\n        }\n    ]\n}\n```\n\nOnce 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.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Roo Code\u003c/b\u003e\u003c/summary\u003e\n\n### Install in Roo Code\n\nAdd this to your Roo Code MCP configuration file. See [Roo Code MCP docs](https://docs.roocode.com/features/mcp/using-mcp-in-roo) for more info.\n\n#### Roo Code Remote Server Connection\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"type\": \"streamable-http\",\n      \"url\": \"https://mcp.docfork.com/mcp\"\n    }\n  }\n}\n```\n\n#### Roo Code Local Server Connection\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Trae\u003c/b\u003e\u003c/summary\u003e\n\nUse the Add manually feature and fill in the JSON configuration information for that MCP server.\nFor more details, visit the [Trae documentation](https://docs.trae.ai/ide/model-context-protocol?_lang=en).\n\n#### Trae Remote Server Connection\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"url\": \"https://mcp.docfork.com/mcp\"\n    }\n  }\n}\n```\n\n#### Trae Local Server Connection\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Visual Studio 2022\u003c/b\u003e\u003c/summary\u003e\n\nYou can configure Docfork MCP in Visual Studio 2022 by following the [Visual Studio MCP Servers documentation](https://learn.microsoft.com/visualstudio/ide/mcp-servers?view=vs-2022).\n\nAdd this to your Visual Studio MCP config file (see the [Visual Studio docs](https://learn.microsoft.com/visualstudio/ide/mcp-servers?view=vs-2022) for details):\n\n```json\n{\n  \"mcp\": {\n    \"servers\": {\n      \"docfork\": {\n        \"type\": \"http\",\n        \"url\": \"https://mcp.docfork.com/mcp\"\n      }\n    }\n  }\n}\n```\n\nOr, for a local server:\n\n```json\n{\n  \"mcp\": {\n    \"servers\": {\n      \"docfork\": {\n        \"type\": \"stdio\",\n        \"command\": \"npx\",\n        \"args\": [\"-y\", \"docfork\"]\n      }\n    }\n  }\n}\n```\n\nFor more information and troubleshooting, refer to the [Visual Studio MCP Servers documentation](https://learn.microsoft.com/visualstudio/ide/mcp-servers?view=vs-2022).\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Gemini CLI\u003c/b\u003e\u003c/summary\u003e\n\nSee [Gemini CLI Configuration](https://github.com/google-gemini/gemini-cli/blob/main/docs/cli/configuration.md) for details.\n\n1.  Open the Gemini CLI settings file. The location is `~/.gemini/settings.json` (where `~` is your home directory).\n2.  Add the following to the `mcpServers` object in your `settings.json` file:\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"httpUrl\": \"https://mcp.docfork.com/mcp\"\n    }\n  }\n}\n```\n\nOr, for a local server:\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\nIf the `mcpServers` object does not exist, create it.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Crush\u003c/b\u003e\u003c/summary\u003e\n\nAdd this to your Crush configuration file. See [Crush MCP docs](https://github.com/charmbracelet/crush#mcps) for more info.\n\n#### Crush Remote Server Connection (HTTP)\n\n```json\n{\n  \"$schema\": \"https://charm.land/crush.json\",\n  \"mcp\": {\n    \"docfork\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.docfork.com/mcp\"\n    }\n  }\n}\n```\n\n#### Crush Remote Server Connection (SSE)\n\n```json\n{\n  \"$schema\": \"https://charm.land/crush.json\",\n  \"mcp\": {\n    \"docfork\": {\n      \"type\": \"sse\",\n      \"url\": \"https://mcp.docfork.com/sse\"\n    }\n  }\n}\n```\n\n#### Crush Local Server Connection\n\n```json\n{\n  \"$schema\": \"https://charm.land/crush.json\",\n  \"mcp\": {\n    \"docfork\": {\n      \"type\": \"stdio\",\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\n\u003cb\u003eInstall in Cline\u003c/b\u003e\n\u003c/summary\u003e\n\nYou can easily install Docfork through the [Cline MCP Server Marketplace](https://cline.bot/mcp-marketplace) by following these instructions:\n\n1. Open **Cline**.\n2. Click the hamburger menu icon (☰) to enter the **MCP Servers** section.\n3. Use the search bar within the **Marketplace** tab to find _Docfork_.\n4. Click the **Install** button.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Zencoder\u003c/b\u003e\u003c/summary\u003e\n\nTo configure Docfork MCP in Zencoder, follow these steps:\n\n1. Go to the Zencoder menu (...)\n2. From the dropdown menu, select Agent tools\n3. Click on the Add custom MCP\n4. Add the name and server configuration from below, and make sure to hit the Install button\n\n```json\n{\n  \"command\": \"npx\",\n  \"args\": [\"-y\", \"docfork@latest\"]\n}\n```\n\nOnce the MCP server is added, you can easily continue using it.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Amazon Q Developer CLI\u003c/b\u003e\u003c/summary\u003e\n\nAdd this to your Amazon Q Developer CLI configuration file. See [Amazon Q Developer CLI docs](https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-mcp-configuration.html) for more details.\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork@latest\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Qodo Gen\u003c/b\u003e\u003c/summary\u003e\n\nSee [Qodo Gen docs](https://docs.qodo.ai/qodo-documentation/qodo-gen/qodo-gen-chat/agentic-mode/agentic-tools-mcps) for more details.\n\n1. Open Qodo Gen chat panel in VSCode or IntelliJ.\n2. Click Connect more tools.\n3. Click + Add new MCP.\n4. Add the following configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"url\": \"https://mcp.docfork.com/mcp\"\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in JetBrains AI Assistant\u003c/b\u003e\u003c/summary\u003e\n\nSee [JetBrains AI Assistant Documentation](https://www.jetbrains.com/help/ai-assistant/configure-an-mcp-server.html) for more details.\n\n1. In JetBrains IDEs go to `Settings` -\u003e `Tools` -\u003e `AI Assistant` -\u003e `Model Context Protocol (MCP)`\n2. Click `+ Add`.\n3. Click on `Command` in the top-left corner of the dialog and select the As JSON option from the list\n4. Add this configuration and click `OK`\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\n5. Click `Apply` to save changes.\n6. The same way docfork could be added for JetBrains Junie in `Settings` -\u003e `Tools` -\u003e `Junie` -\u003e `MCP Settings`\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Warp\u003c/b\u003e\u003c/summary\u003e\n\nSee [Warp Model Context Protocol Documentation](https://docs.warp.dev/knowledge-and-collaboration/mcp#adding-an-mcp-server) for details.\n\n1. Navigate `Settings` \u003e `AI` \u003e `Manage MCP servers`.\n2. Add a new MCP server by clicking the `+ Add` button.\n3. Paste the configuration given below:\n\n```json\n{\n  \"Docfork\": {\n    \"command\": \"npx\",\n    \"args\": [\"-y\", \"docfork\"],\n    \"env\": {},\n    \"working_directory\": null,\n    \"start_on_launch\": true\n  }\n}\n```\n\n4. Click `Save` to apply the changes.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Opencode\u003c/b\u003e\u003c/summary\u003e\n\nAdd this to your Opencode configuration file. See [Opencode MCP docs](https://opencode.ai/docs/mcp-servers) docs for more info.\n\n#### Opencode Remote Server Connection\n\n```json\n\"mcp\": {\n  \"docfork\": {\n    \"type\": \"remote\",\n    \"url\": \"https://mcp.docfork.com/mcp\",\n    \"enabled\": true\n  }\n}\n```\n\n#### Opencode Local Server Connection\n\n```json\n{\n  \"mcp\": {\n    \"docfork\": {\n      \"type\": \"local\",\n      \"command\": [\"npx\", \"-y\", \"docfork\"],\n      \"enabled\": true\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\n\u003csummary\u003e\u003cb\u003eInstall in Copilot Coding Agent\u003c/b\u003e\u003c/summary\u003e\n\n## Using Docfork with Copilot Coding Agent\n\nAdd the following configuration to the `mcp` section of your Copilot Coding Agent configuration file Repository-\u003eSettings-\u003eCopilot-\u003eCoding agent-\u003eMCP configuration:\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.docfork.com/mcp\",\n      \"tools\": [\"get-library-docs\"]\n    }\n  }\n}\n```\n\nFor more information, see the [official GitHub documentation](https://docs.github.com/en/enterprise-cloud@latest/copilot/how-tos/agents/copilot-coding-agent/extending-copilot-coding-agent-with-mcp).\n\n\u003c/details\u003e\n  \n\u003cdetails\u003e\n  \n\u003csummary\u003e\u003cb\u003eInstall in Kiro\u003c/b\u003e\u003c/summary\u003e\n\nSee [Kiro Model Context Protocol Documentation](https://kiro.dev/docs/mcp/configuration/) for details.\n\n1. Navigate `Kiro` \u003e `MCP Servers`\n2. Add a new MCP server by clicking the `+ Add` button.\n3. Paste the configuration given below:\n\n```json\n{\n  \"mcpServers\": {\n    \"Docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"],\n      \"env\": {},\n      \"disabled\": false,\n      \"autoApprove\": []\n    }\n  }\n}\n```\n\n4. Click `Save` to apply the changes.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in OpenAI Codex\u003c/b\u003e\u003c/summary\u003e\n\nSee [OpenAI Codex](https://github.com/openai/codex) for more information.\n\nAdd the following configuration to your OpenAI Codex MCP server settings:\n\n```toml\n[mcp_servers.docfork]\nargs = [\"-y\", \"docfork\"]\ncommand = \"npx\"\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in LM Studio\u003c/b\u003e\u003c/summary\u003e\n\nSee [LM Studio MCP Support](https://lmstudio.ai/blog/lmstudio-v0.3.17) for more information.\n\n#### One-click install:\n\n[![Add MCP Server docfork to LM Studio](https://files.lmstudio.ai/deeplink/mcp-install-light.svg)](https://lmstudio.ai/install-mcp?name=docfork\u0026config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsImRvY2ZvcmsiXX0%3D)\n\n#### Manual set-up:\n\n1. Navigate to `Program` (right side) \u003e `Install` \u003e `Edit mcp.json`.\n2. Paste the configuration given below:\n\n```json\n{\n  \"mcpServers\": {\n    \"Docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\n3. Click `Save` to apply the changes.\n4. 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.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eInstall in Perplexity Desktop\u003c/b\u003e\u003c/summary\u003e\n\nSee [Local and Remote MCPs for Perplexity](https://www.perplexity.ai/help-center/en/articles/11502712-local-and-remote-mcps-for-perplexity) for more information.\n\n1. Navigate `Perplexity` \u003e `Settings`\n2. Select `Connectors`.\n3. Click `Add Connector`.\n4. Select `Advanced`.\n5. Enter Server Name: `Docfork`\n6. Paste the following JSON in the text area:\n\n```json\n{\n  \"args\": [\"-y\", \"docfork\"],\n  \"command\": \"npx\",\n  \"env\": {}\n}\n```\n\n7. Click `Save`.\n\u003c/details\u003e\n\n## 🔨 Available Tools\n\nDocfork MCP provides different tools depending on the client type:\n\n### MCP Clients (Cursor, Claude Code, Claude Desktop, VS Code, etc.)\n\n- `docfork_search_docs`: Search for documentation across the web, GitHub, and other sources.\n  - `query` (required): Query for documentation. Include language/framework/library names.\n  - `docforkIdentifier` (optional): Library identifier in author/repo format (e.g., 'facebook/react', 'vercel/next.js'). Use this to search INSIDE a specific library's documentation for focused, accurate results. Extract from URLs in search results and include in subsequent searches about that library.\n  - `tokens` (optional): Token budget control: 'dynamic' or number (100-10000).\n\n- `docfork_read_url`: Read the content of a documentation URL as markdown/text.\n  - `url` (required): The URL of the webpage to read (typically from `docfork_search_docs` results).\n\n### OpenAI ChatGPT Connectors\n\nFor OpenAI ChatGPT integration, Docfork provides OpenAI MCP specification-compliant tools:\n\n- `search`: Search for documents using semantic search. Returns a list of relevant search results.\n  - `query` (required): Search query string. Natural language queries work best for semantic search.\n\n- `fetch`: Retrieve complete document content by ID for detailed analysis and citation.\n  - `id` (required): URL or unique identifier for the document to fetch.\n\n\u003e **Note:**  \n\u003e The OpenAI tools (`search` and `fetch`) automatically format their responses for ChatGPT connectors and are compatible with deep research workflows.\n\n## 💡 Tips\n\n### Add a Rule\n\nIf you don't want to add `use docfork` to every prompt, you can define a simple rule from your `Cursor Settings \u003e Rules` section in Cursor (or the equivalent in your MCP client) to auto-invoke Docfork on any code question:\n\n```markdown\n---\nalwaysApply: true\n---\n\nwhen the user requests code examples, setup or configuration steps, or library/API documentation\nuse docfork.\n```\n\nFrom then on you'll get Docfork's docs in any related conversation without typing anything extra. You can add your use cases to the match part.\n\n### Use Specific Library Names\n\nWhen you know exactly which library you want to use, be specific in your prompts. This helps Docfork find the right documentation faster and more accurately:\n\n```txt\nimplement basic authentication with supabase. use docfork\n```\n\n```txt\ncreate a Next.js middleware for rate limiting. use docfork\n```\n\n```txt\nconfigure Tailwind CSS with custom typography. use docfork\n```\n\nThe more specific you are about the library and what you want to accomplish, the better documentation you'll receive.\n\n## Development\n\nClone the project and install dependencies:\n\n```bash\nnpm i\n```\n\nBuild:\n\n```bash\nnpm run build\n```\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eEnvironment Variables\u003c/b\u003e\u003c/summary\u003e\n\nThe Docfork MCP server supports the following environment variables:\n\n- `DEFAULT_MINIMUM_TOKENS`: Set the minimum token count for documentation retrieval (default: 10000)\n\n### Transport Configuration\n\n- `MCP_TRANSPORT`: Set the transport type for MCP communication (default: `stdio`)\n  - `stdio` (default): Standard input/output transport for local subprocess communication—simple and reliable with no port management\n  - `streamable-http`: HTTP-based transport with SSE support for multiple client connections, server-initiated messages, and session management\n- `PORT`: Set the base port number for HTTP transport (default: `3000`)\n  - Only used when `MCP_TRANSPORT` is `streamable-http`\n  - If the specified port is unavailable, the server automatically finds the next available port (tries up to 10 consecutive ports)\n\n#### When to Use Streamable HTTP\n\nUse `MCP_TRANSPORT=streamable-http` for remote/hosted servers or when you need multiple client connections, server-initiated messages, or session management. For more details, see the [modelcontextprotocol.io transport documentation](https://modelcontextprotocol.io/specification/latest/basic/transports).\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eExample Configurations\u003c/b\u003e\u003c/summary\u003e\n\n**Standard configuration with default transport (stdio):**\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork@latest\"],\n      \"env\": {\n        \"DEFAULT_MINIMUM_TOKENS\": \"10000\"\n      }\n    }\n  }\n}\n```\n\n**Using streamable-http transport (for advanced features):**\n\nFor remote servers or when you need multiple connections and server-initiated messages:\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork@latest\"],\n      \"env\": {\n        \"MCP_TRANSPORT\": \"streamable-http\"\n      }\n    }\n  }\n}\n```\n\n**Custom port configuration (for streamable-http):**\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork@latest\"],\n      \"env\": {\n        \"MCP_TRANSPORT\": \"streamable-http\",\n        \"PORT\": \"3000\"\n      }\n    }\n  }\n}\n```\n\nNote: If the specified port is already in use, the server automatically finds the next available port.\n\n**Self-hosted HTTP server:**\n\nThese 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\"`).\n\n```bash\n# run with streamable-http transport (opt-in)\nMCP_TRANSPORT=streamable-http PORT=3000 npx -y docfork@latest\n\n# run with stdio (default)\nnpx -y docfork@latest\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eLocal Configuration Example\u003c/b\u003e\u003c/summary\u003e\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"node\",\n      \"args\": [\"/path/to/folder/docfork/dist/index.js\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eTesting with MCP Inspector\u003c/b\u003e\u003c/summary\u003e\n\n```bash\nnpm run inspect\n```\n\n\u003c/details\u003e\n\n## 🚨 Troubleshooting\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eModule Not Found Errors\u003c/b\u003e\u003c/summary\u003e\n\nIf you encounter `ERR_MODULE_NOT_FOUND`, try using `bunx` instead of `npx`:\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"bunx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\nThis often resolves module resolution issues in environments where `npx` doesn't properly install or resolve packages.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eESM Resolution Issues\u003c/b\u003e\u003c/summary\u003e\n\nFor errors like `Error: Cannot find module 'uriTemplate.js'`, try the `--experimental-vm-modules` flag:\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"--node-options=--experimental-vm-modules\", \"docfork\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eTLS/Certificate Issues\u003c/b\u003e\u003c/summary\u003e\n\nUse the `--experimental-fetch` flag to bypass TLS-related problems:\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"--node-options=--experimental-fetch\", \"docfork\"]\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003ePort Already In Use (EADDRINUSE)\u003c/b\u003e\u003c/summary\u003e\n\nIf you see an error like `Error: listen EADDRINUSE: address already in use :::3000`, this means you have `MCP_TRANSPORT=streamable-http` configured:\n\n**Option 1: Use default stdio transport (recommended)**\n\nRemove the `MCP_TRANSPORT` environment variable to use the default stdio transport, which avoids port conflicts:\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"]\n    }\n  }\n}\n```\n\n**Option 2: Automatic port allocation**\n\nThe server automatically finds an available port if the default port is in use. You'll see a message like:\n\n```\nPort 3000 is already in use, using port 3001 instead\n```\n\n**Option 3: Configure a custom port**\n\n```json\n{\n  \"mcpServers\": {\n    \"docfork\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"docfork\"],\n      \"env\": {\n        \"MCP_TRANSPORT\": \"streamable-http\",\n        \"PORT\": \"3500\"\n      }\n    }\n  }\n}\n```\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eGeneral MCP Client Errors\u003c/b\u003e\u003c/summary\u003e\n\n1. Try adding `@latest` to the package name\n2. Use `bunx` as an alternative to `npx`\n3. Consider using `deno` as another alternative\n4. Ensure you're using Node.js v18 or higher for native fetch support\n\n\u003c/details\u003e\n\n## ⚠️ Disclaimer\n\nDocfork 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.\n\nIf you spot content that is suspicious, inappropriate, or potentially harmful, please contact us.\n\nBy using Docfork, you agree to do so at your own discretion and risk.\n\n## 🌟 Let's Connect!\n\nStay in the loop and meet the community:\n\n- 🐦 Follow us on [X](https://x.com/docfork_ai) for product news and updates\n- 🌐 Visit our [Website](https://docfork.com)\n\n## Star History\n\n[![Star History Chart](https://api.star-history.com/svg?repos=docfork/mcp\u0026type=Date)](https://www.star-history.com/#docfork/mcp\u0026Date)\n\n## License\n\nMIT\n","funding_links":[],"categories":["📚 Projects (1974 total)","TypeScript","HarmonyOS","Search \u0026 Data Extraction","MCP Clients"],"sub_categories":["MCP Servers","Windows Manager","How to Submit","IDE Extensions \u0026 Code Assistants"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdocfork%2Fdocfork-mcp","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdocfork%2Fdocfork-mcp","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdocfork%2Fdocfork-mcp/lists"}