Claude Code Bridge vs Agy Bridge
A side-by-side look at the Claude Code Bridge and Agy Bridge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Claude Code Bridge for coding agents work as a local process; choose Agy Bridge for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Claude Code Bridge when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You want tools like
bridge_send, bridge_receive, bridge_wait.
Choose Agy Bridge when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
analyze_files, deep_search, web_lookup.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 55/100 · Good | 68/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 14 | 56 |
| Directory activity | 0 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 13 | 6 |
| Full listing | View Claude Code Bridge | View Agy Bridge |
Tools & capabilities
Claude Code Bridge tools 13
bridge_sendSend legacy text or a protocol-v1 message; supports idempotent retriesbridge_receiveRead a bounded page using a message cursor or durable consumer cursorbridge_waitWait up to 55 seconds for new messages without rapid pollingbridge_ackMonotonically advance a consumer's channel-scoped cursorbridge_channelsList active channels and countsbridge_pingCheck bridge health and capabilitiesbridge_statusSummarize recent activity across channelsbridge_clearDelete every message (and task) in one channelbridge_enqueueAdd a task to a channel's work queue (exclusive; claimed once)bridge_claimAtomically claim the next task with a lease; long-poll with `wait_secondsbridge_completeMark a claimed task done, fenced by its `lease_tokenbridge_failFail a claimed task — requeue with backoff, or dead-letter- +1 more on the listing page
Agy Bridge tools 6
analyze_filesDelegate 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_searchDelegate 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_lookupDelegate 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_reviewGet 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.follow_upContinue 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.delegateRaw 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.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Claude Code Bridge
{
"mcpServers": {
"claude-code-bridge": {
"command": "uvx",
"args": [
"claude-code-bridge"
]
}
}
}
Agy Bridge
{
"mcpServers": {
"sshahzaiib-agy-bridge": {
"command": "npx",
"args": [
"-y",
"agy-bridge"
]
}
}
}
Frequently asked questions
Claude Code Bridge is categorized under Coding Agents and uses a local stdio subprocess. Agy Bridge belongs to Coding Agents and uses a local stdio subprocess. Pick Claude Code Bridge for coding agents work and Agy Bridge for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Claude Code Bridge has no declared pricing — check the project's own site. Agy Bridge is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add claude-code-bridge and sshahzaiib-agy-bridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Claude Code Bridge has a quality signal of 55/100 (Good) with 0 views, 0 installs and 14 GitHub stars. Agy Bridge has 68/100 (Great) with 6 views, 0 installs and 56 GitHub stars.