get_service_info
Get information about a Square API service. Call me before trying to get type info
LABSCO SUMMARY
One entry point instead of a tool per endpoint.
The API is exposed as a service plus a method, so a catalog call and a labor call take the same shape and nothing new appears when Square adds an endpoint. What it asks in return is an order: service info, then type info, then the request — stated in the tool descriptions rather than left to be discovered.
What it is
Three tools that front the whole Square API: one describes a service, one returns the type information for a method, and one performs the request.
What you get
- A single request tool covering Square's services, from catalog, inventory and locations to invoices, bookings, labor, disputes, gift cards and customers
- Type information for a method, which the request tool expects to have been fetched first
- A service-level description to read before the type lookup
Requirements
- Hosted: nothing to install — sign in with your Square account.
- On your own computer:
npx, a Square access token inACCESS_TOKEN, andSANDBOX—truefor Sandbox test data, which Square recommends trying first.
Setup effort
One command plus a key — npx square-mcp-server start, then supply credentials
USE CASES
01
Reading the state of your catalog into a conversation
Ask what the catalog service covers, get the type information for the method you want, then make the request — the order the tools themselves insist on.
02
Raising an invoice from what you just agreed
Fetch the type information for the invoices method so the request body is right the first time, then issue the call against the account the token belongs to.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_type_info
Get type information for a Square API method. You must call this before calling the make_api_request tool.
make_api_request
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.
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected. The three gateway tools reach Square's whole API, 37 services. Set DISALLOW_WRITES=true to keep make_api_request read-only; without it the tool can do anything your access token allows.
Requires
- npx on PATH
- ACCESS_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
npx
TERMINAL
npx square-mcp-server startHosted endpoint
ENDPOINT URL
https://mcp.squareup.com/mcpConnect a client to this instead of installing anything. Then sign in with your Square account. It reaches only your live Square data; for Sandbox test data, use the local setup with SANDBOX set to true. Square accepts only MCP clients on its approved list; if yours can't connect, ask for it to be added in the Square developer forum. Taken from this project's own documentation.
MCP Clients
Claude Desktop — remote
CLAUDE DESKTOP — REMOTE · JSON
{
"mcpServers": {
"mcp_square_api": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.squareup.com/mcp"
]
}
}
}Claude Desktop — local
CLAUDE DESKTOP — LOCAL · JSON
{
"mcpServers": {
"mcp_square_api": {
"command": "npx",
"args": [
"square-mcp-server",
"start"
],
"env": {
"ACCESS_TOKEN": "<YOUR_ACCESS_TOKEN>",
"SANDBOX": "true"
}
}
}
}Goose
The install command automatically updates your Goose configuration:
GOOSE · TERMINAL
npx square-mcp-server install
