Connect Square to Claude Code

Have Claude update your catalog and manage orders in Square. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Square to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Square, you add a Square MCP server: a small hosted service that exposes Square's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Square account. No API keys pasted into config files.

claude mcp add --transport http square https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Square once connected?

Full read-write Square access lets Claude update catalog items and prices, adjust inventory counts, create or modify orders, manage customer records, and issue refunds once you approve. The catalog cleanup and order work that used to mean clicking through the dashboard happens where your Square data already lives.

Update an item's price or description in the Square catalog
Adjust inventory counts for a location after a stock check
Create or modify an order and apply a discount
Add or update a customer record in the directory
Issue a refund against a payment once you approve it
Create a catalog item with variations and assign it to a category

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Square access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Square API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Square changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Square connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Square connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Square account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Square's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Square?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Square account it signs in with. Revoking access is one click in Square.

More on the Square connector

Square connector for claude.ai Stripe + Claude Code Shopify + Claude Code QuickBooks Online + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us