Suppose your client configuration originally specifies an MCP server like this:

{
  "mcpServers": {
    "fetch": {
      "command": "uvx",
      "args": ["mcp-server-fetch"]
    }
  }
}

To route requests through Minibridge (enabling SBOM checks, policy enforcement, etc.), update the entry:

{
  "mcpServers": {
    "fetch": {
      "command": "minibridge",
      "args": ["aio", "--", "uvx", "mcp-server-fetch"]
    }
  }
}

• minibridge aio: Invokes Minibridge in “all-in-one” mode, wrapping the downstream tool.
• uvx mcp-server-fetch: The original MCP server command, now executed inside Minibridge.

Minibridge allows you to deploy your MCP Server using http/sse:

If your client supports the http/sse protocol (like Cursor, VSCode, etc.), just start Minibridge in http/sse mode like:

minibridge aio --listen 127.0.0.1:8000 -- uvx mcp-server-fetch

Then configure your client to use http/sse like:

{
  "mcpServers": {
    "fetch": {
      "url": "http://127.0.0.1:8000/sse"
    }
  }
}

If the client doesn't support http/sse (like Claude Desktop), you can leverage Minibridge's tunneling feature by running it in Web Socket mode locally (without TLS). This mode consist of two parts:

• frontend, this is where the client connect to using stdio
• backend, this is where the frontend connect to the backend running the actual tool

Start the backend:

minibridge backend --listen 127.0.0.1:8080 -- uvx mcp-server-fetch

Use the frontend:

Then configure your client to use Minibridge as a gateway:

{
  "mcpServers": {
    "fetch": {
      "command": "minibridge",
      "args": ["frontend", "--backend", "ws://127.0.0.1:8080/ws"]
    }
  }
}

Congratulations, you have configured your Minibridge to communicate with another Minibridge over the network!