Install
$ agentstack add mcp-acc-c-code-context-engine ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Code Context Engine
Code Context Engine is a local-first code index and MCP server for AI coding agents. It indexes a local repository, returns compact context before an edit, fetches exact source on demand, and reports likely impact afterward.
Source code stays on the local machine unless an optional external provider is configured to do otherwise.
Features
- Indexes Rust, Java, TypeScript/TSX, and Python source.
- Stores chunks, symbols, graph edges, search data, and project memories in
file-backed SQLite storage.
- Provides lexical search, deterministic local hash-vector search, reference
lookup, context expansion, and impact analysis.
- Exposes the workflow through both a
contextCLI and an MCP stdio server. - Supports optional compiler or type-checker reference providers.
- Runs without Java, Node.js, Python, or external providers for the basic local
indexing workflow.
Install
Download a release
- Open GitHub Releases.
- Download the archive matching your operating system and architecture.
- Extract the archive.
- Run
context --helpon Linux/macOS orcontext.exe --helpon Windows.
Each archive has a matching .sha256 file. See [Installation](docs/installation.md) for checksum commands and PATH setup.
Build from source
Install stable Rust, clone this repository, and run:
cargo build --locked --release -p context-cli
The executable is written to target/release/context on Linux/macOS or target/release/context.exe on Windows.
You can also install it into Cargo's binary directory:
cargo install --locked --path crates/context-cli
Quick Start
Index a local project into a file-backed SQLite database:
context index --repo /absolute/path/to/project --db /absolute/path/to/project/.context/code-index.sqlite
Search the index:
context search --db /absolute/path/to/project/.context/code-index.sqlite --query "authentication middleware" --limit 10
Gather context before editing:
context pre-change-context --repo /absolute/path/to/project --db /absolute/path/to/project/.context/code-index.sqlite --task "change authentication middleware" --limit 10 --depth 1
Use context get-chunk with a returned chunk ID when exact source text is needed. Run context post-change-impact after the edit to inspect likely affected symbols and recommended tests.
On Windows, absolute paths such as C:\work\project are accepted. Quote paths that contain spaces.
Start the MCP Server
The MCP entry point is:
context mcp-stdio
Example MCP client configuration:
{
"mcpServers": {
"code-context-engine": {
"command": "/absolute/path/to/context",
"args": ["mcp-stdio"]
}
}
}
Use context.exe on Windows. If the executable is already on PATH, the command may simply be context. See [MCP setup](docs/mcp-setup.md) for smoke tests, path guidance, and the recommended AI workflow.
AI Workflow
- Run
index_repofor the local repository and a file-backed SQLite path. - Run
pre_change_contextbefore a non-trivial edit. - Fetch selected source with
get_chunk. - Edit with normal development tools and run the project's tests.
- Run
post_change_impactwith the Git diff or explicit changed files.
Built-in graph evidence is heuristic. Treat it as investigation guidance, not as proof that every dependency has been found.
Development
Run the public quality gates from the workspace root:
cargo fmt --all -- --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
GitHub Actions runs these checks on pushes and pull requests. Tags matching v* build downloadable Windows, Linux, and macOS release archives.
Documentation
- [Installation](docs/installation.md)
- [MCP setup](docs/mcp-setup.md)
- [CLI guide](docs/cli.md)
- [Tool contracts](docs/tool-contracts.md)
- [Agent workflow](docs/agent-workflow.md)
- [Architecture](docs/architecture.md)
- [Release process](docs/releasing.md)
- [Roadmap](docs/roadmap.md)
- [Changelog](CHANGELOG.md)
License
Apache-2.0. See [LICENSE](LICENSE) and [NOTICE](NOTICE).
Source & license
This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: acc-c
- Source: acc-c/code-context-engine
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.