Claude Square connectorWhat Claude can do in your Square account.
The Claude Square connector exposes 3 tools. 2 read how the Square API is organised, 1 runs real requests against your account, and 0 stay undocumented. Below: what Claude can reach, what can change your data, and why Square asks you to test in a sandbox first.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for a Square seller
Instead of opening the Square dashboard, filtering a report and exporting it, you ask Claude in plain words. Square describes its connector as a door to its whole API (customers, orders, items and more), so the same chat can pull numbers and, when you ask, act on the account. Three tools do all of that: two to find the way, one to send the request.
Find the right corner of Square. You ask for last week's refunds and Claude starts with get_service_info to see which methods a Square service offers, so it is not guessing where refunds live.
Build the request properly. Before it sends anything, get_type_info tells Claude which parameters that method expects.
Get the answer, or make the change. make_api_request is the one that actually talks to your account. It can fetch the customer list you asked for, and it can just as well create or edit something, because Square does not restrict it to reading.
What it will not do: nothing runs on its own. No tool wakes up when a payment lands or stock runs low; Claude acts only while it answers you. If you want Square data pushed somewhere every time a sale happens, that is a job for a scenario tool, and the Square Make integration page covers that side. The two do different jobs, so picking one depends on whether you want answers on demand or a process that runs in the background.
The vocabulary in one minute
Five words you will meet while setting this up.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Tool
- One named action the connector opens to Claude. Claude picks the ones it needs by itself; the directory lists them by name.
- Authorization
- The sign-in screen of Square itself, where you hand Claude the access it will use. Given once per person, and you can take it back.
- Approval
- The confirmation Claude waits for before it finishes something that changes your account, shown right in the conversation.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Square.
Connect Square to Claude in three steps
- 01
Find Square in Claude
In Claude's settings, open Customize, then Connectors, and look for Square in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row and sign in to Square in the window Square opens itself. If the link breaks one day, use Disconnect, then plug it back in from the same row.
- 03
Read the authorization screen
Read Square's screen before you accept. It belongs to Square, not Claude, and it decides what the access covers. You can also withdraw that access later from your Square account.
The 3 tools, grouped by what they do
Square gives Claude 3 tools: 2 that read your account, 1 that change something in it.
Two tools help Claude understand Square's API, one does the work. Names stay in English, as Claude shows them.
- 2 read
- 1 write
What Claude reads (2)
2 toolsTwo tools that look at how Square is organised without touching your data.
get_service_info
Lists the methods a given Square service offers, so Claude knows what it can ask for before asking. You get a map of options, not account data.
get_type_info
Returns what a specific method needs as input, field by field. Claude uses it to prepare a request that Square will accept on the first try.
What Claude can change (1)
1 toolOne general-purpose tool that sends requests to your account. No source describes a confirmation specific to it: the general rule below applies.
make_api_request
Approval: see the ruleSends the actual request to Square and brings back the result. Depending on the method, that can mean reading customers and orders, or creating and editing records in your account.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, at the moment it matters.
On Team and Enterprise, workspace owners decide whether a member can let some actions through without being asked every time. They can also cap what a connector may do for the whole organisation, keeping reading open and closing writing, for example. That setting applies to everyone and nobody gets around it from their own account. And Claude works with your rights, nothing more: what you cannot reach in Square stays out of its reach too.
Which plans it works on
None of the 819 sheets in the official directory shows availability by plan. The answer, connector by connector, is not published anywhere: it is a real gap in the catalogue.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before members can connect. Square's developer page describes something narrower, set side by side in the limits section. For the current state, check the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a payment clears, an order is placed or an item sells out.
The tool list is an observed floor, not a promise, and here it hides a lot: one generic tool opens most of the Square API. The partner badge in the directory is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as described. Everything below comes from Square's own documentation, since neither Claude's help centre nor Anthropic's docs have a page on this connector. For a more classic tool list, compare with the Claude airtable connector.
Which plans can use the Square connector?
- Claude help centre, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise an Owner must switch each one on first.
- Square developer documentation ↗undatedOut of dateSquare only gives setup paths for Claude Team, Enterprise and Max, through an Integrations screen that is no longer the connectors screen.
What this page followsSquare's page is undated and describes an older screen, so Anthropic's rule is the more recent of the two. Neither one settles it for your account: check the connector's sheet in the directory while signed in.
Need help connecting Square to Claude?
A person reads every message.
