Connect your AI agent to your books
Setttle speaks Model Context Protocol over streamable HTTP. Your assistant reads balances and uses the same permissions, accounting commands, review states, and audit trail as the web app.
One URL, the same books
Point any MCP client at the endpoint below. Calls run against the live ledger, not a copy, so a balance your agent reports is the balance in your books.
Streamable HTTP
https://api.setttle.ca/mcpTwo ways to connect
Owners and collaborators sign in with OAuth. Scripts and CI use a token scoped to a single company.
- OAuth
For people. Add Setttle as a connector and sign in through your browser, then choose what the connection may do on the consent screen. The connection is account-wide, so you can switch companies with
use_entity.Works with Claude Desktop, ChatGPT connectors, Claude Code, and Cursor. Clients register themselves; there’s nothing to set up first.
- sett_ API token
For developers and automation. Mint a token in Settings → API tokens; the plaintext is shown exactly once. A token is pinned to one company and never sees another.
Send it as
Authorization: Bearer sett_…. Revoke it from the same page and the next call fails.
Connect a client
Most clients open the Setttle sign-in and consent screen on first use.
- Claude Desktop & ChatGPT
Add a connector or integration and paste the endpoint URL. Your browser opens the Setttle sign-in, then the consent screen where you pick a permission tier.
- Claude Code
Register the server, then run /mcp inside Claude Code to authenticate.
shell
claude mcp add --transport http setttle https://api.setttle.ca/mcp- Cursor
Settings → MCP → Add server → type HTTP, then the endpoint URL. Cursor opens the same OAuth flow the first time a tool runs.
What an agent can do
Read access is available at every tier. Drafting and posting depend on the permission granted at consent. A model suggestion is a draft; an explicit posting command must pass the same accounting rules as the web app.
Read, always
- Account balances and trial balances
- Journal entries, invoices, bills, and receipts
- Bank transactions and reconciliation status
- Reports and tax schedules for filing review
- CRA and registry deadlines, with GST/HST return lines from the books
- The company profile, its documents, and a corporation’s registers
- What still needs a decision, and why
Change, with permission
- Draft and post balanced journal entries
- Create invoices and vendor bills
- Record invoice and bill payments
- Mark deadlines filed or paid, and link the bank payment that paid them
- Add receipts, and attach documents to records or the Company page
- Void an unpaid manual invoice, preserving history
- Switch companies with use_entity, within the connection's scope
Agents do not get a parallel accounting model or a shortcut around review. When the tier is read-only, nothing is written. When it is not, a post still has to satisfy the same rules as the web app.
Deadlines and the company record
The same deadlines, documents and registers as the Deadlines and Company pages. Agents record what the owner confirms; nothing here files with the CRA or a registry.
list_deadlines- CRA deadlines and registry annual returns, earliest first, each with its rule, source, status and what the owner recorded. GST/HST returns carry lines 101, 105, 108 and 109 from the books (and 110 for annual filers), whether the books are caught up, and a posted payment that matches. Read access.
list_deadline_payments- Posted bank payments that could have paid a deadline, likely CRA payments first, with what each has left to assign. Read access.
set_deadline_status- Records the date a deadline was filed or paid, once the owner confirms it. Write access.
link_deadline_payment- Links one bank payment to one or more deadlines, each with its share, and marks them paid. Write access.
get_company_registers- A corporation’s directors and officers, share classes, each shareholder’s holding and percentage on any date, and every share issuance. Read access with company access.
get_company_profile- Registration details, CRA program accounts, and, with company access, the documents register. Read access.
attach_document- With kind company_document, files a new document in the Company page’s register or adds a file to one. list_documents and remove_document take the same target. Write access.
Attribution, review, and revocation
- Every action is attributed
- Entries created through an agent record the actor as an agent, with a timestamp and source. The audit history looks the same whether a person or an agent made the change.
- Drafts stay drafts
- A suggestion from a model is not a posting. Drafts wait for review, and ambiguity is never silently resolved. Explicit posting tools are available only at a permission tier that allows them.
- The ledger still has the final say
- Posted entries cannot be deleted individually, corrections preserve history, and every entry must balance in the company's base currency. A tool call that breaks a rule fails loudly instead of guessing.
- Revoking is immediate
Disconnect from Settings → Connections (or revoke a token from Settings → API tokens). The next tool call is rejected, with no grace period.
Questions, answered plainly
Something else? hi@setttle.ca
Only with a permission tier that allows changes. Read-only connections cannot write. Drafts wait for review; an explicit posting command must pass the same authorization and balance checks as a web action.
No. API tokens are pinned to one company. An OAuth connection can switch only among companies the signed-in person is authorized to access.
Revoke its connection or API token in Settings. The next tool call is rejected.
Give your assistant the real books
Every plan includes MCP access. Permissions and accounting rules still apply to every tool call.