Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Create and send invoices, capture order payments, issue refunds, manage subscriptions and resolve disputes.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The PayPal MCP server connects a PayPal Business account to Claude, ChatGPT and any MCP-compatible agent. It exposes 28 tools for creating and sending invoices, capturing order payments, issuing refunds, managing subscription plans, tracking shipments and resolving disputes. Sign-in is OAuth. This connector writes, and several of the things it writes move money.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
pay_order captures a payment, create_refund returns one, and accept_dispute_claim concedes a dispute and triggers an automatic refund to the buyer. Treat it as an actioning integration, not a reporting one.scopes_supported field, on either the production or the sandbox host. There is no documented way to grant invoice reading without also granting dispute acceptance.initialize on 2026-08-18, so names came from the directory snapshot and meanings from PayPal's documentation. We read no readOnlyHint or destructiveHint off the wire and make no claim about them. No tool was called.429 may indicate anomalous traffic. Its guidance is to use webhooks over polling, cache OAuth tokens, and retry with exponential backoff.update_plan) appears in PayPal's PROMPTS.md but not its README. Expect the live surface to differ from both.PayPal-Request-Id header for idempotency. Whether the MCP server sets that header is not documented.Yes, when you point it at the production endpoint. PayPal documents mcp.paypal.com as the production endpoint and mcp.sandbox.paypal.com as the sandbox one. The tool set includes pay_order, which PayPal describes as capturing payment for an authorised order, and create_refund, which processes a refund for a captured payment. Sandbox transactions use test accounts and no real funds.
No. Creating and sending are separate tools. PayPal's invoicing lifecycle documentation states an invoice starts in draft status, is created but not sent, and is invisible to the payer. The separate send_invoice tool emails it to the recipient, and send_invoice_reminder chases an existing one. Nothing reaches your customer until the send step runs.
It concedes the dispute. PayPal's Disputes API guide states that accepting a claim accepts liability, closes the dispute in the buyer's favour, and that PayPal automatically refunds the buyer. PayPal's Resolution Center documentation describes the same action as closing the case in the buyer's favour and issuing a refund. Money leaves your account as a result.
A PayPal Business account for production and a PayPal Developer account for sandbox, per the prerequisites in PayPal's agent-toolkit repository. Sandbox business and personal test accounts are created automatically when you sign up for the developer account, and you retrieve their credentials from the Developer Dashboard under Sandbox Accounts.
PayPal ships both. Its quickstart documents a local server run with npx @paypal/mcp using a PayPal access token, and a remotely hosted server reached over OAuth. Anthropic's directory lists the hosted one at mcp.paypal.com. PayPal states the complete catalog of tools is available in both the local and remote server.
PayPal publishes no exact numbers. Its rate-limiting guide states PayPal does not publish exact rate limits because they vary by API, environment and circumstances, and that exceeding them returns HTTP 429. Its invoicing troubleshooting page tells callers to use exponential backoff with jitter on any 429 or 5xx response.
No tool for either appears in any published list. PayPal Payouts is a documented product for sending money to many recipients, but no payout, balance, transfer or withdrawal tool appears in Anthropic's 28-name snapshot or in PayPal's own 31-tool reference. The connector acts on invoices, orders, refunds, subscriptions, products, shipments and disputes.
~/.mcp-auth fix (HTTP 200, retrieved 2026-08-18; canonical Markdown at , "Last updated: June 30, 2026"). The URL Anthropic's directory publishes, https://mcp.paypal.com/, returns HTTP 302 to https://developer.paypal.com/tools/mcp-server/, which is itself a 301 to the canonical path above. developer.paypal.com/robots.txt permits this path — its single User-agent: * block disallows only legacy and Braintree paths — and carries no Content-Signal line. · retrieved 2026-08-18README.md and PROMPTS.md at main, retrieved 2026-08-18). Reached from a real href on PayPal's quickstart page. · retrieved 2026-08-18allowed_response_options values, the appeal gate and the stage/status action table (HTTP 200, retrieved 2026-08-18) · retrieved 2026-08-18/developer-resources/llms.txt, /revenue/llms.txt and /other/llms.txt supplied every sub-URL cited above; none was guessed. · retrieved 2026-08-18https://mcp.paypal.com/mcp — initialize returned HTTP 401 with WWW-Authenticate: Bearer realm="OAuth", resource_metadata="https://mcp.paypal.com/.well-known/oauth-protected-resource", error="invalid_token" (2026-08-18). GET /mcp returned HTTP 401, GET /sse 401, GET /http 404 the same day. No tool was called. · retrieved 2026-08-18authorization_servers: ["https://mcp.paypal.com"] and bearer_methods_supported: ["header"]; · retrieved 2026-08-18registration_endpoint, the authorization_code and refresh_token grants and PKCE S256; · retrieved 2026-08-18https://mcp.sandbox.paypal.com/mcp returned HTTP 401 to an anonymous initialize, and its two .well-known documents mirror production including the absent scopes_supported (2026-08-18). · retrieved 2026-08-18Connect PayPal once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.