Square Model Context Protocol Server (Beta)

What is Square Model Context Protocol Server (Beta)?

Square Model Context Protocol Server (Beta) is an implementation of the Model Context Protocol (MCP) standard that allows AI assistants to interact with Square’s Connect API. It is aimed at developers who want to integrate Square’s commerce, payments, and business management capabilities into AI-driven workflows.

How to use Square Model Context Protocol Server (Beta)?

The server can be started locally using npx square-mcp-server start with environment variables such as ACCESS_TOKEN and SANDBOX. A hosted remote MCP version is also available at https://mcp.squareup.com/sse and can be configured via OAuth. Integration instructions are provided for Goose (with npx square-mcp-server install) and Claude Desktop (via claude_desktop_config.json). Configuration options include ACCESS_TOKEN, SANDBOX, PRODUCTION, DISALLOW_WRITES, and SQUARE_VERSION.

Key features of Square Model Context Protocol Server (Beta)

• Three core tools: get_service_info, get_type_info, and make_api_request
• Access to Square’s complete API ecosystem (40+ services)
• Supports both local (access token) and remote (OAuth) authentication
• Sandbox and production environment switching via environment variables
• Read-only mode available with DISALLOW_WRITES=true
• Remote MCP server hosted at mcp.squareup.com/sse

Use cases of Square Model Context Protocol Server (Beta)

• AI-driven catalog management (items, categories, inventory)
• Automated payment processing and refund handling
• Customer relationship management (creation, segmentation, custom attributes)
• Order and invoice management via natural language queries
• Workforce and subscription management (labor, team, subscriptions)

FAQ from Square Model Context Protocol Server (Beta)

What authentication methods does the server support?

Local mode requires a Square access token set via the ACCESS_TOKEN environment variable. The remote MCP server uses OAuth, allowing users to log in with their Square account directly without manual token management.

Can I run the server in a sandbox environment?

Yes. Set the SANDBOX=true environment variable to use Square’s sandbox environment. Alternatively, PRODUCTION=true forces production mode.

How do I restrict the server to read-only operations?

Set the DISALLOW_WRITES=true environment variable to prevent any write operations through the API.

What tools does the server expose?

The server exposes three tools: get_service_info (discover methods for a service), get_type_info (learn parameter requirements), and make_api_request (execute API calls to Square).

What environment variables are available for configuration?

The supported variables are ACCESS_TOKEN (Square API token), SANDBOX, PRODUCTION, DISALLOW_WRITES, and SQUARE_VERSION (API version).