Alternative Payments MCP Server

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.

Capabilities

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.

Plus discovery tools ap_navigate and ap_status.

Related MCP server: paystack-mcp-server

Authentication

Alternative Payments uses OAuth 2.0 client-credentials. Generate an API key (client_id / client_secret) in the Partner Dashboard. Set:

• ALTERNATIVE_PAYMENTS_CLIENT_ID

• ALTERNATIVE_PAYMENTS_CLIENT_SECRET

• ALTERNATIVE_PAYMENTS_ENVIRONMENT (production or demo, default production)

The server exchanges these for a bearer token automatically and refreshes it before expiry.

Quick start

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

Transports

• stdio (default): node dist/index.js

• HTTP (MCP_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.

Development

npm install
npm run build
npm test
npm run lint

License

Apache-2.0