Codex Gemini MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_LOG_DIR | No | Log path override. | |
| MCP_LOG_PREVIEW | No | Whether to save log previews. Set to '1' to enable. | |
| MCP_RUNTIME_DIR | No | Default runtime file root (e.g., .codex-gemini-mcp). | .codex-gemini-mcp |
| MCP_LOG_FULL_TEXT | No | Whether to save full text logs. Set to '1' to enable. | |
| MCP_CLI_TIMEOUT_MS | No | Default CLI timeout in milliseconds. Default is 600000 (10 minutes). | 600000 |
| MCP_MAX_OUTPUT_BYTES | No | Maximum output bytes (cap, for future runtime extension). | |
| MCP_CODEX_DEFAULT_MODEL | No | Default model for codex. Default is gpt-5.3-codex. | gpt-5.3-codex |
| MCP_GEMINI_DEFAULT_MODEL | No | Default model for gemini. Default is gemini-3-pro-preview. | gemini-3-pro-preview |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_codexC | Send a prompt to local Codex CLI and return its output. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as sending prompts to a local Codex CLI, making it impossible for an agent to misselect between non-existent alternatives.
A single tool inherently exhibits perfect naming consistency, as there are no other tools to compare it against. The name 'ask_codex' follows a clear verb_noun pattern and stands alone without any conflicting conventions.
One tool is too few for a server named 'Codex Gemini MCP', which suggests a broader scope or multiple functionalities. A single tool feels thin and limited, failing to provide a comprehensive surface for interacting with a Codex CLI beyond basic prompting.
The tool surface is severely incomplete for the implied domain of a Codex CLI interface. While 'ask_codex' covers basic prompting, there are obvious gaps such as configuration management, session handling, or advanced querying capabilities that would be expected in a more robust integration.