@aiwerk/openclaw-mcp-bridge

OpenClaw plugin for MCP Bridge — connect any MCP server to your OpenClaw agent.

This is a thin wrapper around @aiwerk/mcp-bridge that handles OpenClaw tool registration, lifecycle, and configuration.

Install

openclaw plugins install @aiwerk/openclaw-mcp-bridge

⚠️ Important: Always use the full scoped name @aiwerk/openclaw-mcp-bridge. The unscoped openclaw-mcp-bridge on npm is a different, unrelated package.

Quick Start

# 1. Install the plugin
openclaw plugins install @aiwerk/openclaw-mcp-bridge

# 2. Install a server from the catalog
~/.openclaw/extensions/openclaw-mcp-bridge/install-server.sh todoist

# 3. Restart the gateway
openclaw gateway restart

The install script prompts for your API key and configures everything automatically.

Configuration

The plugin config lives in ~/.openclaw/openclaw.json under plugins.entries.openclaw-mcp-bridge.config:

{
  "plugins": {
    "entries": {
      "openclaw-mcp-bridge": {
        "config": {
          "mode": "router",
          "servers": {
            "todoist": {
              "transport": "stdio",
              "command": "npx",
              "args": ["-y", "@doist/todoist-ai"],
              "env": { "TODOIST_API_KEY": "${TODOIST_API_TOKEN}" },
              "description": "Task management"
            }
          },
          "toolPrefix": true
        }
      }
    }
  }
}

Catalog Options

Breaking change (v0.14.0+): autoMerge now defaults to false. Previously, catalog recipes were always merged automatically. To restore the old behavior, set autoMerge: true in your plugin config.

{
  "plugins": {
    "entries": {
      "openclaw-mcp-bridge": {
        "config": {
          "autoMerge": true
        }
      }
    }
  }
}

Environment variables are resolved from ~/.openclaw/.env and system env.

Note (v0.10.4+): If an env var exists in your shell as an empty string, the plugin falls back to reading ~/.openclaw/.env directly. This prevents issues where dotenv(override:false) silently ignores the .env value.

Modes

Server Catalog

# List available servers
~/.openclaw/extensions/openclaw-mcp-bridge/list-servers.sh

# Install interactively
~/.openclaw/extensions/openclaw-mcp-bridge/install-server.sh <server>

# Available: todoist, github, notion, stripe, linear, google-maps,
#            hetzner, miro, wise, tavily, apify

Docker Sandbox

If you run OpenClaw with Docker sandbox enabled (agents.defaults.sandbox.mode: "all" or "non-main"), plugin-registered tools are not included in the default sandbox tool allowlist. You need to explicitly allow them:

{
  "tools": {
    "sandbox": {
      "tools": {
        "allow": ["group:openclaw", "mcp", "mcp_bridge_update"]
      }
    }
  }
}

• group:openclaw — keeps all built-in OpenClaw tools
• mcp — the MCP Bridge router tool
• mcp_bridge_update — the plugin update tool

You can verify with openclaw sandbox explain --json — check that mcp appears in sandbox.tools.allow.

Alternative ways to apply this:

• Control UI: Open http://localhost:18789/config → navigate to tools → sandbox → tools → allow → add mcp and mcp_bridge_update alongside group:openclaw.
• CLI: openclaw config set tools.sandbox.tools.allow '["group:openclaw", "mcp", "mcp_bridge_update"]'

The gateway hot-reloads the config automatically.

Note: Without sandbox (sandbox.mode: "off"), no extra config is needed — plugin tools are available automatically.

Update

# Check for updates (via the agent)
mcp_bridge_update(check_only=true)

# Install update
openclaw plugins update @aiwerk/openclaw-mcp-bridge
openclaw gateway restart

Architecture

OpenClaw Agent
    │
    ├── mcp tool (router mode)
    │   └── @aiwerk/openclaw-mcp-bridge (this plugin)
    │       └── @aiwerk/mcp-bridge (core)
    │           ├── todoist (stdio)
    │           ├── github (stdio)
    │           └── notion (stdio)
    │
    └── other tools...

The plugin handles:

• Tool registration with OpenClaw (registerTool / unregisterTool)
• Lifecycle (activate / deactivate)
• Update notifications (injected into tool responses)
• OpenClaw config integration (openclaw.json)

The core handles:

• MCP protocol (initialize, tools/list, tools/call)
• Transport management (stdio, SSE, streamable-http)
• Router / direct mode multiplexing
• Schema conversion, reconnection, error handling

Standalone Usage

Don't use OpenClaw? Use the core package directly with Claude Desktop, Cursor, Windsurf, or any MCP client:

npm install -g @aiwerk/mcp-bridge
mcp-bridge init
mcp-bridge install todoist
mcp-bridge

See @aiwerk/mcp-bridge for details.

License

MIT — AIWerk