← Back to directory
C

Context

Community
Local-first documentation for AI agents — offline, instant, private doc retrieval.
GitHub source repository ↗
★ 382 Stars Category · Dev Tools Very popular Source revision efa171b4dbbb
56FMRS · C
Reliability
8/20
Security and permissions
10/20
Maintenance
9/20
Documentation
15/20
Setup experience
14/20

Context is a practical MCP server that provides local, reliable documentation retrieval for AI agents. It solves the common problem of AI using outdated docs and simplifies setup via a community registry. For developers, it's a time-saver and accuracy booster.

Read the FMRS scoring method →

Context is an MCP server backed by a community-driven package registry with 100+ pre-built documentation packages for popular libraries. When your AI agent needs documentation, it searches the registry, downloads the right package, and queries it locally — all automatically. Install once, configure once, then just ask your AI. Docs are stored as compact SQLite databases in ~/.context/packages/, making subsequent queries entirely local.

Tools

search_packages
Search the community registry for available documentation packages.
download_package
Download and install a pre-built documentation package from the registry.
get_docs
Retrieve documentation sections relevant to a topic from installed packages.
list_packages
List locally installed documentation packages.

Setup

  1. Install globally: npm install -g @neuledge/context
  2. Configure the MCP server for your AI client (e.g., Claude Desktop config file)
  3. Restart the client and start asking questions.
claude_desktop_config.json
{"mcpServers":{"context":{"command":"context","args":["serve"]}}}

Fit and risk

Best for

  • Developers who need fast, reliable, and private documentation retrieval
  • Developers using popular libraries like Next.js, React, Prisma
  • AI agent users in offline or low-latency environments
  • Teams that need to share custom documentation packages

Not for

  • Users who need automatic updates for all packages (versions are fixed and need manual updates)
  • Teams that prefer not to install through a global package manager
  • Users expecting a cloud-hosted service

Required permissions

  • Read/write to ~/.context directory (stores docs and auth data)
  • Network access (for first-time package downloads and registry queries)
  • Communication with clients via stdio or HTTP

Risks and side effects

  • Registry packages may contain outdated or inaccurate content (community-maintained)
  • Installed packages consume disk space (a few MB each)
  • In HTTP mode, if not restricted to localhost, could be exposed to other clients on the network

Troubleshooting

  1. Ensure it's installed globally: npm install -g @neuledge/context
  2. Check the command and arguments in your client's MCP config
  3. Verify network connectivity for first-time downloads
  4. Check that ~/.context directory exists and is writable
  5. Run context list to verify packages are installed

Use cases

Get up-to-date, version-specific library docs while developing
Access documentation offline or in restricted networks
Avoid AI providing wrong answers due to outdated docs
Build docs packages for private or internal libraries
Build packages from websites using llms.txt

Supported clients

Claude CodeFull support
Claude DesktopFull support
CursorFull support
OpenAI CodexFull support
VS CodeFull support
WindsurfFull support
ZedFull support
GooseFull support
OpenCodeFull support