codex-agy-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGY_CMD | Yes | Absolute path to the agy binary |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agy_run_startA | Start or continue one foreground Antigravity Run. mode="task" starts a normal bridge-owned task. mode="interactive" starts a persistent conversation session that should be used sparingly. Supplying conversation_id continues that exact Antigravity conversation. dangerously_skip_permissions must be true; the bridge always forwards --dangerously-skip-permissions to Antigravity. |
| agy_start_with_expected_fileC | Start one task Run that cannot complete until expected_file is non-empty. |
| agy_run_waitB | Wait for sparse Run events instead of repeatedly polling status. run_ids is always a list, even for one Run. Supported condition values: any_attention, any_terminal, all_terminal, any_event, plus aliases attention, terminal, finished, finish, complete, completed, result, all_finished, all_complete, and all_completed. |
| agy_loginC | Refresh Antigravity auth state and optionally open one login session. |
| agy_run_observeA | Inspect Run state through one lean observation surface. view="full" returns merged observable state for all run_ids. view="status", "transcript", or "terminal" requires exactly one run_id and returns the corresponding focused view. |
| agy_run_inputB | Send input to a live foreground Run with optional stale-write guards. |
| agy_run_cancelC | Cancel one active Run and terminate its Antigravity process group. |
| agy_run_resultB | Read final result metadata, or a bounded chunk when offset_bytes is set. |
| agy_review_commitA | Start a typed review Run for one commit and return immediately. Keep issue focused and use narrow scope_paths when possible. After the run completes, prefer agy_review_result over manually polling raw artifacts. |
| agy_review_branchA | Start a typed review Run for branch and working-tree changes. Keep issue focused and use narrow scope_paths when possible. Wait for completion with agy_run_wait, then prefer agy_review_result. Avoid frequent agy_run_observe(include_terminal_tail=True) calls unless debugging the bridge. |
| agy_review_resultB | Validate and summarize the artifact from a typed review Run. Preferred way to consume completed agy_review_commit/agy_review_branch runs. |
| agy_goalC | Manage bridge scheduler goals with actions create, start_target, status. dangerously_skip_permissions must be true when supplied. |
| agy_adminC | Run bounded diagnostics and metadata actions for the bridge and agy CLI. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/varadfromeast/codex-agy-bridge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server