<strong>Index your codebase. AI searches instead of re-reading files. 94% token savings, reproducibly benchmarked.</strong>
Index your codebase. AI searches instead of re-reading files. 94% token savings, reproducibly benchmarked.
code-context-engine on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Metric — ResultConfiguration is passed through the environment: CCE_OLLAMA_URL. 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.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
{
"mcpServers": {
"code-context-engine": {
"command": "uvx",
"args": ["code-context-engine"],
"env": {
"CCE_OLLAMA_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CCE_OLLAMA_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.