Alternative Payments

السجل الرسمي المالية والمدفوعات

MCP server for Alternative Payments — customers, invoices, payment requests, payouts, webhooks.

التثبيت

أضف هذا إلى إعدادات MCP في عميلك (Claude Desktop: claude_desktop_config.json، وCursor: ‏.cursor/mcp.json، ويستخدم VS Code وغيره الصيغة نفسها «mcpServers»).

OCI package ghcr.io/wyre-technology/alternative-payments-mcp:v1.0.8
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-technology/alternative-payments-mcp:v1.0.8
إعداد JSON (Claude Desktop وCursor وVS Code)
{
    "mcpServers": {
        "alternative-payments": {
            "command": "docker",
            "args": [
                "run",
                "-i",
                "--rm",
                "ghcr.io/wyre-technology/alternative-payments-mcp:v1.0.8"
            ],
            "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"
            }
        }
    }
}

متغيرات البيئة

  • ALTERNATIVE_PAYMENTS_CLIENT_ID إلزامي سري OAuth client id (API key) from the Alternative Payments Partner Dashboard.
  • ALTERNATIVE_PAYMENTS_CLIENT_SECRET إلزامي سري OAuth client secret paired with the client id.
  • ALTERNATIVE_PAYMENTS_ENVIRONMENT Target environment: 'production' or 'demo'.
  • MCP_TRANSPORT Transport mode. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
  • AUTH_MODE Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
  • LOG_LEVEL Log verbosity: debug, info, warn, error

التوثيق

مأخوذ من ملف README للمشروع على GitHub ويُحدَّث أسبوعيًا. تفتح الروابط على GitHub.

المحتويات
  1. Alternative Payments MCP Server
  2. Capabilities
  3. Authentication
  4. Quick start
  5. Transports
  6. Development
  7. License

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.

DomainTools
customersap_list_customers, ap_get_customer, ap_list_customer_users, ap_create_customer, ap_add_customer_user, ap_archive_customer ⚠
invoicingap_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 ⚠
paymentsap_list_transactions, ap_get_transaction, ap_list_payouts, ap_get_payout, ap_list_payout_transactions
webhooksap_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_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.

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-ID
  • X-Alternative-Payments-Client-Secret
  • X-Alternative-Payments-Environment (optional: production or demo)

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 use CONDUIT_S2S_SECRET.
  • 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. Startup refuses to listen until CONDUIT_S2S_SECRET is a real secret, unless MCP_ALLOW_INSECURE_DEV=1.

Development

npm install
npm run build
npm test
npm run lint

License

Apache-2.0

الأسئلة الشائعة

ما هو Alternative Payments؟

MCP server for Alternative Payments — customers, invoices, payment requests, payouts, webhooks.

كيف أثبّت Alternative Payments؟

يعمل على جهازك. في 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-technology/alternative-payments-mcp:v1.0.8. وفي العملاء الآخرين، الصق إعداد JSON من هذه الصفحة في إعدادات MCP الخاصة بهم.

هل يحتاج Alternative Payments إلى مفتاح API؟

نعم. يتطلب ALTERNATIVE_PAYMENTS_CLIENT_ID, ALTERNATIVE_PAYMENTS_CLIENT_SECRET، وتضبطها في إعداداته.

هل Alternative Payments مفتوح المصدر؟

شيفرته علنية على GitHub، لكن المستودع لا يعلن ترخيصًا قياسيًا.

من يصون Alternative Payments؟

ينشره wyre-technology. يدرجه AI.tn لكنه لا يصونه ولا يوصي به.

من سجل MCP الرسمي. الإدراج ليس توصية: راجع شيفرة الخادم وصلاحياته قبل منحه الوصول إلى بياناتك.