satgate-mcp-bridge

MCP bridge for SatGate — connects any MCP client (Cursor, Claude Code, OpenClaw) to SatGate's budget-enforced proxy.

Quick Start

Add to your MCP client config (e.g. ~/.cursor/mcp.json or Claude Code config):

{
  "mcpServers": {
    "satgate": {
      "command": "npx",
      "args": ["-y", "satgate-mcp-bridge"],
      "env": {
        "SATGATE_URL": "https://gw.satgate.io/mcp",
        "SATGATE_TOKEN": "your-token-here",
        "SATGATE_TENANT": "your-tenant-slug"
      }
    }
  }
}

Get your token from cloud.satgate.io/cloud/mcp/connect.

How It Works

The bridge translates between stdio JSON-RPC (what MCP clients speak) and SSE transport (what SatGate's proxy uses). Every tool call goes through SatGate's budget enforcement — when the budget runs out, the agent gets a clean 402 Payment Required.

Requirements

• Node.js 18+ (uses native fetch)
• No other dependencies

Environment Variables

| Variable | Required | Description | |----------|----------|-------------| | SATGATE_URL | Yes | SatGate MCP proxy URL | | SATGATE_TOKEN | Yes | Bearer token with budget caveat | | SATGATE_TENANT | No | Tenant slug for shared multi-tenant gateways that require X-SatGate-Tenant |

Notes:

• SaaS MCP normally does not need SATGATE_TENANT
• Hybrid/shared public gateways may require it when the host alone does not identify the tenant

License

MIT