Corridor MCP exposes Corridor API operations as MCP tools so AI agents can run payment/account workflows against a real Corridor account.
- Server-to-server style usage with
X-API-Key(Paystack-like integration model) - Wallet, funding, payouts, invoices, links, webhooks, social goals, and account operations
- Optional idempotency keys on mutating tools for safe retries
cd mcp
go build -o corridor-mcp ./cmdexport PAYDAY_API_KEY="pk_live_..."
export PAYDAY_API_URL="https://api.corridormoney.net"
# local: http://localhost:8080./corridor-mcpaccount_settings_getaccount_settings_updatewallets_listwallets_createliquidity_getnotifications_list
funding_sources_listfunding_sources_addfund_walletpayouts_listpayouts_create
customers_listcustomers_createpayment_links_listpayment_links_createinvoices_listinvoices_createinvoice_getinvoice_payment_linkinvoice_sendinvoice_remind
api_keys_listapi_keys_createapi_keys_revokewebhooks_listwebhooks_createwebhooks_delete
social_goals_listsocial_goals_createsocial_goal_getsocial_goal_contributionssocial_goal_contributesocial_goal_ejectsocial_payexchange_rate_get
Mutating tools accept optional idempotency_key. If provided, MCP sends it as X-Idempotency-Key.
Examples:
fund_walletpayouts_createpayment_links_createsocial_goals_createsocial_goal_contributesocial_pay
Corridor enforces paid-plan access on key routes (HTTP 402 when blocked), including:
- API key management
- Webhooks
- Payouts
- EWA
- Treasury sweep
- Keep
PAYDAY_API_KEYserver-side only - Never expose keys in browser clients
- Rotate/revoke keys regularly
- Verify webhook signatures in your own endpoint
{
"mcpServers": {
"corridor": {
"command": "/path/to/corridor-mcp",
"env": {
"PAYDAY_API_KEY": "pk_live_...",
"PAYDAY_API_URL": "https://api.corridormoney.net"
}
}
}
}