AO

aiwerk/openclaw-mcp-bridge

开发工具

本页由 AI 翻译,技术细节请以原文为准。 查看原文

11 stars 5 forks 质量 75 趋势 16MIT

OpenClaw MCP Client Plugin - bridges MCP servers into OpenClaw via registerTool

概览

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. ⚠️ Always use the full scoped name @aiwerk/openclaw-mcp-bridge. The unscoped openclaw-mcp-bridge on npm is a . The install script prompts for your API key and configures everything automatically. The plugin config lives in ~/.openclaw/openclaw.json under plugins.entries.openclaw-mcp-bridge.config: autoMerge now defaults to false. Previously, catalog recipes were always merged automatically. To restore the old behavior, set autoMerge: true in your plugin config. Environment variables are resolved from ~/.openclaw/.env and system env. 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.

README

以下为原文 README 节选,完整内容请查看原文。

@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

Option Type Default Description
catalog boolean true Whether to fetch catalog recipes on startup via bootstrapCatalog()
autoMerge boolean false Whether to auto-merge catalog recipes into your server config

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

| Mode | How it works | Best for |

在 GitHub 查看完整 README

安装

npx -y @doist/todoist-ai
新手?先看 mcpskill.org 教程 →