Agentpay Gateway Mcp

Name: Agentpay Gateway Mcp
Author: Rumblingb

by Rumblingbcommunityv1.0.0

An HTTP-based MCP gateway that proxies an agent’s requests to 42 backend servers through a single MCP endpoint. It supports credit-based per-call billing, account status checks, and Stripe upsell links, with demo and Supabase/Stripe-backed production modes.

From the registry: Centralized API gateway routing to MCP servers with per-call billing

GitHub Repository

Install & configure

Prerequisites

required
Install Python dependencies
Install Python 3.10+ and the required Python packages to run the gateway server locally.
```
$ pip install mcp httpx anyio
```

optional

Set production environment variables

For full production mode, configure Supabase and Stripe environment variables before starting the server. Demo mode does not require these.

$ export SUPABASE_URL=<your-supabase-url>
export SUPABASE_SERVICE_KEY=<your-supabase-service-key>
export STRIPE_API_KEY=<your-stripe-api-key>
export STRIPE_CHECKOUT_LINK=<your-stripe-checkout-link>

required
Start the HTTP gateway server
The MCP server runs as a separate HTTP service and must be started before connecting a client. Demo mode can be started without database configuration.
```
$ python server.py --port 8000
```
required
Obtain an AgentPay API key
Clients authenticate to the gateway using the X-API-Key header.

Install in your client

Paste into the AI you're chatting with — it will figure out the rest

Please install the `agentpay-gateway-mcp` MCP server into my current AI client (that's you).

Required prerequisites (do these first if not already done):
- **Install Python dependencies** — Install Python 3.10+ and the required Python packages to run the gateway server locally. Run: `pip install mcp httpx anyio`
- **Start the HTTP gateway server** — The MCP server runs as a separate HTTP service and must be started before connecting a client. Demo mode can be started without database configuration. Run: `python server.py --port 8000`
- **Obtain an AgentPay API key** — Clients authenticate to the gateway using the X-API-Key header.

Optional prerequisites:
- Set production environment variables — For full production mode, configure Supabase and Stripe environment variables before starting the server. Demo mode does not require these. Run: `export SUPABASE_URL=<your-supabase-url>
export SUPABASE_SERVICE_KEY=<your-supabase-service-key>
export STRIPE_API_KEY=<your-stripe-api-key>
export STRIPE_CHECKOUT_LINK=<your-stripe-checkout-link>`

Canonical MCP server config (HTTP transport):
- url: `http://<your-host>:<your-port>/mcp`
- headers:
  - `X-API-Key`: `<your-api-key>`

Note: This server uses HTTP transport, not stdio. The README shows localhost:8000 as the example endpoint after starting the server with --port 8000. Demo mode works without Supabase or Stripe; production mode requires SUPABASE_URL, SUPABASE_SERVICE_KEY, STRIPE_API_KEY, and STRIPE_CHECKOUT_LINK.

Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.

Note: This server uses HTTP transport, not stdio. The README shows localhost:8000 as the example endpoint after starting the server with --port 8000. Demo mode works without Supabase or Stripe; production mode requires SUPABASE_URL, SUPABASE_SERVICE_KEY, STRIPE_API_KEY, and STRIPE_CHECKOUT_LINK.