Square Model Context Protocol Server
Enables integration with Apple Pay through Square's connect API, allowing for Apple Pay payment processing.
Provides comprehensive access to Square's API ecosystem, allowing for catalog management, order processing, payment handling, customer management, inventory tracking, subscription management, and other commerce operations through Square's platform.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Square Model Context Protocol Server list my recent orders from the last week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Square Model Context Protocol Server (Beta)
This project follows the Model Context Protocol standard, allowing AI assistants to interact with Square's connect API.
Quick Start
Get up and running with the Square MCP server using npx:
# 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-serverReplace 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.
Related MCP server: paystack-mcp-server
Remote MCP Server
Square now offers a hosted remote MCP server at:
https://mcp.squareup.com/sseThe remote MCP is recommended as it uses OAuth authentication, allowing you to log in with your Square account directly without having to create or manage access tokens manually.
Configuration Options
Environment Variable | Purpose | Example |
| Your Square API access token |
|
| Use Square sandbox environment |
|
| Use Square production environment |
|
| Restrict to read-only operations |
|
| Specify Square API version |
|
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:
Or copy and paste the URL into your browser's address bar.
# Automatic installation
npx square-mcp-server install
# Get URL for manual installation
npx square-mcp-server get-goose-urlThe 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/sse"]
}
}
}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 |
| Discover methods available for a service | Exploration and discovery |
| Get detailed parameter requirements | Request preparation |
| 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 |
| Apple Pay integration |
| Bank account management |
| Custom attributes for bookings |
| Appointment booking management |
| Payment card management |
| Cash drawer management |
| Catalog management (items, categories, etc.) |
| Checkout and payment processing |
| Custom attributes for customers |
| Customer grouping |
| Customer segmentation |
| Customer management |
| Square device management |
| Payment dispute handling |
| Event tracking |
| Gift card activity tracking |
| Gift card management |
| Inventory tracking |
| Invoice management |
| Workforce management |
| Custom attributes for locations |
| Location management |
| Loyalty program management |
| Custom attributes for merchants |
| Merchant account management |
| Authentication |
| Custom attributes for orders |
| Order management |
| Payment processing |
| Payout management |
| Refund management |
| Website integration |
| Square Online Code integration |
| Subscription management |
| Staff management |
| Square Terminal management |
| Supplier management |
| Event notifications |
Usage Pattern
For optimal interaction with the Square API through MCP:
Discover: Use
get_service_infoto explore available methodsget_service_info(service: "catalog")Understand: Use
get_type_infoto learn parameter requirementsget_type_info(service: "catalog", method: "list")Execute: Use
make_api_requestto perform the operationmake_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 startDevelopment Workflow
Clone the repository
Install dependencies:
npm installStart development mode:
npm run watchRun the server:
node dist/index.js startTest 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.
Available Tools
3 toolsget_service_infoA
Get information about a Square API service. Call me before trying to get type info
Inputs: service (required).
get_type_infoA
Get type information for a Square API method. You must call this before calling the make_api_request tool.
Inputs: service (required), method (required).
make_api_requestB
Unified tool for all Square API operations. Be sure to get types before calling. Available services: applepay, bankaccounts, bookingcustomattributes, bookings, cards, cashdrawers, catalog, checkout, customercustomattributes, customergroups, customersegments, customers, devices, disputes, events, giftcardactivities, giftcards, inventory, invoices, labor, locationcustomattributes, locations, loyalty, merchantcustomattributes, merchants, oauth, ordercustomattributes, orders, payments, payouts, refunds, sites, snippets, subscriptions, team, terminal, vendors, webhooksubscriptions.
Inputs: service (required), method (required), request.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: get_service_info provides service metadata, get_type_info supplies method type details, and make_api_request handles all actual API calls. The descriptions explicitly state the sequential dependency between them, eliminating any confusion about when to use each tool.
All tools follow a consistent verb_noun pattern (get_service_info, get_type_info, make_api_request) with clear, descriptive names that reflect their specific functions. The naming is uniform and predictable across the entire set.
With only 3 tools, the count feels thin for covering the extensive Square API surface listed (over 40 services). While the tools are well-designed, the minimal number may force agents to rely heavily on a single make_api_request tool for all operations, which could be cumbersome for complex workflows.
The tool set provides complete coverage for the Square API domain through a unified request tool, with preparatory tools for service and type information. However, the reliance on a single generic API call tool may lack the granularity and error handling that dedicated tools for common operations (like create_order or get_payment) would offer, creating minor gaps in usability.
Maintenance
Related MCP Connectors
Connect your AI assistant to Qualy to manage payments, billing, and contacts.
Connect AI assistants to Appimate's Business Agent Tools and Services.
Connect AI to store orders, products and inventory with scoped access and human approvals.
Connect AI agents to 580+ APIs with OAuth or API-key auth. Hosted gateway; API pricing varies.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to manage consignment and retail business operations through the ConsignCloud API, including inventory management, sales tracking, vendor accounts, and analytics.261GPL 3.0

paystack-mcp-serverofficial
AlicenseAqualityDmaintenanceEnables AI assistants to interact with the full range of Paystack APIs, allowing operations like transaction management, customer creation, and payments through natural language.2152 npm56MIT
Spreedly MCP Serverofficial
AlicenseBqualityBmaintenanceEnables AI assistants to manage payments via Spreedly API, including gateways, transactions, and payment method tokenization.32113 npm10Apache 2.0- AlicenseBqualityDmaintenanceEnables AI agents to manage Paystack payments, products, customers, and transactions through natural language.286 npm9MIT