Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Three tools dispatching to 283 Square API methods — take a payment, issue a refund, publish an invoice that emails the…
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Square MCP server connects a Square seller account to Claude, ChatGPT and any MCP-compatible agent. It publishes three tools, but one of them dispatches to 283 methods across 38 Square services — payments, refunds, invoices, orders, catalog, payroll and more. Sign-in is OAuth with 49 named Square permissions.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
9aeafc9, not from a handshake. The hosted server could in principle register tools the open-source repository does not — we could not rule that out.PAYMENTS_WRITE grants both.DISALLOW_WRITES exists only for the local server, and its underlying isWrite flags miss PayOrder, BatchChangeInventory, RemoveGroupFromCustomer, AddGroupToCustomer, ChangeBillingAnchorDate, TestWebhookSubscription and RevokeToken.idempotency_key as the protection against a duplicate charge, and warns that a repeated CreatePayment without one charges the customer twice. Nothing in the MCP layer supplies or enforces that key — an agent that retries a failed call is the exact scenario the key exists to prevent.square-mcp-server on npm was last published at version 0.1.2 in April 2025, while the GitHub repository's head commit is dated April 2026. A local install from npm is not the code we read.Yes to both. Square's open-source server routes CreatePayment and RefundPayment through the same make_api_request tool, and Square's own commit history shows RefundPayment being corrected to a write operation in April 2026. The three-tool listing hides this because the money-moving verbs are arguments, not tool names.
Because it is a dispatcher, not a curated subset. Square's published source registers exactly three tools, and one of them, make_api_request, forwards a service and method pair to any of 283 REST methods across 38 Square services. The tool count measures the interface, not the reach.
Forty-nine named Square permissions, published by the server's own RFC 9728 descriptor on 2026-08-22. They are per-domain and genuinely narrowing, covering payments, orders, invoices, customers, inventory, gift cards, disputes and payouts separately. You can grant reading payments without granting writing customers.
No. Square's permissions reference assigns CreatePayment and RefundPayment the same PAYMENTS_WRITE scope, so any grant that lets an agent charge a card also lets it send money back. The scope boundary falls between business domains, never between a routine write and an irreversible one.
Yes, through invoices. Square documents that publishing an invoice makes Square follow up per the invoice configuration, which can mean emailing the customer or charging their card on file. The connector's own directory listing showcases invoice creation, so this outbound path is the advertised use case rather than an edge case.
Only the local server, and the guard is incomplete. A DISALLOW_WRITES environment variable blocks methods flagged as writes, but Square's source flags PayOrder, BatchChangeInventory and RemoveGroupFromCustomer as non-writes despite each mutating state. The hosted remote server exposes no read-only switch at all.
Not the hosted one. Square's documentation states that remote instances only access production resources, and that a local instance is the way to test against a seller's sandbox. Square also recommends testing prompts against a sandbox before production, which the remote server cannot do.
Both work, and the two sources disagree. Square's documentation only ever gives the SSE path, while Anthropic's directory and Square's own Claude Code install command give the streamable HTTP path. Both returned an authentication challenge on 2026-08-22, so both are live.
square/square-mcp-server at commit 9aeafc9cd2d9ff70b626123a12849a741ea3a162 (read 2026-08-22). Apache-2.0. All method counts, HTTP verbs and isWrite flags on this page were derived from the 38 files under services/. · retrieved 2026-08-22developer.squareup.com/robots.txt names GPTBot, ClaudeBot and PerplexityBot in explicit allow groups; the MCP documentation page is not in any disallow list. · retrieved 2026-08-22https://mcp.squareup.com/mcp and https://mcp.squareup.com/sse each returned HTTP 401 with WWW-Authenticate: Bearer; RFC 9728 metadata at https://mcp.squareup.com/.well-known/oauth-protected-resource and authorization server metadata at https://mcp.squareup.com/.well-known/oauth-authorization-server (2026-08-22) · retrieved 2026-08-22square-mcp-server on npm, version 0.1.2 published 2025-04-25, read from the registry metadata at (retrieved 2026-08-22). The human-facing page at npmjs.com/package/square-mcp-server returns 403 to a non-browser client. · retrieved 2025-04-25Connect Square once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.