Square MCP server
Square's official MCP server gives agents access to the full Square API: payments, catalog, orders, customers, bookings, inventory, and more.
The Square MCP Server is the official server from Square (Block) that exposes Square's entire Connect API surface to an AI agent. Rather than shipping one MCP tool per endpoint, it uses a compact discovery pattern: the agent calls get_service_info to see which methods a service offers, get_type_info to learn the exact parameters a call needs, and then make_api_request to execute it. Through that handful of meta-tools the agent reaches 40+ Square services, including payments, checkout and payment links, catalog and inventory, orders, customers, bookings, loyalty, gift cards, refunds, disputes, invoices, subscriptions, and team/workforce management, all without the server needing a separate tool registered for every operation. A DISALLOW_WRITES flag restricts it to read-only calls, which is the safe default when pointing an agent at a live merchant account.
Square recommends the hosted remote server at https://mcp.squareup.com/sse, which supports OAuth login with granular, scoped permissions. For local use you run it over stdio with npx square-mcp-server start, authenticating with a Square access token in the ACCESS_TOKEN environment variable and choosing the environment with SANDBOX=true or PRODUCTION=true. Because it can move money, scoping the token (or OAuth grant) to only what a given agent needs is the recommended pattern.
Quick install
Copy-paste configs are provided for all 8 supported clients. Pick your client below.
Add to ~/.claude.json
{
"mcpServers": {
"square": {
"command": "npx",
"args": [
"square-mcp-server",
"start"
],
"env": {
"ACCESS_TOKEN": "<ACCESS_TOKEN>",
"SANDBOX": "<SANDBOX>"
}
}
}
}claude mcp add square -- npx square-mcp-server startAvailable tools
| Tool | Description |
|---|---|
| get_service_info | Discovers the methods available for a given Square service (payments, catalog, orders, customers, bookings, and more). |
| get_type_info | Gets the detailed parameter requirements for a specific Square API method. |
| make_api_request | Executes a call against the Square Connect API for the chosen service and method. |
Required configuration
- ACCESS_TOKENRequired
Square access token used to authenticate API calls.
- SANDBOXOptional
Set to true to target the Square sandbox environment.
- PRODUCTIONOptional
Set to true to target the Square production environment.
- DISALLOW_WRITESOptional
Restrict the server to read-only API calls.
What you can do with it
Take a payment or send an invoice
An agent discovers the payments or invoices service, learns the required fields, and makes the API call to create a payment link or send an invoice without anyone touching the dashboard.
Answer questions across the business
Because the server reaches the whole Connect API, the agent can look up a customer, their recent orders, current inventory, and loyalty balance to resolve a support question end to end.
FAQ
- Is it free?
- Yes. The Square MCP server is open source and free to run; you pay only the normal Square processing fees on any real transactions it helps create.
- Does it support remote/OAuth?
- Yes. Square recommends the hosted remote server at https://mcp.squareup.com/sse, which supports OAuth login with granular scoped permissions. The local stdio option (npx square-mcp-server start) uses a Square access token in the ACCESS_TOKEN env var instead.
- Can I keep an agent from changing data?
- Yes. Set DISALLOW_WRITES to restrict the server to read-only API calls, or scope the OAuth grant / access token to only the permissions a given agent needs.