COMMERCE / Square
Square Commerce MCP
Connects an assistant to Square APIs for customer, catalogue, order and other authorized commerce operations.
“The Square MCP server is currently in Beta.”
01 / THE REASONING
Why this made the selection.
- Provides publisher-documented OAuth integration.
- Documents a separate local Sandbox testing path.
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.
- 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"
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
https://developer.squareup.com/docs/mcp
Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, install, access, compatibility, transports, configExample