A Model Context Protocol (MCP) server for PayPal API integration
Most payments and commerce work still happens through a UI a human drives. PayPal MCP Defunct MCP server moves it into the conversation instead. A Model Context Protocol (MCP) server for PayPal API integration.
A Model Context Protocol (MCP) server that provides integration with PayPal's APIs. This server enables seamless interaction with PayPal's payment processing, invoicing, subscription management, and business operations through a standardized interface.
The server publishes 11 tools. What each one is for:
create_payment_token — Create a payment token for future usecreate_order — Create a new order in PayPalcapture_order — Capture payment for an authorized ordercreate_payment — Create a direct paymentcreate_subscription — Create a subscription for recurring billingcreate_product — Create a new product in the catalogcreate_invoice — Generate a new invoicecreate_payout — Process a batch payoutget_userinfo — Retrieve user informationcreate_web_profile — Create a web experience profileget_web_profiles — Get list of web experience profilesConfiguration is passed through the environment: PAYPAL_CLIENT_ID, PAYPAL_CLIENT_SECRET, PAYPAL_ENVIRONMENT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Plenty of payments and commerce servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. PayPal MCP Defunct's toolset — create_payment_token, create_order, capture_order and 8 more — is a fair guide to whether it matches your workflow. It is maintained by arbuthnot-eth; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| create_payment_token | Create a payment token for future use |
| create_order | Create a new order in PayPal |
| capture_order | Capture payment for an authorized order |
| create_payment | Create a direct payment |
| create_subscription | Create a subscription for recurring billing |
| create_product | Create a new product in the catalog |
| create_invoice | Generate a new invoice |
| create_payout | Process a batch payout |
| get_userinfo | Retrieve user information |
| create_web_profile | Create a web experience profile |
| get_web_profiles | Get list of web experience profiles |
{
"mcpServers": {
"paypal": {
"command": "node",
"args": ["path/to/paypal-mcp/build/index.js"],
"env": {
"PAYPAL_CLIENT_ID": "your_client_id",
"PAYPAL_CLIENT_SECRET": "your_client_secret",
"PAYPAL_ENVIRONMENT": "sandbox"
},
"disabled": false,
"autoApprove": []
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PAYPAL_CLIENT_ID | Configuration value read at startup. | Optional |
| PAYPAL_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| PAYPAL_ENVIRONMENT | Configuration value read at startup. | Optional |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.