Square MCP Server
# 🚨 DEPRECATED: Square MCP Server (Old Version)
> **⚠️ This repository is no longer maintained.**
> **Official development has moved to [square/square-mcp-server](https://github.com/square/square-mcp-server).**
> Please use the new repository for the latest, officially supported Square MCP Server.
---
## Archived Information (for reference)
A Model Context Protocol (MCP) server that provides access to Square API functionality.
## Setup
1. Install dependencies:
```bash
uv sync
```
2. Set environment variables:
```bash
# Required
export SQUARE_ACCESS_TOKEN=your_access_token_here
# Optional - defaults to 'sandbox' if not set
export SQUARE_ENVIRONMENT=sandbox # or 'production' for production environment
```
3. Run the server:
```bash
uv pip install .
square-mcp
```
Or for development:
```bash
source .venv/bin/activate
mcp dev src/square_mcp/server.py
```
## Environment Variables
| Variable | Required | Default | Description |
|----------|----------|---------|-------------|
| `SQUARE_ACCESS_TOKEN` | Yes | - | Your Square API access token |
| `SQUARE_ENVIRONMENT` | No | `sandbox` | Square API environment (`sandbox` or `production`) |
---
### 🔗 Migrate to the new server:
- Repository: [square/square-mcp-server](https://github.com/square/square-mcp-server)
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.