Square MCP Server

The Square MCP Server is the official Model Context Protocol implementation maintained by Square (Block, Inc.) that bridges AI assistants and Square's Connect REST API. It exposes Square's full commerce platform, payments, orders, customers, catalog, inventory, bookings, invoices, loyalty, and more, through a small set of generic discovery and execution tools, allowing an agent to introspect available services and then call them.

Rather than listing dozens of individual tools per endpoint, the server uses a meta tool design: get_service_info lists methods for a given Square service, get_type_info returns the parameter schema for any call, and make_api_request executes the actual operation. This covers 40+ Square services through three primitives, keeping the tool surface compact while exposing the entire API.

The server can run remotely via Square's hosted endpoint (https://mcp.squareup.com/sse) using OAuth, which is the recommended path, or locally via npx square-mcp-server using a Square access token. It supports sandbox and production modes, a read-only switch (DISALLOW_WRITES), and pinned API versions. The project is open source under Apache 2.0 and is in Beta.

Tools

Prerequisites

• Node.js and npm installed
• A Square developer account (free)
• For local mode: a Square access token from Square Developer docs
• For remote mode: ability to complete OAuth in a browser

Remote setup (recommended)

Square hosts the MCP server at https://mcp.squareup.com/sse. Authentication uses OAuth, so you do not need to manage access tokens manually.

Claude Desktop config:

{
  "mcpServers": {
    "mcp_square_api": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.squareup.com/sse"]
    }
  }
}

The first run will open a browser window to authenticate with your Square account.

Local setup

Install and run directly with npx:

npx square-mcp-server start

Claude Desktop config:

{
  "mcpServers": {
    "mcp_square_api": {
      "command": "npx",
      "args": ["square-mcp-server", "start"],
      "env": {
        "ACCESS_TOKEN": "YOUR_SQUARE_ACCESS_TOKEN",
        "SANDBOX": "true"
      }
    }
  }
}

Environment variables (local mode)

Supported clients

Per Square's docs, supported assistants include Claude.ai, Claude Desktop, Claude Enterprise & Teams, Goose, Cursor, and Windsurf. The remote server uses an allowlist to prevent malicious client registrations.

• Look up a customer in Square and pull their recent orders, refunds, and outstanding invoices for support workflows.
• Create or update catalog items, modifiers, and inventory counts across locations from a chat agent.
• Process or refund payments and reconcile transactions against orders without leaving the assistant.
• Manage Square Appointments: list available slots, create bookings, and reschedule for a given staff member or location.
• Run loyalty program operations such as enrolling buyers, adjusting points, and querying loyalty status.

• "List all payments from yesterday at my Brooklyn location and total them by card brand."
• "Find the customer with email jane@example.com and show their last 5 orders."
• "Create a new catalog item called 'Cold Brew 16oz' priced at $5.50 and add 24 units of inventory at location LXXXX."
• "Refund payment ID abc123 for $12.00 and add a note about the customer complaint."
• "Show me available booking slots tomorrow for staff member John at the downtown location."

• Official server maintained by Square, published under the square GitHub org and hosted at mcp.squareup.com.
• Broad coverage: exposes 40+ Square services (payments, orders, customers, catalog, inventory, bookings, loyalty, etc.) through three generic tools.
• Supports both OAuth-based remote hosting and local self-hosting with sandbox, production, and read-only modes.
• Open source under Apache 2.0.

• Currently labeled Beta; behavior and tool surface may change.
• Meta-tool design (get_service_info / get_type_info / make_api_request) means agents must discover and chain calls, which can use more tokens than purpose-built tools.
• Local mode requires manual access token management and per-environment flags (SANDBOX vs PRODUCTION).

• Stripe MCP Server for payments and billing on Stripe.
• PayPal MCP Server for PayPal commerce and payouts.
• Shopify Dev MCP for ecommerce storefront and admin operations.