Satgate MCP Server

Satgate MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Why • Build • Features • Quick Start • Docs • Website • Blog.

What you get

SatGate is an Economic Firewall for AI agent requests. Drop it in front of your APIs and MCP tools to enforce scoped authority, budgets, paid-rail context, and Evidence Pack receipts before agents act.

• 🛡️ Capability Tokens (Macaroons) — Cryptographic credentials with built-in caveats, delegation, and next-request revocation. Not API keys — tokens that agents can safely sub-delegate
• 🎯 MCP-Aware — Parses MCP JSON-RPC tool calls. Know that Agent X spent $47 on search_database and $12 on send_email — not just "1,000 requests."
• 💰 Budget Enforcement — Hard stops per agent, team, or API. When the budget hits zero, requests are blocked. Not logged. Not alerted. Blocked
• ⚡ Paid-Rail Governance — Govern paid API access across L402, x402, API-key billing, and enterprise ledgers without making any one rail the control plane
• 🔒 Default-Deny — All routes require valid credentials unless explicitly public. Zero Trust by design
• 🚀 <50ms Overhead — Lightweight Go proxy. Adds governance without adding latency

What the assistant can call

Once Satgate is connected, these are the calls the assistant has available:

• name — public-health
• Macaroons — Bearer tokens with embedded caveats (expiry, scope, budget, IP). Not API keys — they support delegation without server roundtrips
• Delegation — Agent A gives Agent B a sub-token with reduced permissions and a $50 budget cap. B can't escalate
• Paid — rail context**: SatGate treats L402, x402, API-key billing, and enterprise ledgers as rails to govern around. Evidence Packs preserve which rail was
• Per — tool costs**: web_search: 5, dalle_generate: 50 (wildcard patterns supported)
• Policy — Description
• public — No authentication
• capability — Requires valid Macaroon
• l402 — Requires Lightning payment and records paid-rail context
• Language — Package
• JavaScript — npm install @satgate/sdk

Configuration and credentials

You will need 5 environment variables: ADMIN_TOKEN, LIGHTNING_BACKEND, SATGATE_API_KEY, YOUR_CAPABILITY_TOKEN, CAPABILITY_ROOT_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

This sits in the payments and commerce group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Satgate's toolset — name, Macaroons, Delegation and 8 more — is a fair guide to whether it matches your workflow. It is maintained by satgate-io; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Satgate's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 11 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Satgate.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the satgate mcp server does with a few real requests.