MCP Broker
Bellatrix One is a powerful intermediary that aggregates multiple MCP servers into a unified interface. It enables AI agents to access diverse tools and data sources through a single connection point.
What is an MCP Broker?
An MCP Broker sits between AI clients and multiple MCP servers, managing connections and coordinating access. Instead of connecting to each server individually, clients connect once to the broker and gain access to all available tools.
URL
Below is the externally facing, MCP Server url for Bellatrix One. Add it to your MCP client or agent:
https://mcp.bellatrix.one/mcpOnce connected you can interact with Bellatrix One through chat. Examples:
refresh Bellatrix connectorsadd a Github connectoredit that connector
Example Instructions
The following example shows how to set up a Github connector with Claude. Similar steps apply when using other connectors or MCP clients.
- Paste in the connector url for Bellatrix One -
https://mcp.bellatrix.one/mcp - Click Connect
- Start a new chat and enter "refresh Bellatrix connectors"
- Enter "add a Github connector through Bellatrix"
- Click the URL presented to add the new Github connector
- From that page, sign in or sign up to Bellatrix One if needed
- Go to your Github account - Settings - Developer Settings - Fine Grained Tokens
- Configure a new token with at least read-access and paste that into Bellatrix One
- Once configuration is complete the Bellatrix One page can be closed.
- In Claude, enter "refresh Bellatrix connectors"
Repeat from step 6 to add another Github connector. You can now interact with multiple Github connectors through Claude.
Key Features
Tool Aggregation
The broker collects functionalities from various MCP servers into a single interface. This provides unified access to all your tools without managing multiple connections.
Concurrent Access
Multiple clients can connect to and use MCP-enabled resources simultaneously. The broker handles coordination and ensures smooth parallel operations.
Multiple Connectors of the Same Type
You can manage multiple connectors of the same type simultaneously. For example, connect to several different Google Drive accounts, multiple databases, or several instances of any other integration — each managed independently through a single broker connection.
Security & Authentication
The broker provides enterprise-grade security features:
- JWT (JSON Web Token) authentication for secure client connections
- Fine-grained, tag-based access control
- User and team-level permissions
- Encrypted credential storage
Dynamic Configuration
The broker dynamically manages server configurations:
- Automatic tool discovery from connected servers
- Resolution of tool name conflicts across servers
- Real-time updates when tools are added or removed
- Intelligent routing of requests to appropriate servers
How It Works
When an AI agent connects to the MCP Broker:
- The agent authenticates using OAuth or JWT tokens
- The broker provides a unified list of available tools from all connected servers
- When the agent invokes a tool, the broker routes the request to the correct server
- Results are returned through the broker to the agent
- All operations are logged and monitored for security
Example Use Case
A broker can connect an AI agent to a variety of sources simultaneously. For example, you might connect to financial data APIs, internal databases, Google Drive, Slack, and other SaaS tools. The agent sees all these as a single set of capabilities rather than separate systems.
Benefits
- Simplified client configuration - connect once, access everything
- Centralized security and access control
- Better performance through connection pooling and caching
- Easier monitoring and logging of tool usage
- Reduced context overload by filtering relevant tools
Getting Started
Bellatrix One acts as an MCP Broker for your tools and connections. When you connect AI clients to Bellatrix One, they automatically gain access to all your configured connectors and tools.