Alternative Payments
MCP server for Alternative Payments — customers, invoices, payment requests, payouts, webhooks.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
ghcr.io/wyre-ai/alternative-payments-mcp:v1.0.11claude mcp add alternative-payments -e 'ALTERNATIVE_PAYMENTS_CLIENT_ID=<your alternative_payments_client_id>' -e 'ALTERNATIVE_PAYMENTS_CLIENT_SECRET=<your alternative_payments_client_secret>' -e 'ALTERNATIVE_PAYMENTS_ENVIRONMENT=production' -e 'MCP_TRANSPORT=stdio' -e 'AUTH_MODE=env' -e 'LOG_LEVEL=info' -- docker run -i --rm ghcr.io/wyre-ai/alternative-payments-mcp:v1.0.11
{
"mcpServers": {
"alternative-payments": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/wyre-ai/alternative-payments-mcp:v1.0.11"
],
"env": {
"ALTERNATIVE_PAYMENTS_CLIENT_ID": "<your alternative_payments_client_id>",
"ALTERNATIVE_PAYMENTS_CLIENT_SECRET": "<your alternative_payments_client_secret>",
"ALTERNATIVE_PAYMENTS_ENVIRONMENT": "production",
"MCP_TRANSPORT": "stdio",
"AUTH_MODE": "env",
"LOG_LEVEL": "info"
}
}
}
}
Variables d'environnement
ALTERNATIVE_PAYMENTS_CLIENT_IDobligatoire secret OAuth client id (API key) from the Alternative Payments Partner Dashboard.ALTERNATIVE_PAYMENTS_CLIENT_SECRETobligatoire secret OAuth client secret paired with the client id.ALTERNATIVE_PAYMENTS_ENVIRONMENTTarget environment: 'production' or 'demo'.MCP_TRANSPORTTransport mode. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.AUTH_MODECredential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.LOG_LEVELLog verbosity: debug, info, warn, error
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
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.
| 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.
Authentication
Alternative Payments uses OAuth 2.0 client-credentials. Generate an API key
(client_id / client_secret) in the Partner Dashboard.
Copy .env.example. The stdio transport reads these variables and does not use CONDUIT_S2S_SECRET:
ALTERNATIVE_PAYMENTS_CLIENT_IDALTERNATIVE_PAYMENTS_CLIENT_SECRETALTERNATIVE_PAYMENTS_ENVIRONMENT(productionordemo, defaultproduction)
The server exchanges these for a bearer token automatically and refreshes it before expiry.
HTTP service-to-service auth
CONDUIT_S2S_SECRET is required when MCP_TRANSPORT=http. If it is empty, or a known placeholder (changeme, your-s2s-secret, secret, placeholder, and the other example values), the process logs an error and exits non-zero. It never prints the secret. Compose will not start when the variable is unset.
Set MCP_ALLOW_INSECURE_DEV=1 only for local development to start without the secret. The process logs a loud warning, does not check X-Gateway-S2S, and binds 127.0.0.1 only. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) is ignored in that mode and the override is logged. A placeholder secret is still refused.
MCP_HTTP_HOST is honored when a real CONDUIT_S2S_SECRET is set. If MCP_HTTP_HOST is unset, the server keeps the historical default and binds 0.0.0.0. The container image and Compose set 0.0.0.0 and AUTH_MODE=gateway. Publish the port on loopback unless a proxy sits in front.
With a real secret, every /mcp request must include:
X-Gateway-S2S: t=<unix seconds>,v1=<hex hmac-sha256>
v1 is the hex HMAC-SHA256 of the ASCII string t=<unix seconds>, keyed with CONDUIT_S2S_SECRET. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns 401 before vendor credentials are read.
Gateway mode (AUTH_MODE=gateway)
Every /mcp request must also include:
X-Alternative-Payments-Client-IDX-Alternative-Payments-Client-SecretX-Alternative-Payments-Environment(optional:productionordemo)
A request missing the client id or secret gets 401 and does not fall back to ALTERNATIVE_PAYMENTS_CLIENT_ID / ALTERNATIVE_PAYMENTS_CLIENT_SECRET in the process environment. The checked-in Compose service sets no static vendor credentials.
Single-tenant HTTP (AUTH_MODE=env)
/mcp still requires a valid X-Gateway-S2S header. Vendor credentials come from the ALTERNATIVE_PAYMENTS_* environment variables when the request does not carry the client-id and client-secret headers.
/health always returns 200. It does not require authentication and does not read vendor credentials.
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-AI/alternative-payments-mcp
Docker (HTTP transport, gateway mode):
The image listens on 0.0.0.0 inside the container and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the S2S secret. In gateway mode, Alternative Payments credentials arrive on each request as headers; they are not read from the environment.
docker run --rm \
-p 127.0.0.1:8080:8080 \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \
ghcr.io/wyre-ai/alternative-payments-mcp:latest
Compose refuses to start when CONDUIT_S2S_SECRET is unset, sets AUTH_MODE=gateway, publishes 127.0.0.1:8080:8080, and does not inject static vendor credentials:
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up
The gateway signs each /mcp call:
t=$(date +%s)
sig=$(printf 't=%s' "$t" | openssl dgst -sha256 -hmac "$CONDUIT_S2S_SECRET" -hex | awk '{print $NF}')
curl -sS -X POST http://127.0.0.1:8080/mcp \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-H "X-Gateway-S2S: t=${t},v1=${sig}" \
-H "X-Alternative-Payments-Client-ID: $ALTERNATIVE_PAYMENTS_CLIENT_ID" \
-H "X-Alternative-Payments-Client-Secret: $ALTERNATIVE_PAYMENTS_CLIENT_SECRET" \
-H "X-Alternative-Payments-Environment: production" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses ALTERNATIVE_PAYMENTS_CLIENT_ID and ALTERNATIVE_PAYMENTS_CLIENT_SECRET. This is separate from the gateway Compose service:
docker run --rm \
-p 127.0.0.1:8080:8080 \
-e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \
-e AUTH_MODE=env \
-e ALTERNATIVE_PAYMENTS_CLIENT_ID="$ALTERNATIVE_PAYMENTS_CLIENT_ID" \
-e ALTERNATIVE_PAYMENTS_CLIENT_SECRET="$ALTERNATIVE_PAYMENTS_CLIENT_SECRET" \
ghcr.io/wyre-ai/alternative-payments-mcp:latest
Local HTTP without a secret is development-only. It binds 127.0.0.1 and logs a warning:
MCP_ALLOW_INSECURE_DEV=1 npm run start:http
Transports
- stdio (default):
node dist/index.js. Does not useCONDUIT_S2S_SECRET. - HTTP (
MCP_TRANSPORT=http): streamable HTTP onMCP_HTTP_PORT(default 8080), with/mcpand/healthendpoints. Each request gets a fresh stateless server, which is required for the WYRE MCP Gateway. Startup refuses to listen untilCONDUIT_S2S_SECRETis a real secret, unlessMCP_ALLOW_INSECURE_DEV=1.
Development
npm install
npm run build
npm test
npm run lint
License
Apache-2.0
Questions fréquentes
Qu'est-ce que Alternative Payments ?
MCP server for Alternative Payments — customers, invoices, payment requests, payouts, webhooks.
Comment installer Alternative Payments ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add alternative-payments -e 'ALTERNATIVE_PAYMENTS_CLIENT_ID=<your alternative_payments_client_id>' -e 'ALTERNATIVE_PAYMENTS_CLIENT_SECRET=<your alternative_payments_client_secret>' -e 'ALTERNATIVE_PAYMENTS_ENVIRONMENT=production' -e 'MCP_TRANSPORT=stdio' -e 'AUTH_MODE=env' -e 'LOG_LEVEL=info' -- docker run -i --rm ghcr.io/wyre-ai/alternative-payments-mcp:v1.0.11. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour Alternative Payments ?
Oui. Il attend ALTERNATIVE_PAYMENTS_CLIENT_ID, ALTERNATIVE_PAYMENTS_CLIENT_SECRET, à renseigner dans sa configuration.
Alternative Payments est-il open source ?
Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.
Qui maintient Alternative Payments ?
Il est publié par WYRE-AI. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.