RELATED 01
Context Mode
Keeps large tool output out of a coding agent's context by running it in a sandbox and indexing it locally.
34kGitHub stars
67k/wknpm downloads
103popularity score
Context
Version-specific library documentation served from local SQLite packages, searchable offline
By Neuledge TypeScript Local · stdio Knowledge and memoryDeveloper tools
52 popularity score ★ 437 ↓ 1.8k/wk
Connect your client
Local (npm)
Add in one click
Opens the app, which asks before it adds the server.
Or add it by command or config
FirstTerminal
npm install -g @neuledge/contextClaude CodeTerminal
claude mcp add context -- context serveClaude Desktopclaude_desktop_config.json
{
"mcpServers": {
"context": {
"command": "context",
"args": [
"serve"
]
}
}
}Cursor~/.cursor/mcp.json
{
"mcpServers": {
"context": {
"command": "context",
"args": [
"serve"
]
}
}
}VS Code.vscode/mcp.json
{
"servers": {
"context": {
"type": "stdio",
"command": "context",
"args": [
"serve"
]
}
}
}Codex~/.codex/config.toml
[mcp_servers.context]
command = "context"
args = ["serve"]Gemini CLITerminal
gemini mcp add --scope user context context -- serveWhat it does
Context is a documentation server from Neuledge. It keeps each library's docs as a SQLite database with full-text search, stored under ~/.context/packages/, and lets a coding assistant look up the version of a library you actually use instead of relying on what it learned in training.
When the assistant needs docs it does not have, it can search a community registry of over 100 prebuilt packages (npm, pip, Maven and Go libraries among them) and download one. From then on the lookups run on your machine with no network calls. The same `context` program also works as a CLI: `context add` builds a package from a git repository, a local folder, a site's llms.txt or a single web page, and the resulting .db file can be passed to teammates.
The registry address is not fixed. In version 1.3.2 the server reads a list of registry servers from ~/.context/config.json and falls back to https://api.context.neuledge.com when that file is missing; the `server` argument of the search and download tools picks one by name (config.ts). That lets a team point it at its own registry, which the README does not mention.
It speaks stdio by default. `context serve --http` starts a Streamable HTTP endpoint at /mcp instead, and `--libs` limits a session to a fixed set of installed packages.
What it needs
| Runtime | Node.js |
|---|
Node.js with npm, to install the package globally (`npm install -g @neuledge/context`) so the `context` program is on PATH. Network access to the registry the first time a package is downloaded; after that queries work offline. Building packages from git sources with `context add` needs git. The Docker image has to be built from a clone of the repository; it serves HTTP on port 8080, not stdio.
Limits
Searches use literal keywords combined with AND, plus quoted phrases; advanced FTS syntax is not supported, and empty or punctuation-only topics return nothing. Only docs in the registry or packages you build yourself can be searched. Packages added or removed with the CLI show up live only in stdio sessions; an HTTP server started with `--http` must be restarted to see them. With `--libs` set, `search_packages` and `download_package` are hidden. On Windows, replacing a package that is open can fail until the reader is closed.
Who it suits
Suits developers who want their coding assistant to answer from current, version-matched docs without sending queries to a hosted service, and teams that want to package internal or private docs as files they share. It reads and downloads documentation only, so it changes nothing beyond its own package folder. If you need docs that no one has packaged and you won't build them with `context add`, a server that fetches live web pages is a better fit. For shared network use, keep in mind the HTTP mode has no sign-in of its own.
Tools 3
get_docs- Searches one installed documentation package by keywords and returns the matching sections
search_packages- Looks up documentation packages available on a registry by ecosystem and name
download_package- Downloads a prebuilt documentation package from a registry and installs it locally