Docfork Mcp
Give your agent up-to-date library docs and code examples from a single MCP call so integration work stops relying on stale training data.
Overview
Docfork MCP is a MCP server for the Build phase that serves @latest documentation and code examples for 9000+ libraries to LLM-powered editors.
What is this MCP server?
- Surfaces @latest documentation and code examples for 9000+ libraries
- Single MCP entry point for LLMs and AI code editors
- Remote streamable-http server on Smithery (version 0.7.0)
- Open-source docfork/docfork-mcp repository on GitHub
- Reduces hallucinated API usage during day-to-day implementation
- Catalog covers 9000+ libraries per server description
- Published version 0.7.0 in server metadata
- Hosted as streamable-http remote on server.smithery.ai
Community signal: 488 GitHub stars.
What problem does it solve?
Your agent invents outdated APIs because it cannot fetch current library docs while you integrate packages.
Who is it for?
Solo developers who constantly add or upgrade dependencies and want doc lookup inside the agent instead of scattered browser tabs.
Skip if: Teams that only work inside a closed internal API with no public package docs to retrieve.
What do I get? / Deliverables
After connecting Docfork, the agent can pull fresh documentation and examples in-session so Build integrations align with real package behavior.
- In-context @latest docs and examples for supported libraries
- Fewer integration errors from stale training-data APIs
- Faster onboarding to unfamiliar packages during Build
Recommended MCP Servers
Journey fit
Accurate framework docs matter most while you are actively coding integrations and referencing APIs during Build. Docs is the canonical shelf because Docfork’s stated purpose is @latest documentation and examples for thousands of libraries in one MCP surface.
How it compares
Live library documentation MCP, not a brainstorming methodology or blockchain data bridge.
Common Questions / FAQ
Who is ai.smithery/docfork-mcp for?
Builders using Claude Code, Cursor, or similar agents who need current open-source library docs and examples while coding.
When should I use ai.smithery/docfork-mcp?
Use it during Build whenever you touch unfamiliar SDKs, upgrade versions, or need vetted snippets instead of guessed APIs.
How do I add ai.smithery/docfork-mcp to my agent?
Add the Smithery Docfork MCP URL to your client’s MCP servers list and configure the Authorization header with Bearer and your smithery_api_key.