@latest documentation and code examples to 9000+ libraries for LLMs and AI code editors in a singl…
@latest documentation and code examples to 9000+ libraries for LLMs and AI code editors in a singl…. That is what the docfork mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The server publishes 2 tools. What each one is for:
search_docs — Ranked documentation sections with titles, URLs, and relevance scoresfetch_doc — Full rendered markdown content from a documentation URLBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: DOCFORK_API_KEY, YOUR_TEAM_API_KEY, YOUR_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Docfork's toolset — search_docs, fetch_doc — is a fair guide to whether it matches your workflow. It is maintained by ai.smithery; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| search_docs | Ranked documentation sections with titles, URLs, and relevance scores. |
| fetch_doc | Full rendered markdown content from a documentation URL. |
// .cursor/mcp.json (committed to git, picked up by every engineer)
{
"mcpServers": {
"docfork": {
"url": "https://mcp.docfork.com/mcp",
"headers": {
"DOCFORK_API_KEY": "YOUR_TEAM_API_KEY"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| DOCFORK_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_TEAM_API_KEY | Credential the server authenticates with. | Yes |
| YOUR_API_KEY | Credential the server authenticates with. | Yes |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.