Docfork
Fetch fresh, agent-oriented library and framework docs through MCP so Claude Code stops citing outdated package documentation mid-build.
Overview
Docfork is a Build-phase MCP server that delivers up-to-date developer documentation to AI agents over a local npm stdio connection.
What is this MCP server?
- npm stdio MCP package docfork v1.3.2
- Positioned explicitly for up-to-date docs consumed by AI agents
- GitHub-hosted project with MCP registry metadata and SVG icon
- stdio transport for local MCP clients (Cursor, Claude Code, Windsurf)
- npm package version 1.3.2
- stdio transport via registry identifier docfork
- Repository: github.com/docfork/docfork
Community signal: 487 GitHub stars.
What problem does it solve?
Your agent confidently uses old APIs and missing options because package docs changed after the model’s knowledge cutoff.
Who is it for?
Solo builders on Node-friendly MCP setups who routinely integrate third-party packages and need doc freshness in Cursor or Claude Code.
Skip if: Teams that want proprietary internal wiki hosting only, or workflows with no npm/Node MCP runtime available.
What do I get? / Deliverables
After you add the Docfork stdio server, the agent can pull newer documentation context while you integrate libraries and frameworks.
- Agent queries backed by newer public documentation
- Fewer integration errors from stale API references
Recommended MCP Servers
Journey fit
Docfork addresses the core build pain of wrong or stale docs during integration work—before you ship, review security, or optimize distribution. Docs subphase matches a server whose marketed value is “up-to-date docs for AI agents,” not deployment or monitoring.
How it compares
Live docs MCP integration via npm, not a static skills.sh coding skill or hosted doc2mcp remote for one repo.
Common Questions / FAQ
Who is Docfork for?
It is for AI-assisted developers who want an MCP-accessible doc source that stays closer to current package documentation than model memory alone.
When should I use Docfork?
Use it during builds and dependency upgrades whenever accurate, recent library docs would prevent wrong API usage or broken examples.
How do I add Docfork to my agent?
Register the docfork npm package as a stdio MCP server in your client (per Docfork’s install docs), typically requiring Node and the published v1.3.2 identifier.