Provider REST API

16 actions

Connect Claude to PayPal

Read transactions, balances and disputes, manage invoices and orders, and issue refunds. Toolspoke puts 16 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: REST app client credentials
Actions exposed: 16
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install PayPal
Open the marketplace in your workspace, add PayPal to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with rest app client credentials. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. PayPal shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What PayPal asks for

REST app client credentials. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

Client IDRequired: PayPal Developer Dashboard (developer.paypal.com) → Apps & Credentials → switch to Live (or Sandbox) → your REST app, or Create App. The Client ID is shown on the app's page. Turn on Transaction Search under the app's features if list_transactions or get_balances should work.; AbCdEf…
Secret keyRequired: On the same app page, under Secret key - click Show. PayPal exchanges it for a short-lived access token; the secret itself never reaches an API endpoint.; Paste the secret
API addressOptional: Leave blank for live. Use https://api-m.sandbox.paypal.com with a Sandbox app's credentials.; https://api-m.paypal.com

What Claude can do in PayPal

16 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 10Reads
Writes: 2Writes
Destructive: 4Destructive

Reads

Fetches data and changes nothing.

list_transactions
Search the account's transactions between two dates, at most 31 days apart. Results can lag real time by up to three hours. fields controls how much each row carries: transaction_info returns only the transaction itself; all adds payer, cart and shipping detail. Requires Transaction Search to be enabled on the REST app.
get_balances
List the account's balances in every currency it holds, optionally as of a past date-time. Requires Transaction Search on the REST app.
list_invoices
List the account's invoices, newest first, with status, recipient and amount. Takes no required arguments, which is why it is the connection test.
search_invoices
Search invoices by recipient email, invoice number or status.
get_invoice
Retrieve one invoice by id, with its items, recipients, payments and refunds.
get_order
Retrieve one checkout order by id, with its status, payer and any captures.
get_capture
Retrieve one captured payment by id, with its amount, fees and status.
get_refund
Retrieve one refund by id, with its amount and status.
list_disputes
List disputes and claims opened against this account, optionally by state.
get_dispute
Retrieve one dispute by id, with the disputed transaction, messages and evidence.

Writes

Creates or updates something on the other side.

create_draft_invoice
Create a draft invoice to one recipient. A write rather than destructive: a draft is not sent and nobody sees it until send_invoice. Items are [{name, quantity, unit_amount: {currency_code, value}}], with quantity and value as decimal strings.
create_order
Create a checkout order for one amount. A write rather than destructive: no money moves until the payer approves it and capture_order is called. Returns the order id and the approve link to give the payer.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

send_invoice
Send a draft invoice to its recipient. Destructive because it emails someone outside the workspace a request for money, and a sent invoice cannot be unsent - only cancelled, which notifies them again.
cancel_invoice
Cancel a sent invoice so it can no longer be paid. Destructive because it cannot be reversed and, by default, notifies the recipient.
capture_order
Capture payment for an order the payer has approved. Destructive because it moves the payer's money into this account; undoing it means refund_capture.
refund_capture
Refund a captured payment, in full or in part. Destructive because it sends money back to the payer and cannot be undone. Leave amount out to refund the full capture.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 16 actions above are the whole of it. A call to any other name is refused before it reaches PayPal rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It reaches no further than your credential: Toolspoke holds no access to PayPal of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from PayPal: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in PayPal. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around PayPal's own rate limits. A call that PayPal refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in PayPal?

16 named actions: 10 that only read, 2 that write and 4 that delete or permanently alter something. They include list_transactions, get_balances and list_invoices. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the PayPal connector need?

REST app client credentials. The connector asks for client id and secret key, and optionally api address. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the PayPal connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 16 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the PayPal connector not do?

The 16 actions above are the whole of it. A call to any other name is refused before it reaches PayPal rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Toolspoke holds no access to PayPal of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in PayPal. An agent has to ask. Toolspoke does not retry, queue or back off around PayPal's own rate limits. A call that PayPal refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches PayPal's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls PayPal?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and what the call cost in sandbox time and model tokens. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More payments connectors

Browse all of them