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
A Square ACCESS_TOKEN and a SANDBOX value, plus npx on your PATH.
Setup effort
One command plus a key — npx square-mcp-server start, then supply credentials