Give your AI coding agent accurate, up‑to‑date library documentation - so the code it writes actually works. No more hallucinated APIs. No more stale code.
Built on MCP. Works with Claude Code, Cursor, Windsurf, Cline, GitHub Copilot, OpenAI Codex, Antigravity, and any MCP‑compatible agent.
84% of developers use AI coding tools - yet trust in their accuracy has dropped to an all-time low. The #1 frustration: AI solutions that are almost right, but not quite. LLM frameworks ship breaking changes faster than any model can learn. You're asking an AI to write code for a world it hasn't seen yet.
† Stack Overflow Developer Survey 2025 · 49,000+ respondents
Without ProContext, your AI works from memory - like a closed-book exam. Memory goes stale. Answers go wrong. ProContext gives it the reference material it needs, exactly when it needs it.
Finds the right library and version from your query or imports. 2,000+ libraries indexed and ready.
Finds the exact section that's relevant - no need to know the exact name or where it lives.
Reads the full documentation or any specific page your agent needs - always the current version.
Maps the structure of available docs so your agent knows where to look before diving in.
Free and open source. No daemons. No config files to learn. No API keys. Run one command to install, add one config block, and you're done.
$ curl -fsSL https://procontext.dev/install.sh | bash
> irm https://procontext.dev/install.ps1 | iex
{ "mcpServers": { "procontext": { "command": "uvx", "args": ["procontext"] } } }
Everything you need to give your AI coding agent accurate, up-to-date library documentation. Self-host on your own infra, MIT licensed.
ProContext is built on the MCP standard. If your AI client supports MCP, ProContext works with it - no custom integrations needed.
High-accuracy documentation tools are proprietary. Open-source options sacrifice accuracy. ProContext fills that gap - open-source, high accuracy, free for individuals, SaaS for teams.
* Accuracy figures sourced from third-party benchmarks. Results may vary by benchmark methodology and use case. See published comparative analysis. · † Stack Overflow Developer Survey, 2025.