Stop letting AI guess
your library's API
DocForge turns any library's documentation into a prompt-ready .context.md file, pinned to the exact version you're using. No more hallucinated APIs.
Version Pinned
Pinned to react-bits@2.1.4, not whatever the AI was trained on in 2023.
Gotcha Extraction
Surfaces "use client" requirements, deprecated APIs, and breaking changes.
Works Everywhere
Web app, CLI, MCP server, or VS Code extension — drop the result into Cursor or Claude.
Works with any registry or source
Get DocForge
Four ways to use DocForge — pick whichever fits your workflow.
Web App
No install required
Open DocForge in your browser, enter any package name or URL, and download the .context.md instantly.
CLI — dcf
npm · Node ≥ 18
Run dcf from your project directory. Appends the context file directly to your repo so every AI tool picks it up automatically.
npm install -g docforge-cli # then, inside any project: dcf react@18 dcf fastapi==0.115 dcf https://reactbits.dev/
MCP Server
Claude Desktop · Cursor · Windsurf
Let the AI call DocForge automatically mid-conversation. No manual trigger — the assistant detects it needs fresh docs and fetches them on its own.
// ~/.config/claude/claude_desktop_config.json
{
"mcpServers": {
"docforge": {
"command": "python",
"args": ["/path/to/docforge-mcp/server.py"],
"env": {
"DOCFORGE_BACKEND_URL": "https://api.docforge.dev"
}
}
}
}VS Code Extension
Works with Cursor too
Generate context files without leaving your editor. Right-click any file or use the command palette — the .context.md drops straight into your workspace.
# Install from the VS Code Marketplace ext install docforge # Or install the .vsix directly: code --install-extension docforge-1.0.0.vsix
How it works
From URL to usable context in under 90 seconds
Input anything
Package name, version, GitHub URL, docs URL, or paste raw docs.
Smart crawl
Playwright fetches JS-rendered sites. GitHub repos are ingested directly. Copy-paste libraries (shadcn, react-bits) are detected automatically.
AI structuring
Gemini extracts install commands, imports, props, usage examples, and common gotchas.
Ready to use
A .context.md file ready to drop into Cursor, Claude, Copilot, or any AI coding tool.
Works with everything
DocForge resolves the right documentation regardless of input format
# npm packages dcf react@18 dcf @tanstack/react-query@5 dcf @radix-ui/react-dialog # PyPI dcf fastapi==0.115 dcf pandas==2.2 # Other registries dcf crates:serde@1.0 dcf gem:rails@7.1 dcf pub:flutter_bloc@8 dcf nuget:Newtonsoft.Json@13 dcf mvn:com.google.guava:guava@32
# GitHub repos (fetches README + docs) dcf github.com/vercel/next.js dcf github.com/shadcn-ui/ui # Any docs URL dcf https://docs.stripe.com dcf https://reactbits.dev/ # Copy-paste / shadcn-style libraries # (auto-detected — no npm package needed) dcf react-bits dcf magicui dcf shadcn/ui
Why developers use it
AI tools like Cursor and Claude have a training cutoff — they don't know about library updates from the past year.
Pasting entire documentation pages into the context window is wasteful and unreliable.
DocForge distils only what matters: install command, imports, props, usage, and breaking changes.
Copy-paste libraries (shadcn, react-bits, magicui) aren't on npm — DocForge detects and handles them automatically.
One `.context.md` file in your repo means every AI session has accurate, version-pinned knowledge.
Works with 11 package registries and any URL — so no library is left behind.
Ready to fix your AI context?
Takes 30–90 seconds. Bring your own Gemini or Groq key.
npm install -g docforge-cli