Claude + Sage Accounting: What the Integration Can (and Can't) Do in 2026
No — there’s no official Claude Sage connector. Sage isn’t in Anthropic’s connectors directory, and Sage ships no first-party MCP server. The good news: Sage Accounting has a genuinely self-serve OAuth API, so you can connect Claude to it with your own credentials through a community MCP server. One scoping note up front, because “Sage” is a whole product family: this is about Sage Accounting (Sage Business Cloud Accounting) specifically. Sage 50, Sage Intacct, and Sage 200 have separate APIs and different gating — don’t assume what’s true here applies to them.
Here’s exactly what’s possible, the token quirk you have to design around, where the limits bite, and what to use if you want Sage work that runs on its own.
The self-serve OAuth API (Sage Accounting only)
Sage Accounting exposes a well-documented REST API, currently v3.1, with self-serve developer signup at developer.sage.com (there’s also the legacy self-service portal at developerselfservice.sageone.com). It uses standard three-legged OAuth 2.0 — you register to get a client ID and secret plus a redirect URI, then the merchant authorizes access. The API covers businesses, invoices, contacts, ledgers, and the rest of the accounting surface.
The catch worth knowing before you build:
- Access tokens expire every ~5 minutes, and
- refresh tokens rotate on every use.
That means token handling has to be automated and careful — an integration that doesn’t refresh cleanly will break within minutes. It’s not a dealbreaker; it’s a design requirement.
For Claude specifically, with no directory connector and no vendor MCP, a connection means running a community MCP server that wraps the Sage Accounting API with your OAuth credentials. The notable project is larrygmaguire/hash-sage-accounting-mcp (LobeHub-listed; MCP over the Sage Accounting API for Claude Code, OAuth creds and tokens in .env, local). It uses your own Sage OAuth token — vet it before handing over credentials.
Separately, Sage is pushing an in-product AI assistant (“Sage Copilot”), but that lives inside Sage and is not the developer API — it doesn’t connect to Claude.
How to set it up
This is a BYO-key, custom-MCP flow:
- Register a developer application at developer.sage.com to get OAuth 2.0 client credentials and set your redirect URI.
- Complete the OAuth flow so the merchant authorizes access to their Sage Accounting business.
- Run a community MCP server (e.g.
larrygmaguire/hash-sage-accounting-mcp) with your credentials in.env, making sure it handles the ~5-minute token refresh and rotating refresh tokens automatically. - Add it to Claude Desktop or Claude Code as a custom MCP connector — remote custom connectors on claude.ai require a paid plan.
- In a chat, ask Claude to pull invoices, contacts, or ledger data; it’ll query the Sage Accounting API through the server.
Useful for querying your books inside a conversation. It’s a build, not a toggle.
The limits that actually matter
Even with a working MCP server, the shape is “an accountant you query,” not “an agent that keeps your books.” Three limits define it:
- No triggers, no monitoring. MCP tools only run inside a conversation you start. There’s no “when an invoice goes 30 days overdue, send a reminder” or “when a contact is added, tag it.” Nothing fires on a Sage event — you have to be there, prompting.
- Conversation-only. Claude answers when you ask; it doesn’t watch your account for overdue invoices or new transactions and act on them. Close the chat and nothing continues.
- Laptop-bound for anything scheduled. The nearest thing to “running on its own” is Claude Cowork’s scheduled tasks, which fire on a fixed clock, not on inbox events. Not an always-on bookkeeping agent.
So Claude is great for “summarize this month’s Sage invoices” and not built for “chase every overdue invoice as it ages.”
If you want Sage work that runs on its own: Carly
The moment you want something to happen in your books without you in the chat — chase an overdue invoice, send a payment reminder on a schedule, flag unusual activity weekly — you’ve crossed past what Claude’s MCP setup is for.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers, not just answer in a chat:
- Fires on events and schedules, 24/7, in the cloud — an overdue-invoice reminder, a weekly invoice summary, a monthly recap; your laptop doesn’t need to be awake.
- Actually sends and updates — drafts and sends email (Gmail and Outlook) with attachments, files and labels, manages tasks, updates your CRM, and records meetings.
- Connects to Sage Accounting via your own API key — Sage has no native Carly page, so you paste your Sage OAuth credentials on carlyassistant.com/integrations and Carly does whatever the Sage Accounting API allows — including handling the fussy 5-minute token refresh for you. It also has 200+ native integrations for the rest of your stack.
- Builds the workflow for you — describe “follow up on overdue invoices and send me a weekly summary” in plain English; Carly interviews you, then builds it with you. No prompt engineering.
AI agents start at $35/month, and steps in a workflow that don’t use AI run free and unlimited. Carly connects to 200+ tools across 40+ categories — see integrations.
Claude vs Carly for Sage
| Claude (community MCP) | Carly | |
|---|---|---|
| Read invoices & contacts | Yes (build required) | Yes |
| Uses your own Sage token | Yes | Yes |
| Handles 5-min token refresh | You build it | Yes |
| Acts on triggers / events | No | Yes |
| Chases overdue invoices on its own | No | Yes |
| Works while laptop is closed | No | Yes (cloud) |
| Sends reminders / email | No (Gmail draft-only) | Yes (Gmail + Outlook) |
| Pricing | Pro $20 / Max $100–$200 | AI agents from $35/mo |
Claude’s route is a Sage Accounting lookup inside a chat, if you build the connection. Carly is a colleague that keeps the books moving on its own.
Frequently Asked Questions
Does Claude work with Sage?
Not through an official connector — Sage isn’t in Anthropic’s directory and there’s no Sage-built MCP server. But Sage Accounting (Business Cloud Accounting, v3.1) has a self-serve OAuth API at developer.sage.com, so a community MCP server like larrygmaguire/hash-sage-accounting-mcp can connect Claude to your books with your own OAuth token. Note this covers Sage Accounting only — Sage 50, Intacct, and 200 have separate APIs.
How do I connect Claude to Sage Accounting?
Register a developer app at developer.sage.com for OAuth 2.0 credentials, complete the auth flow, run a community MCP server with your credentials, and add it to Claude Desktop or Claude Code as a custom MCP connector (paid plan for remote connectors). Crucially, the server must handle the token lifecycle: access tokens expire about every 5 minutes and refresh tokens rotate on every use.
Which Sage products does this cover?
Only Sage Accounting / Sage Business Cloud Accounting. Other Sage products — Sage 50, Sage Intacct, Sage 200 — have their own separate APIs and gating, so don’t assume the self-serve OAuth flow here applies to them.
Can Claude chase overdue Sage invoices automatically?
No. Claude’s MCP tools only run inside a conversation you start — no schedules, no event triggers. For automatic invoice reminders or a weekly summary, use an agent platform like Carly, which fires on schedules and events in the cloud and can send the email itself. You connect Sage Accounting to Carly with your own API key, and Carly handles the 5-minute token refresh for you.
More: Claude connectors · Claude + QuickBooks · Claude + Xero · Claude + FreshBooks · Can Claude send emails · Claude vs Carly
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
