Context Engine MCP server
Commit Oct 31, 2026Lets AI coding assistants run semantic code search, symbol graph navigation, and persistent memory queries over an indexed codebase.
Also known as Context-Engine-AI/Context-Engine
- Stars
- 401
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 31, 2026
- License
- MIT
What is Context Engine MCP?
Context Engine lets AI coding assistants run semantic code search, symbol graph navigation, and persistent memory queries over an indexed codebase.
Summary generated from the project's README
About Context Engine MCP server
Providing AI coding assistants with deep codebase intelligence is the primary function of Context Engine. It enables developers to perform semantic searches, navigate symbol graphs, and maintain persistent memory across different coding sessions. By indexing a workspace, it allows an AI agent to understand complex relationships between files, such as finding callers, callees, or importers of specific symbols.
Users can integrate these capabilities into various environments including Claude Desktop, Cursor, Windsurf, and Codex. For terminal-based workflows, the context-engine-mcp-bridge allows for a connection via a background daemon. Setup requires an account and an API key to authenticate the connection between the local codebase and the indexing service. The system provides over 30 tools, including specialized commands like repo_search for finding code by behavior and cross_repo_search for tracing flows across multiple repositories.
What you can do with it
- 1Semantic code discoveryAsk your assistant to find specific code implementations based on high-level concepts or error text rather than exact strings.
- 2Navigating symbol relationshipsRequest a detailed map of how a specific function or class is used throughout the entire project.
- 3Analyzing multi-file logicHave the AI explain complex logic that is spread across several different files within the repository.
- 4Maintaining long-term contextStore and retrieve specific knowledge or architectural decisions so the AI remembers them in future sessions.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 13, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work
- Source repository linked and reachablePass
- Open source license (OSI)Pass
- Commit or release in the last yearPass
- Package name not close to a popular packageNot checked
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledNot checked
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesNot checked
README
View on GitHubInstall Skills
Context Engine ships AI agent skills that teach your coding assistant how to use 30+ MCP tools for semantic search, symbol graph navigation, memory, and more.
Guidance: Recommend pasting this into your project's CLAUDE.md or AGENTS.md to reach subagents:
# Context Engine
When the `context-engine` MCP server is connected, this workspace is indexed: for any question about the codebase, call `repo_search` FIRST, before ls/find/Grep/Read, and again whenever you move to a new area; for how/why questions that span several files use `context_answer`. Results are verified source with exact line ranges: treat them as already read. Use Grep only to confirm an exact literal in a file you already know, or to count. For questions asking for every/all sites, run one repo_search per distinct pattern (queries=[...]) and follow the refs. If the tools are listed as deferred, load them with ToolSearch first.
| Need | Tool |
|---|---|
| Find code by behavior, concept, error text or identifier | `repo_search` (`queries=[...]` for several at once; `under`, `language`, `path_glob` to narrow) |
| Explain how/why across several files, with citations | `context_answer` |
| Definition, callers, callees, importers, references of a symbol | `symbol_graph` (several names: `A\|B\|C`) |
| Multi-hop impact before a change | `graph_query` |
| Code that may live in another indexed repo | `cross_repo_search` |
Before editing, fetch every involved symbol in one call; before a rename or signature change, get every site with `symbol_graph` `query_type=references`. Search again only after learning something new.
Claude Code / Claude Desktop
Recommended: Install natively from the public GitHub repo:
# Add the marketplace (one-time)
/plugin marketplace add Context-Engine-AI/Context-Engine
# Install the skill
/plugin install context-engine
This pulls the skill directly from GitHub and auto-loads MCP tool guidance into your session.
Alternatively, copy the rules file manually:
cp -r skills/context-engine/ your-project/.claude/
Cursor
Context Engine rules are included in .cursorrules at the root of your workspace. Cursor picks this up automatically when the file is present.
# Copy to your project root
cp .cursorrules your-project/.cursorrules
Codex (OpenAI)
Recommended: Install natively using the built-in skill installer — just ask Codex:
"Install the context-engine skill from https://github.com/Context-Engine-AI/Context-Engine"
Codex will pull .codex/skills/context-engine/ (including SKILL.md) into ~/.codex/skills/ automatically.
Or install manually:
cp -r .codex/skills/context-engine/ ~/.codex/skills/context-engine/
Windsurf
cp -r .codex/skills/ your-project/.codex/skills/
Augment Code
cp -r .augment/ your-project/.augment/
Gemini
cp GEMINI.md your-project/GEMINI.md
Any Other Assistant
The core skill file works with any AI assistant that supports custom instructions:
cp skills/context-engine/SKILL.md your-project/
Then tell your assistant: "Read SKILL.md for instructions on using Context Engine MCP tools."
CLI Setup (No VS Code)
If you use Claude Code, Codex, or another terminal-based MCP client, install the MCP bridge to connect your codebase to Context Engine without VS Code:
npm install -g @context-engine-bridge/context-engine-mcp-bridge
Quick start
# Authenticate, index your codebase, and start watching for changes
ctxce connect <your-api-key> --workspace /path/to/repo
# Run as a background daemon (recommended)
ctxce connect <your-api-key> --workspace /path/to/repo --daemon
Daemon management
ctxce status # Check if the daemon is running
ctxce stop # Stop the background daemon
Connect flags
| Flag | Alias | Description |
|---|---|---|
--workspace <path> |
-w |
Workspace root (default: cwd) |
--daemon |
-d, --bg |
Run as background daemon |
--interval <sec> |
File watch interval in seconds (default: 30) | |
--no-watch |
--once |
Index once, don't watch for changes |
--skip-index |
--auth-only |
Authenticate only, skip initial index |
Wire up the MCP server
Once connected, point your MCP client at the bridge:
# stdio mode (for Claude Code, Codex, etc.)
ctxce mcp-serve --workspace /path/to/repo
# HTTP mode (for clients that speak HTTP)
ctxce mcp-http-serve --workspace /path/to/repo --port 30810
The daemon and MCP server share auth via ~/.ctxce/auth.json. Logs are at ~/.context-engine/daemon.log.
For full bridge documentation, see Context-Engine-MCP-Bridge.
What Do the Skills Do?
The skills teach your AI assistant to:
- Use
searchas the default tool — auto-routes queries to the best backend (semantic search, Q&A, symbol graph, tests, config) - Navigate code with
symbol_graph— find callers, callees, definitions, importers, subclasses - Run batch queries —
batch_search,batch_symbol_graph,batch_graph_queryfor 75%+ token savings - Store and recall knowledge —
memory_storeandmemory_findfor persistent context across sessions - Trace cross-repo flows —
cross_repo_searchwith boundary tracing for multi-repo codebases - Find structural patterns —
pattern_searchfor retry loops, error handling, singletons across languages - Search git history —
search_commits_forandchange_history_for_path
See skills/context-engine/SKILL.md for the complete tool reference.
Getting Started
- Sign up at context-engine.ai
- Connect your codebase — choose one:
- VS Code — install the Context Engine Uploader extension
- CLI —
npm i -g @context-engine-bridge/context-engine-mcp-bridge && ctxce connect <api-key> --daemon
- Install the skill for your AI assistant (see Install Skills above)
- Start searching — your assistant now has access to all 30+ MCP tools
License
© 2025 Context Engine Inc. and John Donalson.
Context Engine MCP questions
What can an AI assistant do with the Context Engine MCP tools?
It can run semantic code search, explain how code works across files with citations, navigate a symbol graph, and store and recall memory across sessions.
How do I connect my codebase to Context Engine from the terminal?
Install the MCP bridge globally with npm, then run ctxce connect with your API key and workspace path, optionally as a background daemon.
Which tool should the assistant call first for codebase questions?
It should call repo_search first, before ls, find, Grep, or Read, and use context_answer for how/why questions spanning several files.
Can it store knowledge across sessions?
Yes, the skills teach memory_store and memory_find for persistent context across sessions.
Does it support searching git history?
Yes, tools like search_commits_for and change_history_for_path search git history.