Crabeye MCP Bridge consolidates multiple MCP servers into a single STDIO interface, exposing two tools: `search_tools` and `run_tool` for efficient tool management and execution.
From the registry: One MCP connection for all your tools — with discovery, namespacing, and execution policies.
$ npx @crabeye-ai/crabeye-mcp-bridge initPlease install the `crabeye-mcp-bridge` MCP server into my current AI client (that's you).
Optional prerequisites:
- Initialize bridge — Discover MCP client configs and set up the bridge automatically. Run: `npx @crabeye-ai/crabeye-mcp-bridge init`
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","@crabeye-ai/crabeye-mcp-bridge","--config","<path-to-config>.json"]
Note: Meta-MCP bridge that consolidates multiple upstream MCP servers behind a single STDIO connection with two tools: search_tools and run_tool. Use `init` to auto-configure from existing client configs.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.GITHUB_TOKENrequiredUsed for authenticating with GitHub services.AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.
Persistent codebase knowledge graph. Survives session restarts and context compaction.
A powerful toolkit for coding, providing semantic retrieval and editing capabilities.