# Square

> Process payments and manage orders, catalog, inventory, and bookings on Square — official MCP.

[Canonical HTML page](https://top-mcps.com/mcp/square) · [server.json](https://top-mcps.com/mcp/square.json) · [methodology](https://top-mcps.com/about/methodology)

## Install

### Claude Desktop — `claude_desktop_config.json`

Paste under mcpServers. Fully quit and reopen Claude after editing.

```json
{
  "mcpServers": {
    "square": {
      "command": "npx",
      "args": [
        "square-mcp-server",
        "start"
      ]
    }
  }
}
```

### Claude Code — `CLI or .mcp.json`

Run from your repo. Commit .mcp.json to share with your team.

```shell
claude mcp add square -- npx square-mcp-server start
```

### Cursor — `.cursor/mcp.json`

Global path: ~/.cursor/mcp.json. Reload window after editing.

```json
{
  "mcpServers": {
    "square": {
      "command": "npx",
      "args": [
        "square-mcp-server",
        "start"
      ]
    }
  }
}
```

### VS Code — `.vscode/mcp.json`

VS Code uses the "servers" key (not "mcpServers").

```jsonc
{
  "servers": {
    "square": {
      "command": "npx",
      "args": [
        "square-mcp-server",
        "start"
      ]
    }
  }
}
```

### Windsurf — `~/.codeium/windsurf/mcp_config.json`

Open via Cascade → hammer icon → Configure.

```json
{
  "mcpServers": {
    "square": {
      "command": "npx",
      "args": [
        "square-mcp-server",
        "start"
      ]
    }
  }
}
```

### Cline — `cline_mcp_settings.json`

Open via the Cline sidebar → MCP Servers → Edit.

```json
{
  "mcpServers": {
    "square": {
      "command": "npx",
      "args": [
        "square-mcp-server",
        "start"
      ]
    }
  }
}
```

### Continue — `~/.continue/config.json`

Continue uses modelContextProtocolServers with a transport block.

```json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "square-mcp-server",
            "start"
          ]
        }
      }
    ]
  }
}
```

### Codex CLI — `~/.codex/config.toml`

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

```shell
# ~/.codex/config.toml
[mcp_servers.square]
command = "npx"
args = [
  "square-mcp-server",
  "start",
]
```

### Zed — `~/.config/zed/settings.json`

Zed calls them "context_servers". Settings live-reload on save.

```jsonc
{
  "context_servers": {
    "square": {
      "command": {
        "path": "npx",
        "args": [
          "square-mcp-server",
          "start"
        ]
      }
    }
  }
}
```

### ChatGPT — `ChatGPT → Settings → Connectors (remote URL)`

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.

```json
{
  "name": "Square",
  "transport": "http",
  "url": "https://mcp.squareup.com/sse"
}
```

## At a glance

- **Maintainer:** Square
- **Transport:** stdio, SSE
- **Auth model:** OAuth 2.1
- **Required secrets:** None
- **Supported clients:** Claude, Cursor, VS Code, Any MCP-compatible client, Square accounts
- **License:** Apache-2.0
- **Language:** TypeScript
- **Latest version:** latest
- **Last verified:** 2026-07-16
- **GitHub stars:** 101 (fetched 2026-07-17T12:42:37.700Z)
- **Score:** 71/100 (rubric 2026-04 — see https://top-mcps.com/about/methodology)
- **Source:** https://github.com/square/square-mcp-server

## 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
- OAuth via the hosted remote server

**Not for:**
- SaaS subscription billing (use Stripe/Paddle)
- Teams wanting a minimal fixed tool set
- Non-Square commerce stacks

## Description

Square's official MCP (Apache-2.0) exposes 40+ Square services through three discovery tools — get_service_info, get_type_info, and make_api_request — so an agent can reach the entire Square API (payments, orders, catalog, inventory, invoices, bookings, loyalty) without a bespoke tool per endpoint. A hosted remote server at mcp.squareup.com handles OAuth.

## Why it matters

Square runs point-of-sale, e-commerce, and appointments for millions of sellers. The official MCP is the first-party path for an agent to read sales and — behind a scope — take payment and inventory actions.

## Key features

- 40+ Square services via 3 discovery tools
- Hosted remote server with OAuth (mcp.squareup.com)
- DISALLOW_WRITES for read-only mode
- Sandbox and production environments
- Official Square, Apache-2.0, TypeScript

## FAQ

### Remote or local?

Both. The recommended path is the hosted remote server at mcp.squareup.com/sse with OAuth (log in with Square, no token). Locally, run `npx square-mcp-server start` with an `ACCESS_TOKEN` env var.

### How do I make it read-only?

Set `DISALLOW_WRITES=true` so the agent can query sales and catalog without being able to take payment or mutate inventory.

### Why only three tools?

Square exposes the whole API through get_service_info, get_type_info, and make_api_request — the agent discovers services and calls them dynamically instead of loading hundreds of static tools.

## Changelog

- **2026-07-16** — Refreshed install snippets and fact sheet; verified for 2026.
- **2025-05-01** — Initial directory listing.