codex-cli-sync-mcp
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| codex_executeA | Execute one bounded coding task through Codex CLI (synchronous, blocks until done) and return a compact JSON report with diff/status context. |
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 zero ambiguity in selecting between tools. The purpose is clear and singular.
The single tool name follows a clear verb_noun pattern (codex_execute), which is consistent and readable. No conflicting conventions exist.
The server exposes only one tool, which is well below the typical 3-15 range. While the narrow focus may justify a minimal surface, it feels too sparse for a general-purpose coding task executor, especially given the server name suggests broader sync functionality.
The server provides only a single execute operation with no supporting tools for status, history, configuration, or cancellation. This leaves significant gaps in the expected lifecycle of a coding task execution service, likely causing agent dead-ends.