Back to Browse

Alternative Payments MCP Server

FinanceModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

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

About

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

Security Report

5.2
Moderate5.2Moderate Risk

This is a well-architected MCP server for Alternative Payments with strong security practices around credential isolation, request scoping, and destructive action confirmation. The codebase demonstrates careful handling of multi-tenant concerns using AsyncLocalStorage for both credentials and server references. Minor code quality improvements are recommended, but no critical vulnerabilities or authentication/authorization flaws were identified. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 3 high severity).

7 files analyzed · 9 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

OAuth client id (API key) from the Alternative Payments Partner Dashboard.Required

Environment variable: ALTERNATIVE_PAYMENTS_CLIENT_ID

OAuth client secret paired with the client id.Required

Environment variable: ALTERNATIVE_PAYMENTS_CLIENT_SECRET

Target environment: 'production' or 'demo'.Optional

Environment variable: ALTERNATIVE_PAYMENTS_ENVIRONMENT

Transport mode. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.Optional

Environment variable: MCP_TRANSPORT

Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.Optional

Environment variable: AUTH_MODE

Log verbosity: debug, info, warn, errorOptional

Environment variable: LOG_LEVEL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-wyre-technology-alternative-payments-mcp": {
      "env": {
        "AUTH_MODE": "your-auth-mode-here",
        "LOG_LEVEL": "your-log-level-here",
        "MCP_TRANSPORT": "your-mcp-transport-here",
        "ALTERNATIVE_PAYMENTS_CLIENT_ID": "your-alternative-payments-client-id-here",
        "ALTERNATIVE_PAYMENTS_ENVIRONMENT": "your-alternative-payments-environment-here",
        "ALTERNATIVE_PAYMENTS_CLIENT_SECRET": "your-alternative-payments-client-secret-here"
      },
      "args": [
        "-y",
        "alternative-payments-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Alternative Payments MCP Server

License Node.js

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. 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

Reviews

No reviews yet

Be the first to review this server!

Alternative Payments MCP Server - MCP server for Alternative Payments — customers, invoices, | MCP Marketplace