NewCost control: a token allowance a month for each model choice — when one runs out, the cheaper one answers.See how it works
memtro

Square + Memtro

Takings, orders and customers from your Square locations.

Connect Square with a read-only access token and ask about yesterday's takings, what sold, who bought it, which payouts landed and which payments are disputed. Memtro summarises each day's payments per location and keeps order history in the graph.

What you can do with Square in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Square tool, reads what it needs, and answers with the source cited.

01

Daily takings

Every morning the graph holds a per-location summary of yesterday's completed payments, tips and refunds, so 'how did Tuesday go?' is answered without opening the Square dashboard.

02

Chargeback triage

A new dispute becomes a memory with its amount, reason, card brand and evidence deadline, and the disputed payment can be pulled with square_payments to see the customer and order.

  • Payments and refunds with card brand, tip and receipt link
  • Orders with line items, tenders and fulfilment state
  • Customer lookup by email, phone or reference id
  • Payouts to the bank and the charges behind them
  • Disputes with reasons and evidence deadlines
  • Catalog items, prices and stock counts

Ask it like this

Questions people ask once Square is connected. In agent mode each one also checks the other systems that know about the same people, companies or identifiers.

  • ›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?

Where it fits

Teams that get the most from Square in Memtro, with the rest of their stack attached.

Better together

A record in Square is rarely the whole story. Connect the systems that hold the rest and the agent cross-references them by default, then remembers what it learned so the next question starts further along.

Also in Finance and commerce

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

How to connect

  1. 01In developer.squareup.com open your application and copy the Production access token (read permissions only)
  2. 02Paste it into Memtro; add the sandbox base URL if you are testing against a sandbox account
  3. 03Memtro checks the merchant and lists your locations
Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Square tools are the same everywhere.

Set it up as an MCP server →Clients and agents →

Questions

Can Memtro change anything in Square?
Not yet. Today every Square tool reads, searches or lists. When the connector gains actions, each is marked, granted by name per team and used only when a person asks for exactly that, so nothing is created, sent, updated or deleted until you say so.
Who can use a Square connection?
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Does Memtro store my Square data?
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded. An hourly sync anchors recently changed Square records into memory as entities.
How do I connect Square?
API key. In developer.squareup.com open your application and copy the Production access token (read permissions only).

Connect Square in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.