Codex Context Engine
Click on "Deploy 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., "@Codex Context Engine find definitions for the function 'parseConfig'"
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.
Codex Context Engine
Codex Context Engine is a local MCP server that indexes a workspace and exposes code-navigation tools to Codex.
It parses JavaScript and TypeScript files with Babel, uses simple regex-based indexing for Python, Go, and Rust, writes an index to .codex-context.json, and generates a CODEBASE_MAP.md report.
The project is useful for quick local navigation, reference lookup, dependency checks, and lightweight audits. It is not a replacement for a compiler, language server, type checker, or dedicated security scanner.
What It Does
Indexes source files with these extensions:
.js,.jsx,.ts,.tsx,.mjs,.cjs,.py,.go,.rs.Ignores common generated or heavy paths such as
node_modules,.git,dist,build, package lockfiles, and its own index file.Extracts symbols, imports, exports, and call expressions into a JSON index.
Watches the workspace for changes and updates indexed files incrementally. If recursive
fs.watchis not available, it falls back to polling.Provides MCP tools over stdio for local Codex integrations.
Runs locally and does not call external APIs during indexing.
Related MCP server: MCP Indexer
Current Limits
JavaScript and TypeScript support is AST-based, but it is still a static heuristic indexer. It does not type-check code or resolve every dynamic pattern.
Python, Go, and Rust support is regex-based and intentionally shallow.
Reference and call-graph results are best-effort. Dynamic dispatch, aliasing, reflection, generated code, and complex module resolution may be missed.
semantic_queryis keyword scoring over names, paths, and comments. It is not embeddings or AI semantic search.audit_securitydetects common secret patterns and source map files. It can miss secrets and can produce false positives.estimate_semver_impactrequires a Git repository and compares exported JavaScript/TypeScript signatures heuristically.
Architecture
graph TD
A[Codex Agent] <-->|JSON-RPC over stdio| B[MCP Server]
B <--> C[Query Engine]
B <--> D[Codebase Indexer]
D -->|JS/TS AST parsing| E[Babel Parser]
D -->|Python/Go/Rust regex parsing| H[Regex Fallbacks]
D -->|Watches files| F[fs.watch or polling]
D -->|Writes JSON| G[.codex-context.json]
D -->|Generates report| I[CODEBASE_MAP.md]MCP Tools
Tool | Parameters | What it returns |
| None | Rebuilds the workspace index. |
|
| Definition locations, line ranges, docs when available, and code snippets. |
|
| Import and call-expression references found in the indexed files. |
|
| Best-effort caller/callee data from indexed call expressions. |
|
| Weighted keyword matches over symbol names, docs, and file paths. |
| None | Cycles found in resolved internal imports. |
| None | Exports that are not imported elsewhere in the indexed workspace. |
|
| Heuristic SemVer suggestion based on Git diff against a ref. |
| None | Common credential-pattern warnings, source map files, and sensitive config filenames. |
|
| Symbols, import count, and export count for one indexed file. |
Installation
Requires Node.js 18 or newer.
npm installRunning Locally
npm startThe server communicates over stdio, so normal diagnostic output is written to stderr to avoid corrupting MCP JSON-RPC messages on stdout.
Codex MCP Configuration
Project-scoped example:
[mcpServers.codex-context-engine]
command = "node"
args = ["/absolute/path/to/codex-context-engine/src/server.js"]Global config locations commonly used by Codex:
Windows:
%USERPROFILE%\.codex\config.tomlmacOS/Linux:
~/.codex/config.toml
This repository also includes .mcp.json for plugin-style configuration:
{
"mcpServers": {
"codex-context-engine": {
"command": "node",
"args": ["./src/server.js"]
}
}
}Generated Files
.codex-context.json: local index cache. It is ignored by Git.CODEBASE_MAP.md: generated workspace report. This repository currently tracks it as a sample/report artifact.
Testing
npm testThe test suite covers:
JS/TS symbol indexing and doc extraction.
CommonJS imports and exports.
Destructured bindings.
Basic Python, Go, and Rust regex indexing.
Circular dependency and unused export detection.
Git-based SemVer impact estimation.
Security-audit masking for common patterns.
Polling watcher fallback.
MCP stdio safety for indexer diagnostics.
Available Tools
10 toolsaudit_securityA
Scans the workspace to identify sensitive credentials (API keys, private keys, database connection strings) and build source map files (.map) that might leak source structure.
Inputs: no named parameters.
detect_circular_dependenciesA
Analyzes module imports to locate dependency cycles (e.g. A imports B, B imports A) which lead to runtime errors.
Inputs: no named parameters.
estimate_semver_impactB
Estimates the semantic versioning impact (Major/Minor/Patch) of current changes by comparing code signatures with a reference commit or branch.
Inputs: refBranch.
find_definitionsA
Returns definition details, lines, and exact code snippet for a given function, class, or method name.
Inputs: symbolName (required).
find_referencesA
Searches the workspace for references to a given symbol name. Returns file paths, line numbers, caller names, and matching code snippets.
Inputs: symbolName (required).
find_unused_exportsA
Scans the project to identify exported classes, functions, or variables that are never imported anywhere in the codebase.
Inputs: no named parameters.
get_call_graphA
Generates caller-callee trees to trace program execution pathways for a given function or method.
Inputs: functionName (required), direction.
get_file_outlineB
Returns a structured outline of all symbols (classes, functions, methods, variables) declared inside a specific file from the index.
Inputs: filePath (required).
index_workspaceA
Triggers a re-scan of the workspace, parsing all JavaScript/TypeScript files to rebuild the symbol and call graph index.
Inputs: no named parameters.
semantic_queryA
Performs a weighted search over symbols and comments using query keywords to locate code by intent (e.g., "jwt parsing").
Inputs: queryText (required), limit.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Each tool has a clear and distinct purpose: security auditing, circular dependency detection, semver estimation, symbol definition/reference lookup, unused export detection, call graph generation, file outlining, workspace indexing, and semantic querying. No overlap is apparent.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., audit_security, find_definitions, get_file_outline), making them predictable and easy to distinguish.
With 10 tools, the server covers a comprehensive range of code analysis tasks without being overwhelming. Each tool serves a distinct analytical purpose, justifying its inclusion.
The tool set covers essential code analysis operations like indexing, symbol lookup, call graph, security scan, etc. Minor gaps exist (e.g., no tool for refactoring or package-level dependency listing), but the surface is largely complete for a context engine.
Related MCP Connectors
Ask a codebase what calls what: search, blast radius, paths between symbols, and diffs.
Code intelligence for coding agents: semantic, AST, graph, and full-text search. 279+ languages.
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA local server that provides powerful code analysis and search capabilities for software projects, helping AI assistants and development tools understand codebases for tasks like code generation and refactoring.4-
- AlicenseNot gradedqualityDmaintenanceEnables semantic code search across multiple repositories using natural language queries. Provides intelligent code discovery, symbol lookups, and cross-repo dependency analysis for AI coding agents.MIT

Semantic Code Search MCPofficial
AlicenseNot gradedqualityDmaintenanceProvides AI coding agents with structured access to indexed codebases via semantic search, symbol analysis, and file reading tools.13Server Side Public , v 1- AlicenseNot gradedqualityDmaintenanceProvides IDE-like code navigation and search for local repositories, enabling AI assistants to perform symbol search, trigram indexing, and semantic navigation.AGPL 3.0