Connect AI agents to the Magpie Payment Platform. Process payments, create checkouts, send invoices, and manage payment links through natural conversation.
Add this to your Claude Desktop config and restart. No installation needed.
{ "mcpServers": { "magpie": { "command": "npx", "args": ["mcp-remote", "https://mcp.magpie.im/mcp"] } } }
Requires Node.js 18+ for npx / mcp-remote
Add the config above and restart Claude Desktop. The mcp-remote bridge connects to the server automatically.
Your browser opens to an OAuth flow. Enter your Magpie API keys from the Magpie Dashboard. This only happens once.
Ask Claude to process payments, create checkout sessions, send invoices, or manage payment links. 33 tools are available.
| Method | Payments | Checkout | Requests | Links |
|---|---|---|---|---|
| Card | ✓ | ✓ | ✓ | ✓ |
| GCash | ✓ | ✓ | ✓ | ✓ |
| Maya | ✓ | ✓ | ✓ | ✓ |
| GrabPay | ✓ | ✓ | — | — |
| BPI | ✓ | ✓ | — | — |
| Alipay | ✓ | ✓ | — | — |
| UnionPay | ✓ | ✓ | — | — |
| WeChat Pay | ✓ | ✓ | — | — |
| QR PH | ✓ | — | — | — |
| InstaPay | ✓ | — | — | — |
Run the MCP server locally. Provide your API keys as environment variables instead of using the hosted OAuth flow.
npm install -g magpie-mcp-server
Point Claude Desktop at the local server with your Magpie credentials:
{ "mcpServers": { "magpie": { "command": "npx", "args": ["-y", "magpie-mcp-server"], "env": { "MAGPIE_PUBLIC_KEY": "your_public_key", "MAGPIE_SECRET_KEY": "your_secret_key" } } } }
Claude Desktop is a GUI app and doesn't inherit your shell's PATH. If you use a Node version manager (NVM, fnm, Volta, Herd), the bare npx command won't be found.
Fix: use the full path to npx and add its directory to env.PATH:
{
"mcpServers": {
"magpie": {
"command": "/full/path/to/npx",
"args": ["mcp-remote", "https://mcp.magpie.im/mcp"],
"env": {
"PATH": "/full/path/to/node/bin:/usr/local/bin:/usr/bin:/bin"
}
}
}
}
Find your path by running which npx in a terminal.
The mcp-remote bridge caches OAuth tokens locally. To force a fresh authorization flow, delete the cache and restart Claude Desktop:
rm -rf ~/.mcp-auth/
The next time Claude Desktop connects, your browser will open the authorization page where you can enter new API keys.
Your Magpie API keys are stored server-side in an encrypted PostgreSQL database, associated with your OAuth client. They never leave the server.
Your local machine only stores an OAuth access token (in ~/.mcp-auth/) which authenticates requests to the MCP server. The access token expires after 1 hour and is automatically refreshed.
You need Node.js 18+ installed (for the npx and mcp-remote commands). No other installation is required—the hosted server handles everything else.
If you prefer to self-host, you can install the server from npm with npm install -g magpie-mcp-server and provide your own API keys as environment variables.
Anything the Magpie API supports. Examples:
• "Charge 500 PHP to the customer's GCash"
• "Create a checkout session for 1,200 PHP with card and Maya"
• "Send a payment request for 3,000 PHP to juan@example.com"
• "Create a reusable payment link for 250 PHP"
• "Show me all charges from today"
• "Refund charge ch_abc123"