PayPal
by PayPal
Create and send invoices, capture order payments, issue refunds, manage subscriptions and resolve disputes from your AI assistant. 28 tools, OAuth sign-in, and a separate sandbox endpoint for testing.
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.
Connect PayPal via MCP
https://mcp.paypal.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect PayPal once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioPayPal Tools & Capabilities (28)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- This connector writes, and several writes are irreversible transfers of money.
pay_ordercaptures a payment,create_refundreturns one, andaccept_dispute_claimconcedes a dispute and triggers an automatic refund to the buyer. Treat it as an actioning integration, not a reporting one. - No scopes are advertised, so consent is all-or-nothing on the published evidence. Neither the RFC 9728 descriptor nor the RFC 8414 metadata carries a
scopes_supportedfield, on either the production or the sandbox host. There is no documented way to grant invoice reading without also granting dispute acceptance. - Sandbox and production are separate hosts and separate credentials. PayPal names sandbox-and-live mix-up as a recurring integration failure. On this connector the failure mode is a test invoice reaching a real customer, or a live refund issued during a rehearsal.
- Tool parameters and safety annotations were not readable. The endpoint returned HTTP 401 to an anonymous
initializeon 2026-08-18, so names came from the directory snapshot and meanings from PayPal's documentation. We read noreadOnlyHintordestructiveHintoff the wire and make no claim about them. No tool was called. - Rate limits are real but unpublished. PayPal states it does not publish exact rate limits because they vary by API, environment and circumstances, and that a
429may indicate anomalous traffic. Its guidance is to use webhooks over polling, cache OAuth tokens, and retry with exponential backoff. - The published tool list may be behind the server. PayPal's own reference documents 31 tools where Anthropic's snapshot names 28, and one name (
update_plan) appears in PayPal'sPROMPTS.mdbut not its README. Expect the live surface to differ from both. - Retried requests can duplicate an invoice. PayPal's invoicing troubleshooting page documents duplicate invoices from retried requests as a known issue and points to the
PayPal-Request-Idheader for idempotency. Whether the MCP server sets that header is not documented. - PayPal disclaims the accuracy of AI output. Its agent-toolkit repository states that AI-generated content may be inaccurate or incomplete and that users are responsible for independently verifying information before relying on it.
Frequently asked questions
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.
Sources
- PayPal MCP server quickstart guide, for the local/remote split, the sandbox and production endpoint table, transport options, setup steps and the
~/.mcp-authfix (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 tohttps://developer.paypal.com/tools/mcp-server/, which is itself a 301 to the canonical path above.developer.paypal.com/robots.txtpermits this path — its singleUser-agent: *block disallows only legacy and Braintree paths — and carries noContent-Signalline. · retrieved 2026-08-18 - PayPal Agent Toolkit repository, for the 31-tool reference, per-tool parameters, published example prompts, account prerequisites and the AI-output disclaimer (
README.mdandPROMPTS.mdatmain, retrieved 2026-08-18). Reached from a real href on PayPal's quickstart page. · retrieved 2026-08-18 - PayPal Disputes API guide, for what accepting a claim does, the lifecycle stages, the
allowed_response_optionsvalues, the appeal gate and the stage/status action table (HTTP 200, retrieved 2026-08-18) · retrieved 2026-08-18 - PayPal Resolution Center documentation, for the merchant-facing description of accepting a claim (HTTP 200, retrieved 2026-08-18) · retrieved 2026-08-18
- PayPal invoicing lifecycle, for draft-versus-sent status (HTTP 200, retrieved 2026-08-18) · retrieved 2026-08-18
- PayPal invoicing troubleshooting, for the sandbox/live mix-up, duplicate invoices from retries and the 429 backoff guidance (HTTP 200, retrieved 2026-08-18) · retrieved 2026-08-18
- PayPal invoicing core concepts, for the REST scope vocabulary (HTTP 200, retrieved 2026-08-18) · retrieved 2026-08-18
- PayPal rate limiting with REST APIs, for the unpublished-limits statement (HTTP 200, retrieved 2026-08-18) · retrieved 2026-08-18
- PayPal Payouts overview, for the existence of a payouts product with no corresponding tool (indexed 2026-08-18) · retrieved 2026-08-18
- PayPal documentation index (HTTP 200, retrieved 2026-08-18). Section indexes at
/developer-resources/llms.txt,/revenue/llms.txtand/other/llms.txtsupplied every sub-URL cited above; none was guessed. · retrieved 2026-08-18 - Live auth-posture check against
https://mcp.paypal.com/mcp—initializereturned HTTP 401 withWWW-Authenticate: Bearer realm="OAuth", resource_metadata="https://mcp.paypal.com/.well-known/oauth-protected-resource", error="invalid_token"(2026-08-18).GET /mcpreturned HTTP 401,GET /sse401,GET /http404 the same day. No tool was called. · retrieved 2026-08-18 - RFC 9728 protected-resource descriptor (HTTP 200, 2026-08-18). Names
authorization_servers: ["https://mcp.paypal.com"]andbearer_methods_supported: ["header"]; · retrieved 2026-08-18 - RFC 8414 authorization server metadata (HTTP 200, 2026-08-18). Names a
registration_endpoint, theauthorization_codeandrefresh_tokengrants and PKCES256; · retrieved 2026-08-18 - Sandbox corroboration —
https://mcp.sandbox.paypal.com/mcpreturned HTTP 401 to an anonymousinitialize, and its two.well-knowndocuments mirror production including the absentscopes_supported(2026-08-18). · retrieved 2026-08-18 - Anthropic Connectors Directory entry, for tool names, tier, endpoint, the "Read and write" permission label and the published example prompts (snapshot dated 2026-08-16) · retrieved 2026-08-16
- PayPal privacy notice — · Support — <developer@paypal.com>
Server Info
- Category
- Finance
- Developer
- PayPal
- Tools
- 28
- Domain
- mcp.paypal.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Finance
Related Resources
Ready to connect PayPal?
Connect PayPal once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.