minibridge
by acuvity
Minibridge serves as a bridge between MCP servers and the outside world, facilitating communication between Agents and MCP servers. It securely exposes MCP servers to the internet and optionally enables seamless integration with the Acuvity Platform.
Last updated: N/A
What is minibridge?
Minibridge is a connector that bridges MCP servers and external agents. It handles data streams and securely exposes MCP servers to the internet, optionally integrating with the Acuvity Platform.
How to use minibridge?
Minibridge can be used in 'all-in-one' mode, or with separate backend and frontend components. The backend exposes the MCP server API over WebSockets. The frontend provides compatibility with existing agents using POST+SSE, HTTP+STREAM (coming soon), or plain STDIO. It can also be integrated with a Policer for enhanced security and policy enforcement.
Key features of minibridge
Acts as a bridge between MCP servers and the outside world
Securely exposes MCP servers to the internet
Supports WebSocket-based interface for MCP server API
Offers frontend compatibility with POST+SSE, HTTP+STREAM (coming soon), and STDIO
Integrates with a Policer for user authentication, authorization, and request analysis
Use cases of minibridge
Exposing MCP servers to external agents and applications
Securing MCP server access with client authentication and TLS
Integrating MCP servers with the Acuvity Platform
Implementing policy-based controls for MCP server requests
Maintaining backward compatibility with existing agents using various protocols
FAQ from minibridge
What MCP protocol versions are supported?
What MCP protocol versions are supported?
Currently, Minibridge is compatible with any compliant MCP server using protocol version 2024-11-05. Support for version 2025-03-26 is in progress.
What is the purpose of the Policer integration?
What is the purpose of the Policer integration?
The Policer is responsible for user authentication, role-based user authorization, input analysis and logging, full request tracing, and more advanced policy-based controls.
What happens if the Policer denies a request?
What happens if the Policer denies a request?
If the request is denied (or the Policer does not return 200 OK), Minibridge will not forward it to the MCP server. Instead, it will return a descriptive MCP error to the client, indicating why the request was blocked.
What protocols does the frontend support?
What protocols does the frontend support?
The frontend can expose a local interface using POST+SSE, HTTP+STREAM (coming soon), or plain STDIO.
Does Minibridge support connecting to an MCP server using HTTP?
Does Minibridge support connecting to an MCP server using HTTP?
No, this is a feature that is still being worked on.