MCP100 IndexFinance & Payments

ShortlistFirst-party MCP

square

by ecosystem:square

Updated September 21, 2026

Finance & PaymentsFinancial Services & InvestingRetail & E-commerceAccess · Self-hosted

MCP100 verdict

Connect AI clients to supported Square commerce, payment, customer, catalog, and merchant workflows through MCP.

MCP100 Assessment

Editorial verdict

Promising commerce tooling, but it remains on the Shortlist until financial action boundaries, merchant permissions, customer-data exposure, credential handling, and production safeguards are independently reviewed.

Reviewed July 30, 2026

Task Fit

Mapped

Specialized workflows

Trust

Status warning

mcp_relevance; documentation; client_coverage; tool_contract; install_supply_chain; advisory_freshness; resource_type_requirements

Maintenance

Activity observed

A dated repository or package update is available; editorial maintenance review is still pending.

Popularity

Signals available

Visible usage signals are shown for discovery only, not as proof of safety.

Best for

Commerce and payment integration development for Square.

Not ideal for

Production use before the documented maturity gaps are resolved

Avoid if

The connected identity is broader than the task requires
Tool calls cannot be reviewed before consequential mutations

Trade-offs

The implementation is explicitly Beta and has limited production operating history.

Evidence scope

Evidence

Current source snapshot

Popularity

106 MCP repository stars

5.4k package downloads / 30 days

Repository identity: square/square-mcp-server

Package identity: square-mcp-server

Official npm package square-mcp-server: 5,403 downloads / 30 days.

Stars observed August 14, 2026 · Downloads observed September 8, 2026

Exact implementation repository metric.

Exact package is documented; download evidence is unavailable.

Maintenance

Publisher activity observed April 9, 2026

Current source snapshot

Trust review

Source relationship: First-party MCP

Reviewed July 30, 2026

Sources

GitHub repository ↗

Evidence-backed setup

Install & Agents

Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.

Claude Code

Local stdio

MCP100 logic checked

claude mcp add square-api -- npx "mcp-remote" "https://mcp.squareup.com/sse"

The publisher connection details were combined with this client's official MCP transport configuration; installation was not executed by MCP100.

Verify safely: Restart Claude Code, confirm square-api tools are listed, and perform one read-only test with non-sensitive data.

Uninstall and revoke

Remove square-api from Claude Code, restart the client, remove any separately installed package, and revoke dedicated credentials if used.

Evidence & methodology

Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.

Evidence checked 2026-08-12

Evidence 1 ↗Evidence 2 ↗

Read additional publisher installation details

From the publisher README

Publisher installation details

Original client setup and configuration retained from the publisher documentation.

View original README ↗

Publisher-documented clients

Goose

These names appear in the publisher's installation documentation. MCP100-verified configurations are shown separately above when available.

Quick Start

Get up and running with the local server using npx. This runs the server on your own machine with your own access token; for the hosted server, see the note above.

# Basic startup
npx square-mcp-server start

# With environment configuration
ACCESS_TOKEN=YOUR_SQUARE_ACCESS_TOKEN SANDBOX=true npx square-mcp-server start

# local runs
npx /path/to/project/square-mcp-server

Replace YOUR_SQUARE_ACCESS_TOKEN with your actual Square access token. You can obtain your access token by following the guide at Square Access Tokens. You can also set environment variables before running the command.

Remote MCP Server

Square offers a hosted remote MCP server at:

https://mcp.squareup.com/mcp

The remote server is recommended: it uses OAuth, so you sign in with your Square account instead of creating and managing access tokens. Setup guides for Claude, ChatGPT, Goose and other assistants are in the Square MCP documentation. The older https://mcp.squareup.com/sse endpoint is still served for existing SSE configurations.

Loading optional publisher installation details…

Read publisher documentation

Publisher documentation

Publisher README

Original product, capability, tool, and usage documentation from the MCP publisher. Installation sections appear under Install & Agents.

View original README ↗

Square Model Context Protocol Server (Beta)

This project follows the Model Context Protocol standard, allowing AI assistants to interact with Square's connect API.

Most people should use the hosted server. Square runs a remote MCP server at https://mcp.squareup.com/mcp with OAuth sign-in; see the Square MCP documentation for setup with your AI assistant. This repository is the local, self-hosted server: a starting point if you want to run your own copy. Code changes go through the generator described under Contributing.

Configuration Options

Environment Variable	Purpose	Example
`ACCESS_TOKEN`	Your Square API access token	`ACCESS_TOKEN=sq0atp-...`
`SANDBOX`	Use Square sandbox environment	`SANDBOX=true`
`PRODUCTION`	Use Square production environment	`PRODUCTION=true`
`DISALLOW_WRITES`	Restrict to read-only operations	`DISALLOW_WRITES=true`
`SQUARE_VERSION`	Specify Square API version	`SQUARE_VERSION=2025-04-16`

Integration with AI Assistants

Goose Integration

To configure the Square MCP Server with Goose:

Remote MCP

To install the Square remote MCP in Goose, click this URL on a computer where Goose is installed:

goose://extension?cmd=npx&arg=mcp-remote&arg=https%3A%2F%2Fmcp.squareup.com%2Fmcp&id=square_mcp_production_remote&name=Square%20MCP%20Remote&description=Square%20Production%20MCP%20Remote

Or copy and paste the URL into your browser's address bar.

The commands below configure the local server (npx square-mcp-server start), not the hosted one:

# Automatic installation
npx square-mcp-server install

# Get URL for manual installation
npx square-mcp-server get-goose-url

The install command automatically updates your Goose configuration.

Claude Desktop Integration

For Claude Desktop integration, see the Model Context Protocol Quickstart Guide. Add this configuration to your claude_desktop_config.json:

Remote MCP

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

This approach allows you to authenticate directly with your Square account credentials without needing to manage access tokens.

Local MCP

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

Tool Reference

The Square MCP Server provides a streamlined set of tools for interacting with Square APIs:

Tool	Description	Primary Use
`get_service_info`	Discover methods available for a service	Exploration and discovery
`get_type_info`	Get detailed parameter requirements	Request preparation
`make_api_request`	Execute API calls to Square	Performing operations

Service Catalog

Square MCP Server provides access to Square's complete API ecosystem. Check out the Square API Documentation for detailed information about each service:

Service	Description
`applepay`	Apple Pay integration
`bankaccounts`	Bank account management
`bookingcustomattributes`	Custom attributes for bookings
`bookings`	Appointment booking management
`cards`	Payment card management
`cashdrawers`	Cash drawer management
`catalog`	Catalog management (items, categories, etc.)
`checkout`	Checkout and payment processing
`customercustomattributes`	Custom attributes for customers
`customergroups`	Customer grouping
`customersegments`	Customer segmentation
`customers`	Customer management
`devices`	Square device management
`disputes`	Payment dispute handling
`events`	Event tracking
`giftcardactivities`	Gift card activity tracking
`giftcards`	Gift card management
`inventory`	Inventory tracking
`invoices`	Invoice management
`labor`	Workforce management
`locationcustomattributes`	Custom attributes for locations
`locations`	Location management
`loyalty`	Loyalty program management
`merchantcustomattributes`	Custom attributes for merchants
`merchants`	Merchant account management
`oauth`	Authentication
`ordercustomattributes`	Custom attributes for orders
`orders`	Order management
`payments`	Payment processing
`payouts`	Payout management
`refunds`	Refund management
`sites`	Website integration
`snippets`	Square Online Code integration
`subscriptions`	Subscription management
`team`	Staff management
`terminal`	Square Terminal management
`vendors`	Supplier management
`webhooksubscriptions`	Event notifications

Usage Pattern

For optimal interaction with the Square API through MCP:

Discover: Use get_service_info to explore available methods
```
get_service_info(service: "catalog")
```
Understand: Use get_type_info to learn parameter requirements
```
get_type_info(service: "catalog", method: "list")
```

Execute: Use make_api_request to perform the operation

make_api_request(service: "catalog", method: "list", request: {})

Development and Debugging

Using MCP Inspector

The MCP Inspector provides a visual interface for testing:

# Build the project
npm run build

# Start the inspector with the Square MCP Server
npx @modelcontextprotocol/inspector node dist/index.js start

Development Workflow

Clone the repository
Install dependencies: npm install
Start development mode: npm run watch
Run the server: node dist/index.js start
Test your changes using the MCP Inspector

Contributing

This repository is auto-generated from Square's OpenAPI Specification. While contributions are welcome, please note that changes will need to be incorporated into the generator that produces this code. Please open an issue to discuss proposed changes before submitting a pull request.

Loading optional publisher documentation…

FAQ

What can Square MCP do?

Use authorized Square commerce and payment-development workflows through official MCP tools.

Can Square MCP call Square APIs for payment and commerce workflows?

Yes. The official server uses generic service-discovery, type-discovery, and API-request tools to access supported Square APIs. Write operations can be disabled, so the exact commerce actions available depend on the configured server and Square authorization.

Does Square MCP work with Codex?

Yes. MCP100 reviewed an evidence-backed setup for Codex, but has not independently verified it with a live runtime test.

How does Square MCP authenticate?

The publisher documents Square OAuth and developer credentials.

Is Square MCP safe to connect to a production commerce account?

The implementation is explicitly Beta and has limited production operating history. Use a test environment where practical, least-privilege credentials, narrowly enabled tools, and explicit confirmation for mutations. MCP100 did not execute third-party server code during this documentation review.

Is this an official MCP?

ecosystem:square is listed as First-party MCP in MCP100’s current evidence.

Current official resources:

Publisher documentation ↗

Square Model Context Protocol Server (Beta)

This project follows the Model Context Protocol standard, allowing AI assistants to interact with Square's connect API.

Most people should use the hosted server. Square runs a remote MCP server at https://mcp.squareup.com/mcp with OAuth sign-in; see the Square MCP documentation for setup with your AI assistant. This repository is the local, self-hosted server: a starting point if you want to run your own copy. Code changes go through the generator described under Contributing.

Configuration Options

Environment Variable	Purpose	Example
`ACCESS_TOKEN`	Your Square API access token	`ACCESS_TOKEN=sq0atp-...`
`SANDBOX`	Use Square sandbox environment	`SANDBOX=true`
`PRODUCTION`	Use Square production environment	`PRODUCTION=true`
`DISALLOW_WRITES`	Restrict to read-only operations	`DISALLOW_WRITES=true`
`SQUARE_VERSION`	Specify Square API version	`SQUARE_VERSION=2025-04-16`

Integration with AI Assistants

Goose Integration

To configure the Square MCP Server with Goose:

Remote MCP

To install the Square remote MCP in Goose, click this URL on a computer where Goose is installed:

goose://extension?cmd=npx&arg=mcp-remote&arg=https%3A%2F%2Fmcp.squareup.com%2Fmcp&id=square_mcp_production_remote&name=Square%20MCP%20Remote&description=Square%20Production%20MCP%20Remote

Or copy and paste the URL into your browser's address bar.

The commands below configure the local server (npx square-mcp-server start), not the hosted one:

# Automatic installation
npx square-mcp-server install

# Get URL for manual installation
npx square-mcp-server get-goose-url

The install command automatically updates your Goose configuration.

Claude Desktop Integration

For Claude Desktop integration, see the Model Context Protocol Quickstart Guide. Add this configuration to your claude_desktop_config.json:

Remote MCP

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

This approach allows you to authenticate directly with your Square account credentials without needing to manage access tokens.

Local MCP

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

Tool Reference

The Square MCP Server provides a streamlined set of tools for interacting with Square APIs:

Tool	Description	Primary Use
`get_service_info`	Discover methods available for a service	Exploration and discovery
`get_type_info`	Get detailed parameter requirements	Request preparation
`make_api_request`	Execute API calls to Square	Performing operations

Service Catalog

Square MCP Server provides access to Square's complete API ecosystem. Check out the Square API Documentation for detailed information about each service:

Service	Description
`applepay`	Apple Pay integration
`bankaccounts`	Bank account management
`bookingcustomattributes`	Custom attributes for bookings
`bookings`	Appointment booking management
`cards`	Payment card management
`cashdrawers`	Cash drawer management
`catalog`	Catalog management (items, categories, etc.)
`checkout`	Checkout and payment processing
`customercustomattributes`	Custom attributes for customers
`customergroups`	Customer grouping
`customersegments`	Customer segmentation
`customers`	Customer management
`devices`	Square device management
`disputes`	Payment dispute handling
`events`	Event tracking
`giftcardactivities`	Gift card activity tracking
`giftcards`	Gift card management
`inventory`	Inventory tracking
`invoices`	Invoice management
`labor`	Workforce management
`locationcustomattributes`	Custom attributes for locations
`locations`	Location management
`loyalty`	Loyalty program management
`merchantcustomattributes`	Custom attributes for merchants
`merchants`	Merchant account management
`oauth`	Authentication
`ordercustomattributes`	Custom attributes for orders
`orders`	Order management
`payments`	Payment processing
`payouts`	Payout management
`refunds`	Refund management
`sites`	Website integration
`snippets`	Square Online Code integration
`subscriptions`	Subscription management
`team`	Staff management
`terminal`	Square Terminal management
`vendors`	Supplier management
`webhooksubscriptions`	Event notifications

Usage Pattern

For optimal interaction with the Square API through MCP:

Discover: Use get_service_info to explore available methods
```
get_service_info(service: "catalog")
```
Understand: Use get_type_info to learn parameter requirements
```
get_type_info(service: "catalog", method: "list")
```

Execute: Use make_api_request to perform the operation

make_api_request(service: "catalog", method: "list", request: {})

Development and Debugging

Using MCP Inspector

The MCP Inspector provides a visual interface for testing:

# Build the project
npm run build

# Start the inspector with the Square MCP Server
npx @modelcontextprotocol/inspector node dist/index.js start

Development Workflow

Clone the repository
Install dependencies: npm install
Start development mode: npm run watch
Run the server: node dist/index.js start
Test your changes using the MCP Inspector

Promising commerce tooling, but it remains on the Shortlist until financial action boundaries, merchant permissions, customer-data exposure, credential handling, and production safeguards are independently reviewed.

Best for

Not ideal for

Avoid if

Trade-offs

Evidence

Popularity

Maintenance

Trust review

Sources

Install & Agents

Claude Code

Publisher installation details

Quick Start

Remote MCP Server

What it does

Representative uses

Important limits

Context Footprint

Access & risk

Other options

Stripe MCP

PayPal MCP

Shopify Storefront MCP

Publisher README

Square Model Context Protocol Server (Beta)

Configuration Options

Integration with AI Assistants

Goose Integration

Remote MCP

Claude Desktop Integration

Remote MCP

Local MCP

Tool Reference

Service Catalog

Usage Pattern

Development and Debugging

Using MCP Inspector

Development Workflow

Contributing

FAQ

Publisher installation details

Quick Start

Remote MCP Server

Publisher README

Square Model Context Protocol Server (Beta)

Configuration Options

Integration with AI Assistants

Goose Integration

Remote MCP

Claude Desktop Integration

Remote MCP

Local MCP

Tool Reference

Service Catalog

Usage Pattern

Development and Debugging

Using MCP Inspector

Development Workflow

Contributing