Agy Bridge vs Oz MCP Server — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Agy Bridge vs Oz MCP Server
In-depth architectural comparison of the Agy Bridge and Oz MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Agy Bridge
Coding Agents · Local stdio
Quality: 65/100 (Great) | Auth: other
Oz MCP Server
Coding Agents · Local stdio
Quality: 63/100 (Good) | Auth: other
Verdict Summary: Choose Agy Bridge if you need specialized Coding Agents tools running via a local process. Choose Oz MCP Server if your workspace requires Coding Agents integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Agy Bridge when:
You need dedicated capabilities in the Coding Agents domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
Delegate heavy tasks from Claude Code (or any MCP client) to the Antigravity CLI (Gemini): file analysis, repo archaeology, web lookups, and adversarial second-opinion code reviews. Quota-aware model failover with cooldowns, per-tool timeouts, and multi-turn session continuity.
Bridges Warp's Oz coding agent to any IDE or MCP client (Claude Code, Cursor, Codex), plus native @oz in VS Code Copilot Chat. Independent project; uses only Warp's documented public interfaces. MIT.
Category & Scope
Tools & Capabilities Breakdown
Agy Bridge Tools (6)
analyze_files
Delegate file analysis to the Antigravity CLI (Gemini) instead of reading files yourself. USE THIS whenever a file is large (>200 lines) or the task spans more than 3 files: logs, database dumps, generated code, cross-file reviews, comparisons. The files never enter your context — only the answer does.
deep_search
Delegate codebase archaeology to the Antigravity CLI: git log/diff/blame spelunking, wide greps across a repo, 'when/why did X change', 'where is Y used'. USE THIS instead of running many search commands yourself — it saves your context.
web_lookup
Delegate a web/documentation lookup to the Antigravity CLI (Gemini with web access): library docs, API references, error messages, current versions, external knowledge. USE THIS when you need information you don't have or that may be newer than your training data.
adversarial_review
Get an adversarial second opinion from a different model family (Gemini Pro). ALWAYS use this for plan critiques, design reviews, and pre-merge code review: it hunts for flaws, edge cases, security issues, and unstated assumptions you may have missed.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Agy Bridge is categorized under Coding Agents and uses a local stdio subprocess. In contrast, Oz MCP Server belongs to Coding Agents using local stdio subprocess. Select Agy Bridge when you need capabilities focused on coding agents and Oz MCP Server when you require tools for coding agents.
Continue a previous Antigravity session by session_id (returned by every other tool). USE THIS for follow-up questions about a prior delegation — the full prior context is already on agy's side, so you don't resend anything.
delegate
Raw delegation to the Antigravity CLI for heavy tasks that don't fit the other tools. agy has full tool access (shell, file reads, web) in the given cwd.
Oz MCP Server Tools (6)
oz_agent_run
Run `oz agent run` locally with a prompt. Returns the full run payload.
oz_agent_run_cloud
Launch a cloud run. **Consumes Warp credits.
oz_run_get
Fetch a run's status and output by id. Read-only.
oz_run_list
List recent runs; filter by `all` / `active` / `completed` / raw status, plus a numeric `limit`.
oz_list_models
List the AI model ids available to the account and report the current default. Read-only.
oz_set_default_model
Set the default Oz model by writing `defaultModel` into the workspace `.warp/warp-bridge.yaml`.