Connect Square to Claude Code

Read payments, orders, customers, the catalog, inventory and invoices, and issue refunds. Add Toolspoke to Claude Code once and it can use 19 Square actions. Your Square credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Square and connect it

    Add Square to a project in your Toolspoke workspace.

    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 token
    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.
  3. Choose what Claude Code may do

    All 19 actions start on. Switch off any of the 3 actions that change something in Square, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Square actions that only read, so they are safe to try first.

  • List the seller's locations with their ids, addresses, currencies and status
  • List payments taken, newest first by default, inside an optional time window and location
  • Retrieve one payment by id, with its amount, card details, status and the order it paid for
  • List refunds, newest first by default, inside an optional time window, location or status

What Claude Code can do in Square

16 actions read, one writes and 2 delete or permanently change something.

Reads

  • 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

  • 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.

Deletes or permanently changes

  • 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.

Square in Claude Code: questions

Does Claude Code see my Square credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Square?

Yes. Each of the 19 actions can be switched off for a project. Turn off the 3 that change something and Claude Code can only read.

Will 19 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Square action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Square call does not run in a sandbox, so it bills nothing.

Try Square in Claude Code

Free to start, and tool calls cost nothing on any plan.