Manage payments, customers, and subscriptions through Stripe.
Square
Process payments and manage orders, catalog, inventory, and bookings on Square — official MCP.
Quick answer
What it does
Proxies the full Square API to MCP clients via three tools (service discovery, type introspection, and API execution), covering payments, orders, catalog, customers, inventory, invoices, and bookings.
Best for
- Reading Square payments and orders
- Catalog and inventory management
- Invoice and booking workflows
- Point-of-sale reporting
Not for
- SaaS subscription billing (use Stripe/Paddle)
- Teams wanting a minimal fixed tool set
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "square": { "command": "npx", "args": [ "square-mcp-server", "start" ] } } }Paste under mcpServers. Fully quit and reopen Claude after editing.
CLI or .mcp.jsonshellclaude mcp add square -- npx square-mcp-server startRun from your repo. Commit .mcp.json to share with your team.
.cursor/mcp.jsonjson{ "mcpServers": { "square": { "command": "npx", "args": [ "square-mcp-server", "start" ] } } }Global path: ~/.cursor/mcp.json. Reload window after editing.
.vscode/mcp.jsonjsonc{ "servers": { "square": { "command": "npx", "args": [ "square-mcp-server", "start" ] } } }VS Code uses the "servers" key (not "mcpServers").
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "square": { "command": "npx", "args": [ "square-mcp-server", "start" ] } } }Open via Cascade → hammer icon → Configure.
cline_mcp_settings.jsonjson{ "mcpServers": { "square": { "command": "npx", "args": [ "square-mcp-server", "start" ] } } }Open via the Cline sidebar → MCP Servers → Edit.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "npx", "args": [ "square-mcp-server", "start" ] } } ] } }Continue uses modelContextProtocolServers with a transport block.
~/.codex/config.tomlshell# ~/.codex/config.toml [mcp_servers.square] command = "npx" args = [ "square-mcp-server", "start", ]Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "square": { "command": { "path": "npx", "args": [ "square-mcp-server", "start" ] } } } }Zed calls them "context_servers". Settings live-reload on save.
ChatGPT → Settings → Connectors (remote URL)json{ "name": "Square", "transport": "http", "url": "https://mcp.squareup.com/sse" }Paste this into Settings → Connectors → Add custom connector. Requires ChatGPT Pro / Team / Enterprise / Edu with Developer mode enabled. ChatGPT supports remote HTTPS MCP servers only — stdio servers must be hosted on a public HTTPS endpoint first.
- 2
Set required secrets
No credentials required — this MCP runs over stdio without authentication.
- 3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.
Tools & permissions
Tools list pending verification. The server exposes tools over MCP; we haven’t yet parsed its capability manifest into this page. Check the GitHub repo for the authoritative list.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. commerce & payments work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-commerce-payments
Compare Square MCP vs [Stripe MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/square - top-mcps.com listing for Stripe
Install the Square MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/square (fetch https://top-mcps.com/mcp/square.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (no secrets) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 2 updates tracked.Refreshed install snippets and fact sheet; verified for 2026.
Initial directory listing.
More Commerce & Payments MCPs
Other tools in the same category worth evaluating.
Run QuickBooks Online accounting from an agent — invoices, bills, payments, and financial reports.
Official Xero MCP — invoices, contacts, bank transactions, and accounting from an agent.
Compared with Square
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Commerce & Payments? See all Commerce & Payments MCPs →
