Crabeye MCP Bridge

One MCP connection for all your tools - with discovery, namespacing, and execution policies. It runs locally over stdio via the published package.

People connecting this server to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-06-19 · ★ 14 · #212 OF 848 MAINTAINED OTHER · VERIFIED 2026-08-25

MIT · TypeScript servers · how we verify → /methodology

01 · Install Crabeye MCP Bridge

before you install - you'll need

GITHUB_TOKEN

Environment variables documented in the project's README - it lists which are required and which have defaults.

Claude Code

claude mcp add crabeye-ai-crabeye-mcp-bridge -- npx -y @crabeye-ai/crabeye-mcp-bridge

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "crabeye-ai-crabeye-mcp-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "@crabeye-ai/crabeye-mcp-bridge"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package @crabeye-ai/crabeye-mcp-bridge - published under the repo owner's npm scope (@crabeye-ai)

registry namespace io.github.crabeye-ai is GitHub-verified and matches the repo owner

03 · What Crabeye MCP Bridge can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

Latest releases

v1.3.0 · 2026-06-05

Daemon-side MCP ping for spawned stdio children // detects wedged child between sessions, kills + reconnects via existing exit path · Skip tool-search index rebuild on identical re-registration // guards against…

v1.2.1 · 2026-05-11

Sync APP_VERSION with package.json // read version via createRequire so npm version is single source of truth · Per-server context passthrough // _bridge.passthrough opt-in for upstream instructions + tools, daemon…

v1.2.0 · 2026-05-08

STDIO manager docs + telemetry // full-review consider items: cap rpc.errorsTotal map at 64 distinct codes, compute sessionsReopened from closing flag, add closed-enum invariant assertion + cap unit test (AIT-250)…

04 · Who maintains Crabeye MCP Bridge

crabeye-mcp-bridge is maintained by crabeye-ai. It's the only MCP server we track from this author; the repo dates to Feb 2026.

05 · Facts

category
other - ranked #212 of 848 actively-maintained other servers as of 2026-08-25.
release cadence
1 release in the last 90 days (latest 2026-06-05)
registry
io.github.crabeye-ai/crabeye-mcp-bridge (active, first published 2026-03-18 · 3 versions)
packages
npm:@crabeye-ai/crabeye-mcp-bridge

06 · Crabeye MCP Bridge FAQ

What is Crabeye MCP Bridge?

One MCP connection for all your tools - with discovery, namespacing, and execution policies. It runs locally over stdio via the published package.

Is Crabeye MCP Bridge still maintained?

Yes - as of 2026-08-25, its last commit was 2026-06-19 and it shipped 1 release in the last 90 days. We re-verify nightly.

How do I install Crabeye MCP Bridge?

Run `npx -y @crabeye-ai/crabeye-mcp-bridge`. The README documents one environment variable (GITHUB_TOKEN) to set first. You can also paste the ready-made client config above.

Does Crabeye MCP Bridge run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Crabeye MCP Bridge