Square MCP Server

Square API integration for AI assistants to manage payments and business data.

Data last scanned today · Reviewed yesterday

59 1 dangerous tool3 tools★ 101TypeScriptApache-2.0

Overview

This MCP server provides a bridge between AI assistants and the Square Connect API. It supports interacting with various business endpoints, allowing users to perform operations directly through their AI agent workflow by providing a Square access token. The server supports both sandbox and production environments, enabling developers to test workflows before going live. It can be integrated into environments like Goose or Claude Desktop using provided CLI installation tools.

Our verdict

The Square MCP Server receives a security score of 19/100, resulting in a high-risk classification. This is primarily due to the lack of built-in authentication, which exposes the server to anyone with access to the configuration files. Additionally, the project is community-maintained rather than official. Users are strongly advised to utilize the hosted remote MCP server instead, as it supports OAuth authentication and provides a more secure way to connect your Square account.

Supports both Square sandbox and production environments
Offers explicit read-only mode via DISALLOW_WRITES configuration
Includes documentation for integration with Goose and Claude Desktop
Small footprint with only 12 direct dependencies

High security risk due to missing authentication mechanisms
Requires manual handling of sensitive Square access tokens
Maintained by the community instead of the official vendor

Setup

Claude Desktop

{
  "mcpServers": {
    "square-mcp-server": {
      "args": [
        "-y",
        "square-mcp-server"
      ],
      "command": "npx"
    }
  }
}

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Some servers require API keys or tokens as environment variables — check the project's README and add an "env" object if needed.

No read-only mode — running this grants full read/write access.
No built-in authentication — anyone with access to this config can invoke every tool it exposes.

Tools

Tool	Description	Risk
get_service_info	Discover methods available for a service	low
get_type_info	Get detailed parameter requirements	low
make_api_request	Execute API calls to Square	high

Compatibility

Client	Local	Docker	Remote	Read-only
Claude Desktop
Cursor
VS Code
Windsurf
ChatGPT

Frequently asked questions

›What is the difference between the local and remote MCP server options?

The remote server at https://mcp.squareup.com/sse supports OAuth, allowing you to log in with your Square account directly without manual token management. The local server requires you to manually provide a Square access token via environment variables.

›How can I restrict the MCP server to read-only access?

You can restrict the server to read-only operations by setting the DISALLOW_WRITES environment variable to true.

›Can I test the Square MCP server without using live data?

Yes, you can enable the Square sandbox environment by setting the SANDBOX environment variable to true.

›How do I discover available tools and parameter requirements?

You can use the get_service_info tool to discover available methods for a service and the get_type_info tool to retrieve detailed parameter requirements for those methods.

›Is it possible to specify which Square API version to use?

Yes, you can define a specific API version by setting the SQUARE_VERSION environment variable.