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.
接入你的智能体
發布者自己的指令。不是 PlugMCP 端點。
用我們的金鑰與日誌託管一份副本。
docker run -i --rm ghcr.io/wyre-technology/alternative-payments-mcp:v1.0.8Claude Code 沒有本機指令的安裝連結。複製下方指令並在終端機中執行。
ALTERNATIVE_PAYMENTS_CLIENT_ID=<secret> ALTERNATIVE_PAYMENTS_CLIENT_SECRET=<secret> ALTERNATIVE_PAYMENTS_ENVIRONMENT=<value> MCP_TRANSPORT=<value> AUTH_MODE=<value> LOG_LEVEL=<value> claude mcp add io.github.wyre-technology-alternative-payments-mcp -- docker run -i --rm ghcr.io/wyre-technology/alternative-payments-mcp:v1.0.8在終端機中執行。
{ "mcpServers": { "io.github.wyre-technology-alternative-payments-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/wyre-technology/alternative-payments-mcp:v1.0.8" ], "env": { "ALTERNATIVE_PAYMENTS_CLIENT_ID": "<secret>", "ALTERNATIVE_PAYMENTS_CLIENT_SECRET": "<secret>", "ALTERNATIVE_PAYMENTS_ENVIRONMENT": "<value>", "MCP_TRANSPORT": "<value>", "AUTH_MODE": "<value>", "LOG_LEVEL": "<value>" } } }}claude_desktop_config.json
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者
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.
MCP server for Alternative Payments — customers, invoices, payment requests, payouts, 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.
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.
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 (production or demo, default production)The server exchanges these for a bearer token automatically and refreshes it before expiry.
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.
AUTH_MODE=gateway)Every /mcp request must also include:
X-Alternative-Payments-Client-IDX-Alternative-Payments-Client-SecretX-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.
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.
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
node dist/index.js. Does not use CONDUIT_S2S_SECRET.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.npm install
npm run build
npm test
npm run lint
Apache-2.0
MCP server for Alternative Payments — customers, invoices, payment requests, payouts, webhooks.
{ "mcpServers": { "io.github.wyre-technology-alternative-payments-mcp": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/wyre-technology/alternative-payments-mcp:v1.0.8" ], "env": { "ALTERNATIVE_PAYMENTS_CLIENT_ID": "<secret>", "ALTERNATIVE_PAYMENTS_CLIENT_SECRET": "<secret>", "ALTERNATIVE_PAYMENTS_ENVIRONMENT": "<value>", "MCP_TRANSPORT": "<value>", "AUTH_MODE": "<value>", "LOG_LEVEL": "<value>" } } }}工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
發布者列出了以下環境變數:ALTERNATIVE_PAYMENTS_CLIENT_ID, ALTERNATIVE_PAYMENTS_CLIENT_SECRET, ALTERNATIVE_PAYMENTS_ENVIRONMENT, MCP_TRANSPORT, AUTH_MODE, LOG_LEVEL。
Alternative Payments 透過 stdio 在本機執行。
上次檢查時間:2026-11-10。 MCP server for Alternative Payments — customers, invoices, payment requests, payouts, webhooks.