Is this an official Square MCP server?

No. It is Memtro's MCP server with Memtro's Square connector behind it: the connector reads Square through its API with the credentials you connect on Dashboard → Connections, and Square publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Square?

Not yet. Today every Square tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Finance and commerce

Square MCP server

Square in any MCP client, through Memtro: Square does not publish this server. Memtro's Square connector reads Square through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only point-of-sale and online payments from Square: payments and refunds, orders with line items, customers, payouts to the bank, disputes, and the catalog with prices and stock counts.

Reads

square_paymentsPayments (default) or refunds taken through Square, newest first: amount, tip, status, card brand and last four, customer and order ids, location…
square_ordersOrders with their line items, totals, tenders and fulfilment state, newest first, across all active locations unless location_ids is given.
square_customersFind customers by email (fuzzy: a full address or a domain), phone number, or reference id; or list the most recently created…
square_payoutsPayouts from Square to the bank account, newest first: amount, status (SENT, PAID, FAILED), type, arrival date, fees, location.
square_catalogCatalog items with their variations, SKUs and prices: search by text (name, description, SKU) or browse.
square_disputesChargebacks and inquiries raised against payments: amount, reason, state (EVIDENCE_REQUIRED, PROCESSING, WON, LOST, ACCEPTED…), card brand…

Connect it

First connect Square on Dashboard → Connections, then add Memtro to your client once. The Square tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Square connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› How much did the Soho shop take yesterday?
› Show me refunds over £100 this month
› Which orders did jane@example.com place?
› Has the payout for Monday arrived?
› Which items are low on stock?
› Are there any open disputes?

Questions

Is this an official Square MCP server?: No. It is Memtro's MCP server with Memtro's Square connector behind it: the connector reads Square through its API with the credentials you connect on Dashboard → Connections, and Square publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Square?: Not yet. Today every Square tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.