MCP server for Alternative Payments — customers, invoices, payment requests, payouts, webhooks.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-wyre-technology-alternative-payments-mcp": {
"args": [
"-y",
"github"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server that gives AI assistants read + safe-write access to Alternative Payments — customers, invoices, payment requests, transactions, payouts, and webhooks.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'github' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked github against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in finance
MCP server for QuickBooks Online — accounts, customers, invoices, bills, and reports.
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
Swiss accounting integration for Bexio. 310 tools for invoices, contacts, projects.
MCP server for retrieving Japanese stock market data via J-Quants API v2
MCP Security Weekly
Get CVE alerts and security updates for io.github.wyre-technology/alternative-payments-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server that gives AI assistants read + safe-write access to Alternative Payments — customers, invoices, payment requests, transactions, payouts, and webhooks.
Maintained by Wyre Technology.
This server deliberately does not move money. It exposes reads and safe writes
(creating customers, invoices, and hosted payment links). It does not implement
direct payment creation (POST /payments), which would charge a card or bank account.
The three destructive tools — ap_archive_customer, ap_archive_invoice,
ap_delete_webhook — require interactive confirmation before they run.
| Domain | Tools |
|---|---|
| customers | ap_list_customers, ap_get_customer, ap_list_customer_users, ap_create_customer, ap_add_customer_user, ap_archive_customer ⚠ |
| invoicing | ap_list_invoices, ap_get_invoice, ap_get_invoice_payment_link, ap_get_invoice_pdf_link, ap_create_invoice, ap_create_payment_request, ap_get_payment_request, ap_archive_invoice ⚠ |
| payments | ap_list_transactions, ap_get_transaction, ap_list_payouts, ap_get_payout, ap_list_payout_transactions |
| webhooks | ap_list_webhooks, ap_list_webhook_events, ap_create_webhook, ap_retry_webhooks, ap_delete_webhook ⚠ |
Plus discovery tools ap_navigate and ap_status.
Alternative Payments uses OAuth 2.0 client-credentials. Generate an API key
(client_id / client_secret) in the Partner Dashboard. Set:
ALTERNATIVE_PAYMENTS_CLIENT_IDALTERNATIVE_PAYMENTS_CLIENT_SECRETALTERNATIVE_PAYMENTS_ENVIRONMENT (production or demo, default production)The server exchanges these for a bearer token automatically and refreshes it before expiry.
Claude Code (CLI):
claude mcp add alternative-payments \
-e ALTERNATIVE_PAYMENTS_CLIENT_ID=your-client-id \
-e ALTERNATIVE_PAYMENTS_CLIENT_SECRET=your-client-secret \
-- npx -y github:wyre-technology/alternative-payments-mcp
Docker (HTTP transport, gateway mode):
docker run --rm -p 8080:8080 \
-e AUTH_MODE=env \
-e MCP_TRANSPORT=http \
-e ALTERNATIVE_PAYMENTS_CLIENT_ID=... \
-e ALTERNATIVE_PAYMENTS_CLIENT_SECRET=... \
ghcr.io/wyre-technology/alternative-payments-mcp:latest
node dist/index.jsMCP_TRANSPORT=http): streamable HTTP on MCP_HTTP_PORT (default 8080),
with /mcp and /health endpoints. Each request gets a fresh stateless server,
which is required for the WYRE MCP Gateway.npm install
npm run build
npm test
npm run lint
Apache-2.0