Which integrations are available for this 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.

How do I use Square Model Context Protocol Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. 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

by ampcome-mcps

Overview Schema Source Related Servers Discussions Admin

TypeScript

Hybrid

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-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.

Related MCP server: paystack-mcp-server

Remote MCP Server

Square now offers a hosted remote MCP server at:

https://mcp.squareup.com/sse

The 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
`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%2Fsse&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.

# 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/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
`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.

Available Tools

3 tools

get_service_infoA

Get information about a Square API service. Call me before trying to get type info

ParametersJSON Schema

Name	Required	Description	Default
`service`	Yes	The Square API service category (e.g., 'catalog', 'payments')

TDQS

A3.7/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description must disclose behavior. It only says 'get information', without mentioning whether it's read-only, idempotent, or any side effects. Minimal transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two efficient sentences: first states purpose, second provides usage guidance. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a simple info tool with one parameter, but lacks description of the output format or any additional behavioral context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% description coverage for the only parameter, so baseline is 3. Tool description does not add extra meaning beyond the schema parameter description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Describes a specific action: getting info about a Square API service. Explicitly differentiates from sibling tool get_type_info by telling the agent to call this before that.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear directive to call this before get_type_info, indicating proper ordering. However, no guidance on when not to use or alternatives like make_api_request.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_type_infoA

Get type information for a Square API method. You must call this before calling the make_api_request tool.

ParametersJSON Schema

Name	Required	Description	Default
`service`	Yes	The Square API service category (e.g., 'catalog', 'payments')
`method`	Yes	The API method to call (e.g., 'list', 'create')

TDQS

A3.5/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must cover behavior. It states it 'gets type information' but does not disclose whether it is read-only, any side effects, or what the response structure looks like, leaving significant gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose and a clear usage instruction. Every sentence adds value with no wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple prerequisite tool, the description is acceptable but lacks detail on return values and behavioral context. Given no output schema, the agent might need more info to effectively use the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, with both parameters described. The description adds no additional information beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it gets type information for a Square API method, and the prerequisite relationship with make_api_request distinguishes it from sibling tools, though it does not specify what 'type information' entails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly instructs the agent to call this tool before make_api_request, providing clear usage context. However, it does not mention when not to use it or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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.

ParametersJSON Schema

Name	Required	Description
`service`	Yes	The Square API service category (e.g., 'catalog', 'payments')
`method`	Yes	The API method to call (e.g., 'list', 'create')
`request`	No	The request object for the API call.

TDQS

B3.3/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but only states it is a unified tool and lists services. It does not disclose that it makes HTTP calls, requires authentication, can modify data, or has rate limits. Minimal behavioral context is provided.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—two sentences with no superfluous words. It front-loads the core purpose and then lists services efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the tool's complexity (any API operation), the description lacks details on return values, how to structure the request object, or supported methods beyond 'list' and 'create' implied. Sibling tools exist but the description does not fully compensate for missing output schema or behavioral specifics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds value by enumerating all available services, which is absent as enum constraints in the schema. This helps the agent select valid service values, going beyond the generic schema description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it is a unified tool for all Square API operations, clearly indicating its purpose as a general-purpose API caller. It distinguishes from sibling tools (get_service_info, get_type_info) by specifying it performs operations rather than information retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description advises to 'get types before calling,' providing a prerequisite but not explicit when-to-use or when-not-to-use guidance. It implies this is the primary tool for API calls but does not contrast with alternatives beyond the mention of getting types.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

3 tool updatesAug 18, 2025
- First observedget_service_info
- First observedget_type_info
- First observedmake_api_request

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored 2026-04-18 09:05 across 3 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count3/5

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.

Completeness4/5

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

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

Store MCPOAuth
com.store-mcp
Connect AI to store orders, products and inventory with scoped access and human approvals.
E-commerce & Retail ERP Systems
1
API.market MCP GatewayOAuth
io.github.Noveum
Connect AI agents to 580+ APIs with OAuth or API-key auth. Hosted gateway; API pricing varies.
Agent Orchestration
1
BankSyncOAuth
io.banksync
Connect AI agents to bank accounts, transactions, balances, and investments.
Finance Customer Data Platforms App Automation
22
ComposioOAuth
io.github.ComposioHQ
Connect AI agents to 1000+ apps with managed authentication and tool-calling.
Agent Orchestration App Automation
21

Related MCP Servers

ConsignCloud MCP Server
E-commerce & Retail ERP Systems
modellers
A
license
B
quality
D
maintenance
Enables AI assistants to manage consignment and retail business operations through the ConsignCloud API, including inventory management, sales tracking, vendor accounts, and analytics.
Updated 8 months ago (2026-01-14 07:36 UTC)
26
1
GPL 3.0
paystack-mcp-serverofficial
Payments & Billing Finance
PaystackOSS
A
license
A
quality
C
maintenance
Enables AI assistants to interact with the full range of Paystack APIs, allowing operations like transaction management, customer creation, and payments through natural language.
Updated 3 months ago (2026-06-29 01:35 UTC)
2
11 npm
55
MIT
Spreedly MCP Serverofficial
Payments & Billing Finance
spreedly
A
license
B
quality
C
maintenance
Enables AI assistants to manage payments via Spreedly API, including gateways, transactions, and payment method tokenization.
Updated 17 days ago (2026-09-09 21:58 UTC)
32
18 npm
10
Apache 2.0
paystack-mcp
Payments & Billing E-commerce & Retail
kohasummons
A
license
B
quality
D
maintenance
Enables AI agents to manage Paystack payments, products, customers, and transactions through natural language.
Updated a year ago (2025-04-28 10:00 UTC)
28
11 npm
9
MIT

Square Model Context Protocol Server (Beta)

Quick Start

Remote MCP Server

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

Available Tools

TDQS

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

ConsignCloud MCP Server

paystack-mcp-serverofficial

Spreedly MCP Serverofficial

paystack-mcp