Context Proxy vs Crabeye MCP Bridge
A side-by-side look at the Context Proxy and Crabeye MCP Bridge MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Context Proxy for aggregators work as a local process; choose Crabeye MCP Bridge for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Context Proxy when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
Choose Crabeye MCP Bridge when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Aggregators | Aggregators |
| Quality signal | 35/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 15 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Context Proxy | View Crabeye MCP Bridge |
Tools & capabilities
Context Proxy tools
No tool names declared yet. Check the project README from the listing page.
Crabeye MCP Bridge tools
No tool names declared yet. Check the project README from the listing page.
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.
Context Proxy
{
"mcpServers": {
"context-proxy": {
"command": "npx",
"args": [
"-y",
"mcp-lazy-proxy"
]
}
}
}
Crabeye MCP Bridge
{
"mcpServers": {
"crabeye-mcp-bridge": {
"command": "npx",
"args": [
"-y",
"@crabeye-ai/crabeye-mcp-bridge"
]
}
}
}
Frequently asked questions
Context Proxy is categorized under Aggregators and uses a local stdio subprocess. Crabeye MCP Bridge belongs to Aggregators and uses a local stdio subprocess. Pick Context Proxy for aggregators work and Crabeye MCP Bridge for aggregators.
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.
Context Proxy has no declared pricing — check the project's own site. Crabeye MCP Bridge has no declared pricing — check the project's own site. 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 context-proxy and crabeye-mcp-bridge as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Context Proxy has a quality signal of 35/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Crabeye MCP Bridge has 41/100 (Fair) with 0 views, 0 installs and 15 GitHub stars.