You can connect PayPal to Claude in a few minutes using the Model Context Protocol (MCP), and once it’s connected, Claude can look up an invoice, check an order, or trace a transaction without you logging into the PayPal dashboard to find it. This guide covers both ways to do it: PayPal’s official remote MCP server connected directly, and connecting it through a gateway if you use more than one AI client.

What the PayPal MCP server actually does

PayPal publishes an official remote MCP server at mcp.paypal.com/mcp. It exposes your account’s invoices, orders, and transactions as tools Claude can call directly, so prompts like these work against your live PayPal data:

  • “Show me every invoice I sent last month that’s still unpaid.”
  • “What was the status of order #12345?”
  • “Find the transaction tied to this email and summarize it.”
  • “Draft a new invoice for this client for $500.”

Claude acts through the same permissions your PayPal account already has — it isn’t a separate export or a report you generate by hand, it’s your account looking things up, and in some cases creating or changing them, on your behalf.

Option 1: Connect PayPal to Claude directly

Claude supports remote MCP servers natively. The short version of the setup:

  • Open Claude’s connector or MCP settings.
  • Add a remote server pointing at PayPal’s MCP endpoint.
  • Sign in with your PayPal account when prompted — this is standard OAuth, so Claude never sees your PayPal password, and you can revoke access from PayPal’s own account settings at any time.

That’s enough if Claude is the only AI client you use with PayPal. The tradeoffs show up once you add a second tool or a second teammate: every additional AI client (ChatGPT, Cursor, an agent) needs its own copy of that same connection, its own OAuth grant, and its own place where the config can go stale.

Option 2: Connect it once, through a gateway

If you’re already juggling more than one MCP server or more than one AI client, wiring each pair directly gets old fast — that’s the connection sprawl we wrote about in what an MCP gateway is. The alternative is connecting PayPal (and everything else) to one gateway URL, then pointing every AI client at that single URL instead of reconfiguring each one.

With gate specifically, connecting PayPal looks like this: add gate’s gateway URL to Claude once, then pick PayPal from the PayPal server page in the directory and sign in with OAuth the same way you would directly. From then on, PayPal’s tools are available in every client connected to your gate URL — Claude, ChatGPT, or Cursor — without a second setup step. See the full list of servers set up this way on the MCP servers page.

Why the connection method matters for a payments account

Like any payments account, PayPal holds transaction history, customer contact details, and the ability to send money out through an invoice or a payout — not just look things up. A few things worth checking before or right after you connect:

  • Is it the official endpoint? Connect PayPal’s documented server (mcp.paypal.com), not a third-party mirror claiming to proxy it.
  • Read, or read and write? A connection that can look up an invoice can also create one — that is not the same risk, and it is worth knowing which tools are read-only before you hand an assistant a prompt like “follow up on all overdue invoices.”
  • Sandbox first, if you can. PayPal offers a developer sandbox with fake accounts and fake money; trying prompts there before pointing Claude at a live business account is a reasonable way to see what a tool call actually returns.
  • Who else on the team can reach it? If more than one person connects PayPal to their own AI client, a shared, revocable setup beats everyone holding their own grant — the same access-control question covered in MCP access control for teams.

You can run a quick, no-signup check on any server’s tool list with gate’s free MCP security scanner, which looks for prompt injection and hidden instructions in tool descriptions before you rely on a server day to day.

Troubleshooting the connection

A few things that commonly go wrong when connecting any remote MCP server, PayPal included:

  • OAuth loop or sign-in fails. Make sure you’re signed into the right PayPal account — and the right account, if you manage more than one business — before authorizing.
  • Claude can’t find a transaction you know exists. PayPal’s tools respect your account’s own permissions; a transaction on a business account won’t show up while Claude is connected to a personal one, or the other way around.
  • Tools disappear after a PayPal update. Remote servers can change their tool list without warning. If you’re connected through a gateway, that kind of change is exactly what drift detection is meant to catch — see how MCP rug pulls work for why a one-time review isn’t enough.
Where gate fits: gate connects PayPal once, behind a URL every AI client can share, with allow/ask/block rules you can set per tool — so a lookup can run automatically while creating an invoice or a payout waits for a human. Every server is scanned for prompt injection before it goes live, and every call is recorded in a plain-language log. See the full gateway at /mcp-gateway.

The bottom line

Connecting PayPal to Claude with MCP takes a few minutes either way: point Claude directly at PayPal’s server and sign in, or connect it once through a gateway if you want the same access available in every AI client you use, with rules on what it can do without asking first. Either way, a payments account is exactly the kind of connection worth a minute’s thought before you say yes — especially the part that can send money.