Skip to content

Introduction

MCP Bridge is the core runtime for connecting many MCP servers through a single interface. This documentation covers three connected projects:

  • @aiwerk/mcp-bridge — router, transport layer, auth, caching, and batching
  • @aiwerk/mcp-catalog — searchable recipe catalog with MCP + REST interfaces
  • @aiwerk/openclaw-mcp-bridge — OpenClaw plugin adapter built on top of the bridge core

Get running fast

Initialize MCP Bridge, install your first server, and connect it to your MCP client.

Configure your stack

Learn server definitions, auth models, modes, and environment variable handling.

Use Smart Router

Route by intent, compress schemas, cache results, and resolve tool collisions.

Integrate OpenClaw

Install the plugin and map universal recipes to OpenClaw-native configuration.

MCP client calls the bridge (mcp meta-tool in router mode, or direct tool names in direct mode). The bridge dispatches to configured upstream servers over stdio, sse, or streamable-http.