The Context Engine MCP Server is a local-first, agent-agnostic platform for workspace indexing, semantic search, AI-assisted planning, code review, memory management, and security validation.
Workspace Indexing & Retrieval
Index 50+ file types for semantic search (
index_workspace,semantic_search,codebase_retrieval)Retrieve full/partial file contents (
get_file) and token-aware context for AI prompts (get_context_for_prompt)Enhance simple prompts into detailed, codebase-aware prompts (
enhance_prompt)Manage index health: check status, reindex, or clear (
index_status,reindex_workspace,clear_index)
Memory Management
Persist preferences, architecture decisions, and project facts across sessions (
add_memory,list_memories)
Planning & Execution
Generate AI-powered implementation plans with dependency graphs, risk assessments, and Mermaid diagrams (
create_plan,refine_plan,visualize_plan)Execute plan steps with AI-generated code changes, preview or apply (
execute_plan)Save, load, list, and delete plans (
save_plan,load_plan,list_plans,delete_plan)Track step-by-step progress and version history; roll back plan versions (
start_step,complete_step,fail_step,view_progress,view_history,compare_plan_versions,rollback_plan)Gate execution with human approval workflows (
request_approval,respond_approval)
Code Review
AI-powered review of diffs or git changes with structured findings (P0–P3 priority, confidence scores) (
review_changes,review_diff,review_git_diff,review_auto)Reactive PR review with parallel execution, session management, commit-aware caching, and telemetry (
reactive_review_pr,get_review_status,pause_review,resume_review,get_review_telemetry)Deterministic invariant checks against YAML-defined rules (
check_invariants) and static analysis via TypeScript/Semgrep (run_static_analysis)
Security & Validation
Detect and mask 15+ secret types before sending content to an LLM (
scrub_secrets)Multi-tier content validation: bracket balancing, JSON structure, TODO detection, hardcoded URLs, and automatic secret scrubbing (
validate_content)
Tool Discovery
Inspect all available server tools and capabilities (
tool_manifest)
Provides comprehensive tools for automatic retrieval and review of code changes, including staged, unstaged, branch, and commit-level diffs.
Enables the visualization of structured execution plans by generating and displaying Mermaid-formatted diagrams.
Integrates with local static analysis tools like tsc to provide deterministic feedback and analysis during the code review process.
Supports deterministic invariant checking using YAML-based rule files to enforce project-specific constraints during reviews.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Context Engine MCP Serverfind where the user authentication logic is implemented"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Context Engine MCP Server
A local-first, agent-agnostic Model Context Protocol (MCP) server for workspace indexing, retrieval, planning, and review workflows.
New here? Check out INDEX.md for a complete documentation guide.
Quick Start: QUICKSTART.md -> GET_STARTED.md -> API_REFERENCE.md
Windows Deployment: docs/WINDOWS_DEPLOYMENT_GUIDE.md
Architecture: TECHNICAL_ARCHITECTURE.md for deep technical dive
Architecture
This implementation follows a clean 5-layer architecture:
┌────────────────────────────┐
│ Coding Agents (Clients) │ Layer 4: Codex, Claude, Cursor, etc.
│ Codex | Claude | Cursor │
└────────────▲───────────────┘
│ MCP (tools)
┌────────────┴───────────────┐
│ MCP Interface Layer │ Layer 3: server.ts, tools/
│ (standardized tool API) │
└────────────▲───────────────┘
│ internal API
┌────────────┴───────────────┐
│ Context Service Layer │ Layer 2: serviceClient.ts
│ (query orchestration) │
└────────────▲───────────────┘
│ domain calls
┌────────────┴───────────────┐
│ Retrieval + Review Engine │ Layer 1: local-native runtime
│ (indexing, retrieval) │
└────────────▲───────────────┘
│ storage/state
┌────────────┴───────────────┐
│ Local State / Artifacts │ Layer 5: workspace state + evidence
│ (index, cache, receipts) │
└────────────────────────────┘Layer Responsibilities
Layer 1: local-native indexing, retrieval, review support, and provider orchestration
Layer 2: context assembly, snippet formatting, deduplication, limits, and caching
Layer 3: MCP tools, validation, and request/response contracts
Layer 4: coding agents and MCP clients that consume the tools
Layer 5: persisted index state, caches, rollout receipts, and generated artifacts
Features
MCP Tools
The server exposes tools across these areas:
Core context and retrieval
Memory
Planning and execution
Plan management
Code review
Reactive review
Use tool_manifest() in the MCP server to inspect the current tool inventory directly.
Key Characteristics
Local-first runtime with no legacy provider SDK dependency in the active path
Agent-agnostic MCP interface
Local-native retrieval provider as the active runtime
Persistent state and evidence artifacts for rollout-proof workflows
Planning, review, and validation workflows built into the server
Optional benchmarking, parity, and governance gates for safer changes
Quick Start
npm install
npm run build
npm run verify
node dist/index.js --workspace .Optional validation commands:
npm run ci:check:no-legacy-provider
npm run ci:check:legacy-capability-parity
npm run ci:check:legacy-capability-parity:strictDocumentation Quick Links
Setup: QUICKSTART.md
MCP Clients: docs/MCP_CLIENT_SETUP.md
Getting Started: GET_STARTED.md
Troubleshooting: TROUBLESHOOTING.md
Testing: TESTING.md
Architecture: ARCHITECTURE.md
Memory Operations: docs/MEMORY_OPERATIONS_RUNBOOK.md
All Docs: INDEX.md
Current Status
Active runtime is local-native only
Legacy-provider references that remain are historical docs, tests, or migration guardrails
Removal and parity proof tracking lives in docs/LEGACY_PROVIDER_ADOPTION_AND_REMOVAL_TRACKER.md
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.