# Connect an agent to one company's books with the right access

> Connect an agent to one company's books with the right access: 2 companies fully do it, 8 with a limit, 13 carry the tag. Every listing in Accounting & invoicing with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/accounting.connect-books/
- Markdown: https://www.anchorterminal.com/niches/accounting.connect-books/index.md (~1,550 tokens)
- Slim: https://www.anchorterminal.com/niches/accounting.connect-books/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/accounting.connect-books/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 2 | 8 | 13 | 17 | 12 |

## What counts as done

The agent reaches the real company (not only a demo) through documented setup a single business can complete itself, with a read-only or object-limited grant that the tool enforces, and a second user can connect without displacing the first.

Measured, for our own tests: setup in under 30 minutes without an app review.

How agents ask for it: connect Claude to my QuickBooks; give the agent read-only access to Xero; let my bookkeeper and me both use it; make sure it cannot delete anything

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Pennylane (Pennylane SAS)**: An admin on Essentiel or above makes a company token in Settings > Connectivity > Developers with :readonly or :all scopes per resource and an expiry; a company can hold several tokens, one per user or integration. The hosted MCP is read-only.
- **Zoho Books (Zoho Corporation Private Limited)**: A Self Client serves a business connecting its own organisation with no review, and scopes are per module and per action (ZohoBooks.invoices.READ), so a read-only grant is enforced. Each user authorises with their own tokens.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Apideck Accounting API + MCP (Apideck Inc. and Apideck NV/BV)**: Built for SaaS products reaching customers; a business can connect its own ledger through Vault on a 30-day trial, then $599 a month. MCP --scope read is enforced since 0.19.0 (issue 62), but the REST API key itself has no read-only grant.
- **FreeAgent API (FreeAgent Central Limited)**: Any developer registers an app on the dashboard with no review and each user authorises their own token. There are no OAuth scopes; the only limit is authorising as a user with a lower permission level (Invoices, Bills, Banking), which is not read-only.
- **FreshBooks API (2NDSITE Inc.)**: OAuth scopes are per object and per read or write (user:invoices:read), so a read-only grant is enforced. Only one refresh token lives per user per app, so concurrent refreshes break, and whether a private app needs no review was not found.
- **Invoice Ninja API (Invoice Ninja LLC)**: A business creates an API token in its own settings (Settings > Account Management > Integrations), on hosted Pro or self-hosted, with no review. No read-only or per-object token is documented.
- **Merge Accounting API (Merge API, Inc.)**: Aimed at SaaS products linking customers through Merge Link; a business could link its own ledger (the listing's pricing notes give 3 free linked accounts). linked-account-scopes sets model and field permissions per linked account.
- **Odoo External API (Odoo SA)**: A user makes an API key in Preferences with a set lifetime, and the docs advise a dedicated bot user with minimum rights, which Odoo's access rights enforce. Odoo Online excludes the external API on One App Free and Standard; the Custom plan is needed.
- **Puzzle API and MCP (Puzzle Financial Inc.)**: The hosted MCP signs in by OAuth, lets the user pick companies, is read-only by default with write as an opt-in beta, and can be revoked. That rests on the product page; no tool list or scope enforcement test is published.
- **Xero API + MCP (Xero Limited)**: Custom Connections give one organisation its own client, and granular .read scopes are enforced by the API. Custom Connections aren't offered in Canada (acc-31) and post-29 April connections can't authenticate with the MCP's hard-coded scopes (acc-26); both open, and the MCP still lists write tools.

- not this job: Codat (Codat Limited): Sold to lenders and fintechs under an order form with no self-serve signup; API keys have no scopes or read-only mode and reach every connected company.
- not this job: QuickBooks Online API + MCP (Intuit Inc.): A business must register an Intuit OAuth app like a SaaS vendor (acc-38, no personal token), and one accounting scope covers the whole ledger including delete (acc-05). The MCP's DISABLE_WRITE flags hide tools locally; the token stays full access.
- not this job: rotki MCP server (Rotki Solutions GmbH): Connects to the user's local rotki app, not to a company's ledger; there is no multi-user model.
- not this job: Rutter Accounting API (Rutter): Built for lenders and fintech products: production is a sales quote, each connection's access_token rides in the query string, and no read-only scope is documented.

## What stops agents finishing

- only a public OAuth app works, with no personal token for a single business
- the connector type the MCP needs is not offered in the organisation's country
- one scope covers the whole ledger, including delete

## Around it

After: accounting.read-reports, accounting.raise-invoice, accounting.reconcile-bank.

## Where this comes from

Weight 17 of 100 in Accounting & invoicing: 12 of 69 use-case citations across 60 accounts, scaled to 100

As data: https://www.anchorterminal.com/api/v1/use-cases/accounting.connect-books.json, or the MCP tool get_use_case with id accounting.connect-books. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
