PopMCPPayments and finance MCP stack for your AI
Card payments, subscription billing, the store's own orders and both ledgers a bookkeeper might be running.
- Stripe
- Xero
- QuickBooks
- Chargebee
- Shopify
app.popmcp.com/mcpThe 5 connections
Money arrives in one system, is billed in a second, is refunded in a third, and has to be explained in a fourth before anyone can close the month.
- StripeAPI credentialTest helpersCustomersTreasuryIssuing581tools26triggers
- XeroOAuthPayrollPayroll auProjectsFiles364tools25triggers
- QuickBooksOAuthSalesTransactionsPurchasesLists133tools23triggers
- ChargebeeAPI credentialSubscriptionsInvoicesCustomersHosted pages466tools24triggers
- ShopifyOAuthOrdersCollectionsCustomersInventory70tools24triggers
Across the stack663 read and 951 write operations, 213 API modules1,614tools122triggers
One question, every connection
The tool names below are the real ones your client calls. Check any chain against the catalog on the integration’s own page.
What is outstanding right now, and who do I chase first?
- Stripe
stripe_list_invoicesstripe_list_payment_intents - Chargebee
chargebee_list_invoiceschargebee_retrieve_a_customer - Xero
xero_get_invoicesxero_get_contacts - QuickBooks
quickbooks_run_report
One receivables list built from every system that can raise an invoice, instead of three partial ones that each look complete.
Reconcile last month without an export.
- Stripe
stripe_list_chargesstripe_list_payoutsstripe_list_refunds - Shopify
shopify_get_ordersshopify_get_order_refunds - Xero
xero_get_bank_transactionsxero_get_payments
Payouts matched to orders matched to bank lines, with the unmatched rows named — which is the only part of reconciliation that needed a person.
Which failed payments actually cost us a subscription?
- Stripe
stripe_list_payment_intentsstripe_list_subscriptions - Chargebee
chargebee_list_subscriptionschargebee_list_credit_notes - QuickBooks
quickbooks_queryquickbooks_get_invoice
A failed charge, the subscription behind it and the invoice it was meant to settle, joined in one read rather than three lookups.
Turning it on
Nothing to deploy, and nothing to install on the provider side.
- Connect the accounts
One connection per store, property or ad account. Three authorise with OAuth, two take an API credential. Credentials are encrypted at rest and never reach your AI client.
- Tick what each client reaches
Your client signs in to PopMCP with OAuth and gets only the connections you approve. Writes run the moment it calls them, so keep reporting teammates on read-only.
- Register one URL
app.popmcp.com/mcp, once per client. Claude, ChatGPT, Codex and the rest reach the same five connections with the same permissions.
Five connections need Starter or above — the free tier holds two. See what each plan includes.
The other stacks
Same endpoint, same controls. Most teams end up running two or three of them side by side.
Questions about the payments and finance stack
Do I need both Xero and QuickBooks?
Almost nobody does. They are listed together because the rest of the stack is identical either way: connect whichever ledger your books are in. Agencies and bookkeepers are the exception — they connect both because their clients are split across the two.
Can an agent move money?
Some of these connections expose write tools that create refunds, credit notes and invoices, and they run as soon as the AI calls them. This is the stack to be most deliberate about: connect it only to the clients that need it, and keep every teammate who is only reporting on read-only, which hides the write tools entirely.
Does PopMCP see our card data?
No. PopMCP holds the API credential or OAuth connection you authorise, encrypted at rest, and calls the provider on your behalf. Card numbers live with the processor, exactly as they do when you use its own dashboard. Your AI client never receives the credential either.
Connect the payments and finance stack to your AI
Add Stripe, Xero, QuickBooks and the rest with credentials you already own, and get one secure MCP URL for all of them.