Square MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SQUARE_ENVIRONMENT | No | Square API environment ('sandbox' or 'production') | sandbox |
| SQUARE_ACCESS_TOKEN | Yes | Your Square API access token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| paymentsC | Manage payment operations using Square API |
| terminalB | Manage Square Terminal operations |
| ordersC | Manage orders and checkout operations |
| catalogC | Manage catalog operations |
| inventoryC | Manage inventory operations |
| subscriptionsB | Manage subscription operations |
| invoicesC | Manage invoice operations |
| teamC | Manage team operations |
| customersC | Manage customer operations |
| loyaltyC | Manage loyalty operations |
| bookingsC | Manage booking operations |
| businessC | Manage business operations |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
The tools are organized into clear domains (bookings, business, catalog, etc.), each with distinct purposes, reducing overlap. However, within some domains, operations like 'create' and 'update' across different resources might be conceptually similar, but the structured categorization helps differentiate them. There is minor potential for confusion in operations like 'search' vs 'list' across tools, but overall, the separation is effective.
The tool names follow a highly consistent pattern: all are simple nouns (e.g., bookings, business, catalog) that correspond to Square API domains. Within each tool, operations use a consistent verb_noun format (e.g., create_booking, list_locations), with no mixing of conventions like camelCase or snake_case deviations. This uniformity makes the set predictable and easy to navigate.
With 12 tools, the server is well-scoped for a comprehensive Square API integration, covering key business areas like payments, orders, inventory, and more. Each tool represents a distinct domain, and the count is appropriate for the broad functionality offered, avoiding both excessive fragmentation and insufficient coverage. It aligns with typical MCP server ranges for such APIs.
The tool set provides extensive coverage of Square's API domains, including CRUD operations for resources like bookings, customers, orders, and payments, as well as lifecycle management for subscriptions and invoices. There are no obvious gaps; each domain includes create, retrieve, update, delete, and search/list operations, ensuring agents can handle full workflows without dead ends.