Connect PayPal to Claude Code

Have Claude send invoices and issue refunds in PayPal. From the terminal, inside the sessions where you already work.

How do you connect PayPal to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect PayPal, you add a PayPal MCP server: a small hosted service that exposes PayPal's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own PayPal account. No API keys pasted into config files.

claude mcp add --transport http paypal https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in PayPal once connected?

Full read-write PayPal access lets Claude create and send an invoice, record a payment, issue a partial or full refund, and initiate a payout to a vendor once you approve. The reconciliation and follow-up that used to mean logging into the dashboard happen inside the conversation, with every money-moving step gated.

Create and send an invoice to a customer with line items and due date
Issue a full or partial refund against a specific transaction
Initiate a payout to a vendor or contractor after you approve
Send a reminder on an unpaid or overdue invoice
Pull recent transactions and reconcile them against your records
Cancel or void a draft invoice before it goes out

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same PayPal access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the PayPal API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when PayPal changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build PayPal connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same PayPal connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own PayPal account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on PayPal's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to PayPal?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the PayPal account it signs in with. Revoking access is one click in PayPal.

More on the PayPal connector

PayPal connector for claude.ai Sage Intacct + Claude Code Wave + Claude Code Zoho Books + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us