Skip to main content
Equated runs an MCP server at /mcp. It’s how an assistant turns “prepare month-end” into Equated actions — reading the review checklist, inspecting transactions, linking documents, and proposing changes you approve. Everything below is also available from Settings → AI Agents in the app, with the URL filled in for your workspace.

Connect your assistant

Let your agent handle setup. Paste Read https://app.equated.co/setup.md and follow it to connect Equated. into ChatGPT desktop Work mode, Claude Code, Codex CLI, Cursor, or Antigravity (desktop app or CLI). It registers the server, guides you through sign-in, and verifies the connection. Hosted chat apps use the account-level steps below.
1

Add a custom connector

Go to Customize → Connectors (or Settings → Connectors in desktop), then + → Add custom connector. On Team and Enterprise plans, an owner must first add Equated under Organization settings → Connectors.
2

Paste the server URL

3

Sign in

Click Connect and sign in to Equated. Leave advanced OAuth client credentials empty.
4

Turn it on in a session

In a chat or Claude Cowork session, open the + menu → Connectors and switch Equated on. One connector covers claude.ai, the desktop app, Claude Cowork, and mobile, so an agent running inside those apps can’t register it for you.
Replace the host with your own Equated workspace URL.
Setup is verified when list_accounts succeeds, including an empty account list. A saved configuration alone does not prove access. If tools are missing, check the URL, enabled state, authentication, and client logs before reloading or starting a new session. Client instructions checked September 9, 2026 against Claude Code, Claude connectors, ChatGPT desktop and CLI, ChatGPT web, Cursor, Antigravity CLI, and VS Code.

Authentication

Connecting through the app is keyless — your assistant signs in with OAuth and Equated issues it a token scoped to your organization. For a script or a server-side client that can’t complete a browser sign-in, pass an API token from Settings → API Tokens instead:
The same token works for the REST API. Browser session cookies are deliberately rejected on /mcp, so a signed-in tab can’t be used as credentials. See Authentication.

What your agent already knows

Your assistant doesn’t need to be taught your accounting model, and you don’t need to paste it a procedure. On connect the server hands it the rules it has to follow plus a map of every job it can do, so an ordinary sentence — “pay my open bills and link the transactions that paid them” — is enough. It looks up the steps for that job before it touches anything, which is why the steps can improve without you rewriting a prompt. From the first message it knows:
  • How a transaction moves. Imported, then categorized in your inbox, then confirmed and counted in your balances. A confirmed transaction has to be unconfirmed before it can be changed or deleted; while it’s still in the inbox you can delete it outright, and a deleted bank-synced transaction won’t come back on the next sync.
  • What it can categorize onto. Your chart of accounts is a mix of folders and the postable accounts inside them; only the latter are valid targets.
  • When to ask first. Your explicit request or standing instructions can authorize work. Otherwise the assistant shows the proposed change and asks before committing it. Any instruction to ask first still applies.
  • How splitting actually works. There’s no split tool. A split replaces a journal entry’s posting set with a balanced one, keeping the bank side untouched.
  • To work in batches. Confirming sixty transactions is one call, not sixty.

Available tools

Your assistant lists the current tools when it connects, so the set it sees is always the live one. Today that covers transactions, documents, bills and invoices, the chart of accounts, merchants, reconciliation and opening balances, financial reports (profit and loss, balance sheet, cash flow, general ledger), journal entries and their audit history, QuickBooks migration checks, and automation rules. For exact request and response shapes, see the API Reference — the MCP tools and the REST endpoints run on the same services.
See Action safety for the preview-and-execute contract, and Connect your AI for what you can hand off.