Square MCP Server

Square MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Square API Model Context Protocol Server.

What you get

A Model Context Protocol (MCP) server that provides access to Square API functionality.

What the assistant can call

Once Square is connected, these are the calls the assistant has available:

• Repository — square/square-mcp-server
• Variable — Required
• SQUARE_ACCESS_TOKEN — Yes
• SQUARE_ENVIRONMENT — No

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need 2 environment variables: SQUARE_ACCESS_TOKEN, SQUARE_ENVIRONMENT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Square's toolset — Repository, Variable, SQUARE_ACCESS_TOKEN and 1 more — is a fair guide to whether it matches your workflow.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the square mcp server does with a few real requests.