square-mcp-server

Square MCP Server

Square payments, catalogs, bookings, and customer data become accessible to AI assistants through this MCP integration. It serves developers connecting Square workflows to clients such as Goose and Claude Desktop, with tools for API discovery, parameter inspection, and requests.

Server facts

square-mcp-server

Project

Author
square
License
Apache-2.0

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
108
Last commit
Data as of

Overview

Square commerce workflows span payments, orders, inventory, appointments, and customer management in this beta integration. Its tools support a discovery-first sequence: get_service_info identifies methods within a selected service, get_type_info explains the parameters for a chosen method, and make_api_request submits the operation. Type inspection is required before making a request. This structure lets an assistant explore the relevant API interface before acting, whether the task concerns catalog items, invoices, refunds, subscriptions, staff, or another listed Square service.

Developers can connect through a local Node-based setup or Square's hosted remote option. Local configuration accepts a Square access token and settings for sandbox or production use, read-only restrictions, and API version selection. The hosted option uses OAuth so users can authenticate with their Square accounts rather than manage access tokens themselves. The documentation includes integration paths for Goose and Claude Desktop, plus testing guidance using MCP Inspector. The repository is generated from Square's OpenAPI specification, so proposed code changes need to be addressed in the generator.

square-mcp-server setup notes

  • square-mcp-server records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers