Gateway Channels

Gateway channels provide a single MCP server endpoint for connecting AI clients like Claude Desktop and Cursor.ai.

How Gateway Channels Work

A Gateway channel creates a private MCP (Model Context Protocol) server that acts as a unified entry point to all your designated Bellatrix One tools. This allows you to:

  • Connect any MCP-compatible AI client
  • Access multiple apps through a single connection
  • Use tools directly within your preferred AI assistant
  • Maintain secure, authenticated access to your resources

Security Features

  • Each Gateway channel has unique credentials for each user
  • Tools are allowed for authorized users only
  • All connections are encrypted and authenticated
  • Access can be revoked instantly if needed

Setting Up Gateway Channels

  1. Navigate to Channels in your Bellatrix One dashboard
  2. Click "Create New Channel" and select "Gateway"
  3. Choose which apps to make available
  4. Select authorized users (including yourself) and save
  5. Click Connect and generate your MCP server credentials

Client Configuration

Most MCP clients can be configured with the Gateway channel URL and a bearer token (sometimes called an API token or key). The specific configuration format varies by client.

Claude Desktop Pro

If you have a pro or enterprise account a remote connection can be added directly. Follow the instructions to add the url and api key.

MCP Remote Server Documentation →

Claude Desktop Free

Go to Settings → Developer → Edit Config and add a block similar to the below. Replace the URL and access token with the Gateway channel connection details. Restart Claude Desktop to accept the changes. This assumes you have python installed and can run uvx.

{
  "mcpServers": {
    "bellatrix": {
      "command": "uvx",
      "args": [
        "mcp-proxy",
        "--transport=streamablehttp",
        "https://channel-XXXXXXXX-XXXXXXXX.gw.bellatrix.one/mcp"
      ],
      "env": {
        "API_ACCESS_TOKEN": "eyXXXXXXXXXXX..."
      }
    }
  }
}
Replace your url and access token.

Cursor.ai

Edit the mcp.json file. Detailed instructions are at:

Cursor MCP Documentation →

{
  "mcpServers": {
    "server-name": {
      "url": "https://channel-XXXXXXXX-XXXXXXXX.gw.bellatrix.one/mcp",
      "headers": {
        "API_KEY": "eyXXXXXXXXXXX"
      }
    }
  }
}
Replace your url and access token.

Best Practices

  • Create separate Gateway channels for different projects
  • Regularly rotate credentials for enhanced security
  • Monitor usage through the Bellatrix One dashboard
  • Test connections before sharing with team members