SynAgent MCP - Cross-Agent CLI Bridge
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 |
|---|---|
| codex_statusA | Get the active OpenAI Codex CLI configuration, active model, reasoning effort, and governance policies (e.g. Astra approval rules). |
| codex_debug_errorC | Consult OpenAI Codex to diagnose errors, exceptions, stack traces, or unexpected test/build failures and suggest solutions. |
| codex_analyzeB | Perform deep architectural, dependency, and structural code analysis in read-only sandbox mode using OpenAI Codex. |
| codex_review_codeA | Run an automated code review on uncommitted repository changes or a specific git diff using OpenAI Codex in read-only mode. |
| codex_implementA | Request OpenAI Codex to synthesize complex code, algorithms, structural refactorings, or boilerplate in read-only sandbox mode. |
| codex_consultB | Consult OpenAI Codex for a second opinion on an architecture plan, refactoring strategy, or technical trade-offs. |
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 6 tools
The tools target distinct Codex usage modes: status, analysis, debugging, review, implementation, and consultation. However, codex_analyze, codex_consult, and codex_review_code have adjacent boundaries that could cause occasional misselection.
All tools use a consistent codex_ prefix and snake_case, which makes the set predictable. There is minor inconsistency between verb-only names (codex_analyze, codex_implement, codex_consult), verb_noun names (codex_debug_error, codex_review_code), and a noun name (codex_status).
Six tools is well-scoped for a Codex CLI wrapper, and each tool represents a meaningful, non-redundant operation. The count is neither thin nor bloated.
The surface covers common Codex interactions including status, analysis, debugging, review, implementation, and consultation. Minor gaps exist around applying changes, continuing sessions, or explicitly generating/running tests, but agents can work around these limitations.