MCP.so
Sign In

MCP Bridge

@SecretiveShell

Basic information

Category

Developer Tools

License

MIT

Transports

stdio

Author

SecretiveShell

About MCP Bridge

A middleware to provide an openAI compatible endpoint that can call MCP tools

MCP Bridge config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "MCP-Bridge": {
      "command": "uv",
      "args": [
        "sync"
      ]
    }
  }
}

MCP Bridge tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP-Bridge?

MCP-Bridge acts as a bridge between the OpenAI API and MCP (Model Context Protocol) tools, enabling developers to leverage MCP tools through the OpenAI API interface. It is designed for developers who want to use any OpenAI-compatible client with MCP tools without requiring explicit MCP support in the client.

How to use MCP-Bridge?

Recommended installation is via Docker: clone the repository, edit the compose.yml file to reference a config.json (via volume mount, HTTP URL, or environment variable), then run docker-compose up --build -d. For manual installation, clone the repo, run uv sync, create a config.json, and execute uv run mcp_bridge/main.py. Once running, interact with the OpenAI API at http://yourserver:8000/docs. Configuration requires specifying an inference_server and mcp_servers in the config file; API key authentication is optional.

Key features of MCP-Bridge

  • Non‑streaming chat completions with MCP tools
  • Streaming chat completions with MCP tools
  • Non‑streaming completions without MCP
  • MCP sampling support
  • SSE bridge for external MCP clients
  • REST API endpoints for all MCP primitives
  • API key authentication

Use cases of MCP-Bridge

  • Use any OpenAI‑compatible client (e.g., Open Web UI) with MCP tools
  • Outsource MCP server complexity to a central bridge
  • Test MCP server configurations via SSE with tools like mcp-cli
  • Use MCP tools inside STDIO‑only clients (e.g., Claude Desktop) via a gateway

Frequently asked questions

1

Is MCP-Bridge still actively maintained?

MCP-Bridge is looking for new maintainers. Open WebUI natively supports MCP starting in v0.6.31, so MCP-Bridge is considered soft deprecated.

2

What are the runtime requirements?

It requires an inference engine with tool call support (tested with vLLM; ollama is likely compatible). Docker is the recommended installation method.

3

Where does the configuration live?

Configuration is stored in a `config.json` file, which can be provided as a volume mount, downloaded from an HTTP URL, or set as a JSON environment variable.

4

What transports and authentication does it support?

It supports an SSE bridge (`/mcp-server/sse`) for external MCP clients. Authentication is enabled via API keys passed as a Bearer token in the `Authorization` header.

5

What are the known limitations?

Streaming completions without MCP are not yet implemented. MCP resource support is planned but not currently available.

Comments

More Developer Tools MCP servers