Codex Context Engine
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| index_workspaceA | Triggers a re-scan of the workspace, parsing all JavaScript/TypeScript files to rebuild the symbol and call graph index. |
| find_definitionsA | Returns definition details, lines, and exact code snippet for a given function, class, or method name. |
| find_referencesA | Searches the workspace for references to a given symbol name. Returns file paths, line numbers, caller names, and matching code snippets. |
| get_call_graphA | Generates caller-callee trees to trace program execution pathways for a given function or method. |
| semantic_queryA | Performs a weighted search over symbols and comments using query keywords to locate code by intent (e.g., "jwt parsing"). |
| detect_circular_dependenciesA | Analyzes module imports to locate dependency cycles (e.g. A imports B, B imports A) which lead to runtime errors. |
| find_unused_exportsA | Scans the project to identify exported classes, functions, or variables that are never imported anywhere in the codebase. |
| estimate_semver_impactB | Estimates the semantic versioning impact (Major/Minor/Patch) of current changes by comparing code signatures with a reference commit or branch. |
| audit_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. |
| get_file_outlineB | Returns a structured outline of all symbols (classes, functions, methods, variables) declared inside a specific file from the index. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.