Docfork Mcp
Fetch up-to-date library documentation into agent sessions—prefer the non-deprecated io.github.docfork/docfork registry id for new installs.
Overview
com.docfork/docfork-mcp is a MCP server for the Build phase that supplies up-to-date package documentation to your agent, though the registry id is deprecated in favor of io.github.docfork/docfork.
What is this MCP server?
- Docfork MCP serves fresh documentation formatted for AI consumption
- Registry entry explicitly DEPRECATED in favor of io.github.docfork/docfork
- Remote streamable-http at mcp.docfork.com plus optional npm stdio package docfork
- npm package docfork version 1.3.0 listed alongside server version 1.3.3
- GitHub source at github.com/docfork/docfork
- Server version 1.3.3; npm package docfork 1.3.0
- 1 streamable-http remote (mcp.docfork.com)
- Manifest states DEPRECATED: use io.github.docfork/docfork
Community signal: 488 GitHub stars.
What problem does it solve?
Agents often cite outdated APIs because training data lags releases, which slows indie builders integrating fast-moving libraries.
Who is it for?
Solo builders in Claude Code or Cursor who want live doc lookup while shipping integrations and want to know the maintained registry slug.
Skip if: Teams that already pinned internal doc mirrors, or anyone who should install io.github.docfork/docfork instead of this deprecated id.
What do I get? / Deliverables
After connecting Docfork MCP, your assistant can pull current docs context so you implement against real signatures and examples.
- In-session documentation snippets aligned to queried libraries
- Reduced integration errors from stale API assumptions
Recommended MCP Servers
Journey fit
Canonical shelf in Build/docs because the server’s purpose is keeping implementation references current while you code against third-party packages. Docs subphase is where agents need authoritative, version-aligned API surfaces instead of stale training cutoffs.
How it compares
Live documentation MCP feed, not an agent skill for planning or code review.
Common Questions / FAQ
Who is com.docfork/docfork-mcp for?
It is for developers using MCP agents who need fresh library documentation during implementation, with awareness that the canonical registry id moved to io.github.docfork/docfork.
When should I use com.docfork/docfork-mcp?
Use it during Build when you integrate third-party SDKs and want doc-backed answers; prefer the non-deprecated Docfork server id for new setups.
How do I add com.docfork/docfork-mcp to my agent?
Add remote https://mcp.docfork.com as streamable-http or install the npm docfork stdio package per your client docs, and migrate configs to io.github.docfork/docfork when possible.