Skip to content

corridrlabs/mcp

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Corridor MCP Server

Corridor MCP exposes Corridor API operations as MCP tools so AI agents can run payment/account workflows against a real Corridor account.

What this enables

  • 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

Build

cd mcp
go build -o corridor-mcp ./cmd

Configure

export PAYDAY_API_KEY="pk_live_..."
export PAYDAY_API_URL="https://api.corridormoney.net"
# local: http://localhost:8080

Run

./corridor-mcp

Available tools

Account and wallets

  • account_settings_get
  • account_settings_update
  • wallets_list
  • wallets_create
  • liquidity_get
  • notifications_list

Funding and payouts

  • funding_sources_list
  • funding_sources_add
  • fund_wallet
  • payouts_list
  • payouts_create

Commerce flows

  • customers_list
  • customers_create
  • payment_links_list
  • payment_links_create
  • invoices_list
  • invoices_create
  • invoice_get
  • invoice_payment_link
  • invoice_send
  • invoice_remind

Developer operations

  • api_keys_list
  • api_keys_create
  • api_keys_revoke
  • webhooks_list
  • webhooks_create
  • webhooks_delete

Social and transfers

  • social_goals_list
  • social_goals_create
  • social_goal_get
  • social_goal_contributions
  • social_goal_contribute
  • social_goal_eject
  • social_pay
  • exchange_rate_get

Idempotency

Mutating tools accept optional idempotency_key. If provided, MCP sends it as X-Idempotency-Key.

Examples:

  • fund_wallet
  • payouts_create
  • payment_links_create
  • social_goals_create
  • social_goal_contribute
  • social_pay

Plan-gated features

Corridor enforces paid-plan access on key routes (HTTP 402 when blocked), including:

  • API key management
  • Webhooks
  • Payouts
  • EWA
  • Treasury sweep

Security notes

  • Keep PAYDAY_API_KEY server-side only
  • Never expose keys in browser clients
  • Rotate/revoke keys regularly
  • Verify webhook signatures in your own endpoint

Example (Claude Desktop)

{
  "mcpServers": {
    "corridor": {
      "command": "/path/to/corridor-mcp",
      "env": {
        "PAYDAY_API_KEY": "pk_live_...",
        "PAYDAY_API_URL": "https://api.corridormoney.net"
      }
    }
  }
}

About

Corridor open-source corridor-mcp

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages