Back to directory

@aiwerk/openclaw-mcp-bridge

An OpenClaw plugin that connects any MCP server to an OpenClaw agent, registering its tools automatically and offering either individual per-tool registration or a single router tool that saves most of the token cost of many servers.

@aiwerk/openclaw-mcp-bridge

This plugin is a thin wrapper around the @aiwerk/mcp-bridge library that handles tool registration, lifecycle and configuration for connecting MCP servers to an OpenClaw agent. Installed as an OpenClaw plugin, it can install servers from a bundled catalog, such as Todoist, GitHub, Notion, Stripe, Linear, Google Maps and Hetzner, through an interactive script that prompts for API keys and configures them automatically.

A direct mode registers every server's tools individually, which suits a small number of servers or simpler models, while a router mode exposes a single mcp tool through which the agent discovers and calls server tools, saving roughly 99% of the tool-definition tokens when three or more servers are connected. Configuration lives in the OpenClaw config file, with environment variables resolved from a local .env file or the system environment, and catalog recipes can optionally auto-merge into the server configuration.

Built with TypeScript. MIT licensed.

More in MCP servers

See all 734
  • Light Cloud

    light-cloud.com

    A hosting platform that deploys a static site, a container, or a managed Postgres database straight from a GitHub, GitLab, or Bitbucket push, with a preview URL for every branch and an MCP server for deploying from Claude Code.

  • ForensicDbg

    forensicdbg.com

    A post-mortem debugger for native Windows x86 and x64 crashes, with an MCP interface so AI tools can consume crash-dump analysis directly.

  • Karada.ai

    karada.ai

    A CI/CD platform that auto-compiles existing APIs into Go MCP servers, attaches composable middleware, and exposes them through one gateway usable from Cursor, Claude Code, and Windsurf.