PayPal MCP Server – Payments and Merchant Tools

PayPal's official MCP server lets AI agents interact with PayPal APIs through function calling. Use it to support merchant workflows such as creating and sending invoices, creating orders, processing refunds, managing disputes, tracking shipments, managing catalog products and subscriptions, and reviewing transactions.

#payments#invoicing#merchant-tools

Overview

PayPal's official MCP server connects compatible AI clients to PayPal merchant
capabilities. It lets agents use natural-language requests to perform supported
PayPal business tasks through structured MCP tools, reducing the need to switch
manually between an AI assistant, PayPal API documentation, and merchant tools.

What the MCP server enables

The official server exposes PayPal tools across several merchant workflows.
Depending on the configured environment, account permissions, and selected
tools, an AI agent can:

Create, list, retrieve, send, remind, cancel, and generate QR codes for
invoices.
Create, retrieve, and pay orders.
Create and retrieve refunds.
List disputes, retrieve dispute details, and accept dispute claims.
Create and retrieve shipment tracking records.
Create, list, inspect, and update catalog products.
Create, update, list, inspect, and cancel subscription plans and subscriptions.
List transactions for reporting and insight workflows.

When to use it

Use PayPal MCP when an AI agent is helping a merchant complete PayPal business
tasks. Practical examples include creating a sandbox invoice for testing,
sending a production invoice after approval, checking recent transactions,
looking up an order, issuing a refund, reviewing open disputes, creating a
product catalog entry, or setting up a subscription plan from a conversational
workflow.

Connection and authentication

PayPal provides two setup options. The local MCP server runs with
npx -y @paypal/mcp --tools=all and requires Node.js 18 or later. Configure
PAYPAL_ACCESS_TOKEN and set PAYPAL_ENVIRONMENT to SANDBOX for testing or
PRODUCTION for live usage. The access token can also be passed with the
documented --access-token argument.

PayPal also provides hosted remote MCP endpoints. Sandbox uses
https://mcp.sandbox.paypal.com; production uses https://mcp.paypal.com.
Remote Streamable HTTP endpoints end in /http, while SSE endpoints end in
/sse. Remote setup can use PayPal login and consent through the MCP client,
or bearer authorization when configured through an MCP remote bridge.

Key considerations

PayPal MCP tools can create invoices, take payment-related actions, issue
refunds, update products, cancel subscriptions, and affect real merchant
accounts. Use the sandbox endpoint and PAYPAL_ENVIRONMENT=SANDBOX while
testing. Require human approval before production writes, refunds, cancellations,
dispute actions, or invoice sending. Store access tokens, client secrets, and
generated bearer values in a secret manager. PayPal access tokens expire, so
clients should be prepared to refresh or reauthorize as needed. Clear local MCP
auth files only as a troubleshooting step when remote authorization becomes
stuck.

Frequently Asked Questions

When should an AI agent use the PayPal MCP server?

Use it when a merchant workflow needs PayPal actions or context, such as creating or sending invoices, creating orders, issuing refunds, reviewing disputes, adding shipment tracking, managing products or subscriptions, or listing recent transactions.

What does the PayPal MCP server add to an AI agent's capabilities?

It gives the agent structured access to supported PayPal API workflows through MCP tools, allowing it to perform merchant tasks through function calls instead of relying only on static model knowledge or manually written API requests.

What can an AI agent access or manage through PayPal MCP?

Depending on credentials and selected tools, the agent can work with invoices, orders, refunds, disputes, shipment tracking, catalog products, subscription plans, subscriptions, and transaction reporting. Production actions affect real PayPal merchant resources.

How is authentication configured for the PayPal MCP server?

The local server uses PAYPAL_ACCESS_TOKEN and PAYPAL_ENVIRONMENT, with SANDBOX for testing or PRODUCTION for live usage. Remote endpoints can use PayPal login and consent through the MCP client or bearer authorization via a remote MCP bridge. Keep all tokens and client secrets secure.

Which transport should be used for the PayPal MCP server?

Use local stdio with @paypal/mcp when running the server on the developer's machine. Use Streamable HTTP for modern remote clients, choosing the sandbox endpoint for testing and the production endpoint for live workflows. Use SSE only when the MCP client or bridge specifically requires SSE.