Square MCP

Square runs payments, point of sale, online checkout and the back office around them for small and mid sized merchants. Its MCP server wraps the Square API so an agent can read a merchant account and act on it without a developer writing integration code for each question. The exposed surface follows the API itself: payments and refunds, orders with their line items and fulfillment state, the catalog of items, variations, modifiers and categories with create and update support, inventory counts and adjustments per location, customer records, invoices, bookings for appointment based businesses, locations, team members, and payout records. Every call is bounded by the OAuth scopes granted on the access token, so a strictly read-only integration is straightforward to set up. Most use is operational rather than analytical. Reconcile a day of payments against deposits, bulk edit prices across a catalog, trace the order behind a disputed charge, check stock at one location before promising it to a customer, or pull the invoices a client has not settled. Square provides sandbox credentials, and anything that writes to a catalog, inventory or invoice should be tested there before it points at a live merchant.