Paypal MCP server

Read from the package source without running it. The installed server may list more.

• accept_dispute_claim

  Accept liability for a dispute claim via POST /v1/customer/disputes/{id}/accept-claim. The disputed amount is refunded to the buyer. Terminal action.

• authorize_orderwrite action

  Authorize payment for an approved order via POST /v2/checkout/orders/{id}/authorize. Use after the buyer approves an order with intent=AUTHORIZE. Returns the created authorization (capture later with capture_authorization).

• cancel_subscriptionwrite action

  Cancel an active subscription via POST /v1/billing/subscriptions/{id}/cancel. Pass a reason string. Returns 204 No Content on success.

• capture_authorization

  Capture a previously authorized payment via POST /v2/payments/authorizations/{id}/capture. Pass an amount object for partial captures, or omit to capture the full authorized amount. Set final_capture=true on the last partial capture.

• capture_orderwrite action

  Capture payment for an approved order via POST /v2/checkout/orders/{id}/capture. Use after the buyer approves an order with intent=CAPTURE. Returns the captured payment details.

• create_batch_payoutwrite action

  Create a batch payout via POST /v1/payments/payouts. sender_batch_header carries metadata; items is an array of payout_item objects each with recipient_type, amount { currency, value }, receiver, and note. Async — poll get_payout to track status.

• create_orderwrite action

  Create a PayPal Order via POST /v2/checkout/orders. Pass intent ('CAPTURE' or 'AUTHORIZE') and purchase_units (each with an amount object). Returns the order with id, status, and HATEOAS links (including the approve URL for the buyer).

• create_subscriptionwrite action

  Create a billing subscription via POST /v1/billing/subscriptions. plan_id is the id of a previously created billing plan. Returns the subscription with status (APPROVAL_PENDING) and HATEOAS approve link for the buyer.

• get_dispute

  Fetch a dispute by id via GET /v1/customer/disputes/{id}. Returns full dispute details including reason, status, life_cycle_stage, disputed_transactions, and messages.

• get_orderwrite action

  Fetch a PayPal Order by id via GET /v2/checkout/orders/{id}. Returns the full order including status, purchase_units, and payments collection.

• get_payment_details

  Fetch a payment object by id via GET /v2/payments/{type}/{id}. type is one of 'authorizations', 'captures', or 'refunds'. Returns the full payment object with status and links.

• get_payout

  Fetch a payout batch by id via GET /v1/payments/payouts/{batch_id}. Returns batch_header (status, time_created, etc.) and items array with per-item status.

• get_payout_item

  Fetch a single payout item by id via GET /v1/payments/payouts-item/{item_id}. Use to inspect the status of one recipient inside a batch (UNCLAIMED, SUCCESS, FAILED, etc).

• get_subscription

  Fetch a subscription by id via GET /v1/billing/subscriptions/{id}. Returns id, status, plan_id, subscriber, billing_info, and links.

• list_disputes

  List disputes via GET /v1/customer/disputes. Filter by disputed_transaction_id, dispute_state, update_time_before / update_time_after. Pagination via page_size and next_page_token.

• list_webhooks

  List configured webhooks for the app via GET /v1/notifications/webhooks. Returns each webhook with id, url, and event_types.

• refund_capturewrite action

  Refund a captured payment via POST /v2/payments/captures/{id}/refund. Pass an amount object for partial refunds, or omit for a full refund. Idempotent via PayPal-Request-Id.

• verify_webhook_signature

  Verify a webhook event signature via POST /v1/notifications/verify-webhook-signature. Pass the headers and body received on your webhook endpoint. Returns verification_status SUCCESS or FAILURE.

• void_authorization

  Void (release) an unsettled authorization via POST /v2/payments/authorizations/{id}/void. Use when funds were authorized but will not be captured. Returns 204 No Content on success.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitystatic API keys via environment variables6/15
• Maintenancelast push 29 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

82/100

higher than 75% of 2,174 E-commerce servers

Tools

19

the typical E-commerce server has 6

Tools that change things

42%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

271

more than 95% of 1,047 E-commerce servers

Downloads a week

24

more than 10% of 411 E-commerce servers with a package

Paypal: common questions

Is Paypal MCP server safe?

Mostly: it is graded B (82/100). Read the Paypal safety report

How do I install Paypal?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Paypal need an API key?

Yes. The registry entry asks for PAYPAL_CLIENT_SECRET.

Is Paypal maintained?

The last commit was 67 days ago (2026-08-29). The latest release is v0.1.2.

What can I use instead of Paypal?

Servers from other publishers that do the same job: Świadectwo Energetyczne 24 MCP server, Dodo Payments MCP server and Stripe MCP server.

How does Paypal compare with other E-commerce MCP servers?

safety score 82/100 (higher than 75% of 2,174 E-commerce servers); tools 19 (the typical E-commerce server has 6); tools that change things 42% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.