C1 Bridge
Connect C1 to private systems and MCP servers without opening inbound firewall rules.
Reach private systems without exposing the network.
Outbound-only connectivity
The bridge client opens and maintains the connection to C1, so your network does not need an inbound listener or firewall exception.
Multiple private services
One bridge can advertise multiple MCP servers and supported private services, each with its own name, port, path, and transport.
Governed through C1
Register each advertised MCP server under a C1 app, discover its tools, and govern access through the same identity and policy model.
PRIVATE CONNECTIVITY
Connect private apps and MCP Servers with no inbound firewall rules
How it works
Run bridge-client on a VM, container, laptop, or Kubernetes cluster that can reach the apps, infrastructure, databases, and MCP servers you want C1 to access.
MULTIPLEXING
Multiplex connectors and MCP servers behind a single bridge.
How it works
Carry traffic for multiple connectors and MCP servers over one bridge-client session instead of deploying a bridge process for every endpoint.
