---
title: "Square Commerce MCP: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/square-hosted/
description: "Connects an assistant to Square APIs for customer, catalogue, order and other authorized commerce operations."
---

# Square Commerce MCP: review, setup & limitations · Undominated.ai

> Connects an assistant to Square APIs for customer, catalogue, order and other authorized commerce operations.

[← Explore all mcp servers](/mcp-servers/)

COMMERCE / Square

# Square Commerce MCP

Connects an assistant to Square APIs for customer, catalogue, order and other authorized commerce operations.

 [See setup guidance ↓](#setup)[Original source ↗](https://developer.squareup.com/docs/mcp)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 1 linked sources
 Publisher Square
 Licence Not established
 [Read what was—and wasn’t—checked ↓](#review)

“The Square MCP server is currently in Beta.”

 [Square · upstream description ↗](https://developer.squareup.com/docs/mcp) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Provides publisher-documented OAuth integration.
- Documents a separate local Sandbox testing path.

### A good fit for

 - Exploring Square API workflows in Sandbox.
- Inspecting authorized customer and order data.

### Weigh up before choosing

 - The hosted endpoint accesses production only; it is not a Sandbox connection.
- Beta; tools can invoke writes within granted OAuth permissions.
- Square maintains a client allowlist. Local DISALLOW_WRITES is a documented switch, not an independently tested security boundary.
- A sandbox setting in a local process does not change the remote production endpoint, and generic OAuth support does not ensure the client is on Square's allowlist.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - https://developer.squareup.com/docs/mcp
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - The guide explicitly separates local Sandbox access from hosted production access.
- The endpoint inherits granted account permissions; connecting does not validate transaction logic.
- MCP lane cross-review compared retained publisher setup/capability evidence with this proposed record before integration; no installation or authenticated calls were performed.
- Remote Square MCP connects to production resources only and maintains a client allowlist; Sandbox requires a separately configured local instance.

### Not established by this review

 - Authentication, live tool execution, hosted implementation and security isolation were not tested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://developer.squareup.com/docs/mcp)
 - First test the documented local adapter with ACCESS_TOKEN set to a Sandbox credential, SANDBOX=true and DISALLOW_WRITES=true; the documented launcher is npx square-mcp-server start.
- Connect the hosted endpoint only for intended production work and select required OAuth scopes.
- Review target account and proposed operations before allowing writes.
- Test prompts with a local SANDBOX=true configuration and use DISALLOW_WRITES=true when inspection is intended before connecting the hosted production service.

### Before you start

 - Square account and supported OAuth client.
- Optional local testing needs Node.js and Sandbox credentials.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "square-hosted": {
 "type": "http",
 "url": "https://mcp.squareup.com/mcp"
 }
 }
} Copy configuration ↗

### Compatibility

Remote MCP clients with Streamable HTTP support

### Transports

Remote HTTP

### Hosted service

 - Reads and can change commerce resources permitted by the authorized account and scopes.

### Cost model

Square account/API terms and transaction charges may apply; no separate MCP tariff established here.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Publisher setup and capability reference ↗](https://developer.squareup.com/docs/mcp) Checked 2026-10-14 https://developer.squareup.com/docs/mcp Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### PayPal hosted MCP ↗ Connects assistants to PayPal commerce tools, including invoice creation, with separate Sandbox and production endpoints.](/mcp-servers/paypal-hosted/)[### Square MCP Server ↗ Gives an MCP client generic access to Square's API: discover a service's methods and types, then execute requests, locally with an access token or through Square's hosted OAuth endpoint.](/mcp-servers/square/)[### Airtable MCP Server ↗ Hosted Airtable server exposing bases, records, tables, interfaces and automations as tools over Streamable HTTP. Every connection is scoped to authorised bases and the server enforces existing Airtable permissions, so a read-only base stays read-only through MCP.](/mcp-servers/airtable/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
