Provider REST API

19 actions

Connect Claude to Square

Read payments, orders, customers, the catalog, inventory and invoices, and issue refunds. Toolspoke puts 19 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Provider REST API
Authentication: Access token
Actions exposed: 19
What a call bills: Nothing
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Square
Open the marketplace in your workspace, add Square to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with access token. 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. Square 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 Square asks for

Access token. 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.

Access tokenRequired: Square Developer Console (developer.squareup.com/apps) → your application → Credentials → Production → Production access token → Show. The token acts as the seller account that owns the application, with every permission, so keep it to an account this connection should reach.; EAAA…
API addressOptional: Leave blank for production. Use https://connect.squareupsandbox.com with a Sandbox access token.; https://connect.squareup.com

What Claude can do in Square

19 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: 16Reads
Writes: 1Writes
Destructive: 2Destructive

Reads

Fetches data and changes nothing.

list_locations
List the seller's locations with their ids, addresses, currencies and status. Takes no arguments and is the connection test; the location ids it returns are what payments, orders and invoices filter by.
list_payments
List payments taken, newest first by default, inside an optional time window and location. Amounts are in the currency's smallest unit (cents).
get_payment
Retrieve one payment by id, with its amount, card details, status and the order it paid for.
list_refunds
List refunds, newest first by default, inside an optional time window, location or status.
get_refund
Retrieve one refund by id.
search_orders
Search orders at one or more locations, optionally by state and creation window. Returns orders with their line items, totals and fulfillments.
get_order
Retrieve one order by id, with its line items, taxes, discounts, tenders and fulfillments.
list_customers
List the seller's customer directory.
search_customers
Find customers by email address or phone number. email does a fuzzy match; email_exact matches the whole address.
get_customer
Retrieve one customer profile by id.
list_catalog
List catalog objects - items, variations, categories, taxes, discounts - optionally only some types.
search_catalog_items
Search catalog items by text, category or location.
get_catalog_object
Retrieve one catalog object by id, optionally with the objects it references (variations, category, taxes).
get_inventory_counts
Read current stock counts for catalog item variations, optionally at some locations only.
list_invoices
List the invoices at one location, with their status, recipient and payment requests.
get_invoice
Retrieve one invoice by id.

Writes

Creates or updates something on the other side.

create_customer
Add a customer profile to the seller's directory. A write rather than destructive: it charges nothing and messages nobody. Square needs at least one of given_name, family_name, company_name, email_address or phone_number.

Destructive

Deletes or permanently alters something. Worth granting on purpose.

cancel_payment
Cancel (void) a payment that was authorized but not yet completed, releasing the hold on the buyer's card. Destructive because the sale is lost and the authorization cannot be restored.
refund_payment
Refund all or part of a completed payment to the buyer's original payment method. Destructive because it moves money back to the buyer and cannot be undone. amount is in the smallest currency unit (cents). idempotency_key must be unique per refund: re-sending the same key returns the first refund instead of making a second.

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 19 actions above are the whole of it. A call to any other name is refused before it reaches Square 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 Square 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 Square: 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 Square. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Square's own rate limits. A call that Square refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Square?

19 named actions: 16 that only read, 1 that write and 2 that delete or permanently alter something. They include list_locations, list_payments and get_payment. 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 Square connector need?

Access token. The connector asks for access token, 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 Square connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 19 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 Square connector not do?

The 19 actions above are the whole of it. A call to any other name is refused before it reaches Square 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 Square 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 Square. An agent has to ask. Toolspoke does not retry, queue or back off around Square's own rate limits. A call that Square 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 Square'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 Square?

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