Alternative Payments MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Alternative Payments MCP Serverlist my overdue invoices and get the payment link for the latest one"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Alternative Payments MCP Server
An MCP server for the Alternative Payments partner API. It lets an AI agent work with an MSP's billing in Alternative Payments: customers, invoices, standalone payment requests, payment transactions, payouts and webhook subscriptions.
Transport: MCP Streamable HTTP at
POST /mcp, health probe atGET /healthStateless and multi-tenant: credentials arrive on every request as HTTP headers and are never stored; the OAuth access token is obtained per request and not cached
Python 3.12, uv, FastMCP, httpx
License: Apache-2.0, Copyright 2026 MSPbots.ai
Authentication headers
Header | Required | Type | Default | Allowed values | Description | Example |
| Yes | string | none | - | API key client id |
|
| Yes | string | none | - | Client secret paired with the client id |
|
| No | string |
|
|
|
|
Where to get them:
Client id / secret: in the Alternative Payments Partner Dashboard open Team Preferences -> API Keys -> Generate API Key. The server exchanges them for a short-lived bearer token (OAuth 2.0 client credentials) on each request; the secret is only sent to the token endpoint.
Scopes: pick read scopes for Customers, Invoices, Payments, Payouts and Webhooks for the read tools. Add the matching write scopes only if the agent should create or archive customers/invoices, create payment requests, or manage webhooks.
Environment: use
demofor a sandbox API key.
A request to /mcp without the required headers gets HTTP 401 with the list of required
headers; an unknown environment gets HTTP 400.
Related MCP server: Agent Billy MCP Server
Tools
All tools return a JSON string. List tools return {items, count, has_more, next_cursor};
pass next_cursor as after to get the next page. limit defaults to 50 (max 100).
Amounts are in US dollars; USD is the only supported currency.
Read tools:
Tool | Purpose | Parameters (required in bold) |
| Show the tools of one area | domain ( |
| Check the credentials and environment | - |
| List customers | limit, after, company_name |
| One customer | id |
| Portal users of a customer | id, limit, after |
| List invoices | status ( |
| One invoice | id |
| Hosted pay link for an invoice | id |
| PDF download link for an invoice | id |
| One payment request | id |
| Payments, refunds, chargebacks | limit, after, before, type, status, customer_id, invoice_id, payment_method, created_at_start, created_at_end |
| One transaction | id |
| Payouts to the MSP | limit, after, status, start_date, end_date |
| One payout | id |
| Transactions inside a payout | id |
| Webhook subscriptions | limit, topic, after |
| Webhook deliveries | limit, status ( |
Write tools (change real billing data; descriptions tell the agent to call them only when the user explicitly asks):
Tool | Purpose | Parameters (required in bold) |
| Create a customer | name, email, legal_name, external_id, street_address, city, state, postal_code, country |
| Add a portal user to a customer | id, email, first_name, last_name |
| Archive a customer (destructive) | id |
| Create an invoice | customer_id, currency ( |
| Create a standalone pay link | amount, currency ( |
| Archive an invoice (destructive) | id |
| Subscribe an https endpoint to a topic | endpoint_url, topic, secret_key |
| Re-send failed webhook deliveries | - |
| Delete a subscription (destructive) | subscription_id |
Errors come back as a JSON envelope instead of an exception:
{"error": {"code": "unauthorized", "message": "Alternative Payments rejected the client id / secret (token request failed)", "retryable": false}}code is one of not_configured, unauthorized, not_found, invalid_argument,
rate_limited, upstream_error.
Run locally
uv sync
uv run python -m alternative_payments_mcp # listens on 0.0.0.0:8080or with Docker:
docker build --platform linux/amd64 -t alternative-payments-mcp:dev .
docker run --rm -p 8080:8080 alternative-payments-mcp:devConfiguration (environment variables, all optional): MCP_HTTP_HOST (default 0.0.0.0),
MCP_HTTP_PORT (default 8080), LOG_LEVEL (default INFO). Credentials are never read from
the environment.
Testing example
# list tools
curl -s http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "X-Alternative-Payments-Client-Id: your-client-id" \
-H "X-Alternative-Payments-Client-Secret: your-client-secret" \
-H "X-Alternative-Payments-Environment: demo" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
# overdue invoices
curl -s http://localhost:8080/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "X-Alternative-Payments-Client-Id: your-client-id" \
-H "X-Alternative-Payments-Client-Secret: your-client-secret" \
-H "X-Alternative-Payments-Environment: demo" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"ap_list_invoices","arguments":{"status":"OVERDUE","limit":10}}}'Unit tests (no network access needed):
uv run pytestDelivery notes
Tool count (26). Above the suggested 20 because the tool names are an existing contract used by agents and tenant connections; none were merged or removed. The
ap_prefix is also kept for the same reason.Write tools. Nine tools change data. They are annotated (
readOnlyHint=false; archive and delete alsodestructiveHint=true), validate their input before calling the API (USD only,YYYY-MM-DDdates, https URLs), and their descriptions tell the agent to act only on an explicit request.Currency. The partner API bills in USD only.
ap_create_payment_requestkeeps itscurrencyargument for compatibility and rejects anything other thanUSD.
License
This server cannot be deployed
Maintenance
Related MCP Connectors
Stripe payments for AI agents. Create links, verify, manage customers.
Manage Apollo invoices and customers with entity-scoped OAuth and optional read/write access.
Connect your AI to your Well financial data - invoices, companies, contacts.
Connect AI agents to 580+ APIs with OAuth or API-key auth. Hosted gateway; API pricing varies.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to interact with multiple payment providers (Stripe, Paystack) through a unified API. Supports payment initialization, verification, refunds, customer management, and invoicing without requiring knowledge of specific provider implementations.2-
- AlicenseNot gradedqualityDmaintenanceProvides secure, role-based access to Stripe billing operations for AI assistants like Claude and Cursor. It enables users to manage customers, subscriptions, invoices, and refunds through a local proxy with server-side permission enforcement.6 npmMIT

Alternative Payments MCPofficial
FlicenseNot gradedqualityAmaintenanceProvides AI assistants with read and safe-write access to Alternative Payments customers, invoices, payment requests, transactions, payouts, and webhooks without directly moving money.-
Subotiz MCPofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage subscriptions, usage-based billing, payments, refunds, tax compliance, and invoicing to drive revenue growth.1MIT