Skip to content
Back to search

docfork

Docfork - Up-to-date docs for AI Coding Agents.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/docfork--docfork/badge.svg)](/listings/docfork--docfork)

HTML

<a href="/listings/docfork--docfork"><img src="/api/listings/docfork--docfork/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

> [!TIP] > Run `npx dgrep setup` to install automatically (use `--agent claude-code` to target one). Manual config below for other clients.

**Cursor** — <a href="https://cursor.com/en/install-mcp?name=docfork&config=eyJ1cmwiOiJodHRwczovL21jcC5kb2Nmb3JrLmNvbS9tY3AifQ%3D%3D"><img src="https://cursor.com/deeplink/mcp-install-dark.svg" height="20" alt="Add to Cursor"/></a>

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

**Claude Code**

claude mcp add --transport http docfork https://mcp.docfork.com/mcp/oauth

**OpenCode**

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

Don't see your client? [Setup guides for all 29 supported clients →](https://docfork.com/docs/mcp/setup)

**OAuth Authentication**

Docfork supports [MCP OAuth specs](https://modelcontextprotocol.io/specification/latest/basic/authorization). 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 full OAuth guide →](https://docfork.com/docs/authentication#oauth-20)_

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 17 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. {
  2. "name": "docfork",
  3. "owner": {
  4. "name": "Docfork",
  5. "email": "support@docfork.com"
  6. },
  7. "metadata": {
  8. "description": "Docfork plugins for Claude Code — documentation search for AI agents"
  9. },
  10. "plugins": [
  11. {
  12. "name": "docfork",
  13. "source": "./plugins/claude/docfork",
  14. "description": "Up-to-date and secure docs search for AI agents. Search 10,000+ libraries and lock your agent to your stack with Cabinets."
  15. }
  16. ]
  17. }
README.md · README · 218 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. <p align="center">
  2. <a href="https://docfork.com">
  3. <picture>
  4. <source srcset="logo_light.png" media="(prefers-color-scheme: dark)">
  5. <source srcset="logo_dark.png" media="(prefers-color-scheme: light)">
  6. <img src="logo_dark.png" alt="Docfork" height="40" />
  7. </picture>
  8. </a>
  9. </p>
  10. > [!CAUTION]
  11. > **Docfork has shut down as of June 14, 2026.**
  12. > The MCP server, CLI, and all hosted endpoints are offline and will not return. API keys no longer work, and `npx dgrep setup` will fail. Thank you to everyone who used the service.
  13. <p align="center">Up-to-date docs for AI coding agents.</p>
  14. AI agents hallucinate APIs, bloat context with stale docs, and write code against outdated signatures. Docfork serves up-to-date documentation directly in Cursor, Claude Code, and Windsurf.
  15. ### Without Docfork
  16. ```diff
  17. app.use('/api/*', jwt({ secret: ... }))
  18. - ^^^ removed in Hono v4
  19. ```
  20. ### With Docfork
  21. ```diff
  22. app.use('/api/*', bearerAuth({ verifyToken: ... }))
  23. + ^^^ current API, Hono v4.2
  24. ```
  25. ## Get Started
  26. ```bash
  27. npx dgrep setup
  28. ```
  29. Installs the Docfork MCP server in your IDE. Detects your installed agents and writes the config file; sign in to Docfork on first use, no API key needed. Target one with `--agent claude-code` (also: cursor, codex, opencode, vscode, windsurf, amp, factory, zed).
  30. Your agent now has two tools:
  31. | Tool | Returns |
  32. | ------------- | ---------------------------------------------------------------------- |
  33. | `search_docs` | Ranked documentation sections with titles, URLs, and relevance scores. |
  34. | `fetch_doc` | Full rendered markdown content from a documentation URL. |
  35. No prompt suffix needed:
  36. ```
  37. Set up server-side rendering with Next.js App Router.
  38. ```
  39. Or search from the terminal:
  40. ```bash
  41. dgrep search "middleware redirect based on authentication" -l vercel/next.js
  42. dgrep search "server actions with forms" -l vercel/next.js
  43. ```
  44. [Quickstart →](https://docfork.com/docs/quickstart) · [dgrep docs →](https://docfork.com/docs/dgrep) · [CLI reference →](https://docfork.com/docs/reference/cli)
  45. ### Your own docs
  46. Index any public or private GitHub repository as a [custom library](https://docfork.com/docs/libraries#custom-libraries). Your internal APIs, SDKs, and runbooks become searchable by your agents — same pipeline as public libraries. [GitHub integration setup →](https://docfork.com/docs/integrations)
  47. ## Teams
  48. Free: 1,000 requests/month per organization. For team rollout, commit the MCP config to your repo:
  49. ```json
  50. // .cursor/mcp.json (committed to git, picked up by every engineer)
  51. {
  52. "mcpServers": {
  53. "docfork": {
  54. "url": "https://mcp.docfork.com/mcp",
  55. "headers": {
  56. "DOCFORK_API_KEY": "YOUR_TEAM_API_KEY"
  57. }
  58. }
  59. }
  60. }
  61. ```
  62. Share API keys and [Cabinets](https://docfork.com/docs/cabinets) across your organization. Docfork doesn't store your code or prompts. [Security →](https://docfork.com/security) · [Pricing →](https://docfork.com/pricing)
  63. ## MCP Setup
  64. > [!TIP]
  65. > Run `npx dgrep setup` to install automatically (use `--agent claude-code` to target one). Manual config below for other clients.
  66. **Cursor** — <a href="https://cursor.com/en/install-mcp?name=docfork&config=eyJ1cmwiOiJodHRwczovL21jcC5kb2Nmb3JrLmNvbS9tY3AifQ%3D%3D"><img src="https://cursor.com/deeplink/mcp-install-dark.svg" height="20" alt="Add to Cursor"/></a>
  67. ```json
  68. {
  69. "mcpServers": {
  70. "docfork": {
  71. "url": "https://mcp.docfork.com/mcp",
  72. "headers": {
  73. "DOCFORK_API_KEY": "YOUR_API_KEY"
  74. }
  75. }
  76. }
  77. }
  78. ```
  79. **Claude Code**
  80. ```bash
  81. claude mcp add --transport http docfork https://mcp.docfork.com/mcp/oauth
  82. ```
  83. **OpenCode**
  84. ```jsonc
  85. {
  86. "mcp": {
  87. "docfork": {
  88. "type": "remote",
  89. "url": "https://mcp.docfork.com/mcp",
  90. "headers": { "DOCFORK_API_KEY": "YOUR_API_KEY" },
  91. "enabled": true,
  92. },
  93. },
  94. }
  95. ```
  96. Don't see your client? [Setup guides for all 29 supported clients →](https://docfork.com/docs/mcp/setup)
  97. **OAuth Authentication**
  98. Docfork supports [MCP OAuth specs](https://modelcontextprotocol.io/specification/latest/basic/authorization). Change your endpoint to use OAuth:
  99. ```diff
  100. - "url": "https://mcp.docfork.com/mcp"
  101. + "url": "https://mcp.docfork.com/mcp/oauth"
  102. ```
  103. _Note: OAuth is for remote HTTP connections only. [View full OAuth guide →](https://docfork.com/docs/authentication#oauth-20)_
  104. ## Agent Rule
  105. Add a rule so your agent calls Docfork MCP automatically. [Full rule and IDE-specific setup →](https://docfork.com/docs/mcp/best-practices)
  106. > [!NOTE]
  107. > **[Add Rule to Cursor (One-Click)](https://cursor.com/link/rule?name=docfork-policy&text=When%20writing%20or%20debugging%20code%20that%20involves%20third-party%20libraries%2C%20frameworks%2C%20or%20APIs%2C%20use%20Docfork%20MCP%20%60search_docs%60%20and%20%60fetch_doc%60%20tools%20rather%20than%20relying%20on%20training%20data.%0A%0A%2A%2ATwo%20defaults%20to%20follow%20every%20time%3A%2A%2A%0A-%20Start%20%60library%60%20with%20a%20short%20name%20or%20keyword%20%28e.g.%2C%20%60nextjs%60%2C%20%60zod%60%29.%20Use%20the%20%60owner%2Frepo%60%20from%20the%20result%20URL%20for%20follow-up%20calls%2C%20never%20guess%20it%20upfront.%0A-%20After%20finding%20a%20relevant%20result%2C%20call%20%60fetch_doc%60%20to%20get%20the%20full%20content.%20Search%20results%20are%20summaries%20only.%0A%0ASkip%20Docfork%20when%3A%0A-%20Language%20built-ins%2C%20general%20algorithms%2C%20syntax%20stable%20across%20versions%0A-%20Code%20or%20docs%20the%20user%20has%20already%20provided%20in%20context%0A%0AWhen%20uncertain%2C%20default%20to%20using%20Docfork.)**
  108. **Claude Code** — add to your `CLAUDE.md`:
  109. ```markdown
  110. ## Docfork policy
  111. Use Docfork MCP `search_docs` and `fetch_doc` tools for library/API docs, setup, and configuration questions.
  112. - 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.
  113. - After finding a relevant result, call `fetch_doc` to get the full content. Search results are summaries only.
  114. - Prefer Docfork results over training data when they conflict.
  115. ```
  116. <details>
  117. <summary>Full rule (all clients)</summary>
  118. ```markdown
  119. 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.
  120. **Two defaults to follow every time:**
  121. - 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.
  122. - After finding a relevant result, call `fetch_doc` to get the full content. Search results are summaries only.
  123. Skip Docfork when:
  124. - Language built-ins, general algorithms, syntax stable across versions
  125. - Code or docs the user has already provided in context
  126. When uncertain, default to using Docfork.
  127. ```
  128. </details>
  129. ## FAQ
  130. **How is Docfork different from Context7?**
  131. Both provide MCP servers and CLIs for searching library documentation. Here are the key differences:
  132. - **Stack scoping.** `dgrep init` reads your `package.json` and scopes all searches to your declared dependencies. Cabinets let you version-pin those libraries across a team.
  133. - **Resolve once, search many.** `dgrep init` resolves package names to canonical identifiers once and caches the mapping in `.dgrep/config.json`. No per-query resolution step.
  134. - **Hybrid search.** Semantic search and BM25 run in parallel, fused via Reciprocal Rank Fusion. AST-aware chunking preserves function boundaries.
  135. **Does Docfork store my code or prompts?**
  136. Your code and prompts never leave your machine. At search time, only the query and library name are sent to Docfork — queries are not stored. Indexed documentation content lives in an upstream vector store; private library content is end-to-end encrypted and deleted atomically when you remove the library. [Security →](https://docfork.com/security)
  137. **What libraries are supported?**
  138. Docfork maintains a curated catalog of popular frameworks. Add any public or private GitHub repository as a custom library. [Add custom libraries →](https://docfork.com/docs/libraries#custom-libraries)
  139. ## Docs
  140. - [Quickstart](https://docfork.com/docs/quickstart)
  141. - [How Docfork Works](https://docfork.com/docs/how-it-works)
  142. - [dgrep CLI](https://docfork.com/docs/dgrep)
  143. - [Docfork MCP](https://docfork.com/docs/mcp)
  144. - [Libraries](https://docfork.com/docs/libraries)
  145. - [Cabinets](https://docfork.com/docs/cabinets)
  146. - [Troubleshooting](https://docfork.com/docs/troubleshooting)
  147. ## Community
  148. - **[Changelog](https://docfork.com/changelog)**
  149. - **[X (Twitter)](https://x.com/docfork_ai)**
  150. - Found an issue? [Open a GitHub issue](https://github.com/docfork/docfork/issues) or [contact us](mailto:support@docfork.com).
  151. ## Star History
  152. [![Star History Chart](https://api.star-history.com/svg?repos=docfork/docfork&type=Date)](https://www.star-history.com/#docfork/docfork&Date)
  153. ## License
  154. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.