Sage Intacct MCP Server (AI Gateway): what it reads, what access it needs, how to connect it
Sage hosts a read-only Intacct MCP Server, part of its AI Gateway. Users sign in with OAuth and see what their Intacct role allows. Verified 21 Oct 2026.
- Official remote MCP · read-only
- Hosting
- Remote, hosted by Sage at https://mcp.intacct.com/mcp. There is no local server or open-source repo.
- Auth
- OAuth sign-in. The server's published sign-in settings require a pre-registered client ID and secret and offer a refresh token. Access follows the Intacct role of the user who signs in.
- Read / write
- Read-only. Creating or updating records goes through Sage's separate REST API.
- Works with
- Claude and other MCP clients that accept your own OAuth client ID. Rand Group also names ChatGPT as compatible, but Sage doesn't document connecting it. No Claude directory listing as of 21 Oct 2026.
- Plan requirement
- A Sage Intacct subscription. Sage's pricing page for the AI Gateway wasn't publicly reachable on 21 Oct 2026; the dataset records that Sage asks you to request pricing.
- Last changed
- 2026-05-28: Sage announced general availability with 2026 Release 2
- Verification
- Verified 21 Oct 2026 by theFinanceStack · confidence: medium
What can an agent do with Sage Intacct through MCP?
It can read Sage Intacct data across 6 areas (general ledger, payables, receivables, cash management, purchasing and order entry) that the signed-in user's role allows. It cannot post, change or delete anything.
Sage ships the MCP Server as one half of its Intacct AI Gateway, released in 2026 Release 2 (release notes dated 8 May 2026) and announced as generally available on 28 May 2026.
Where it runs
| Part | Reads or writes |
|---|---|
| MCP Server | Baker Tilly, summarising Sage's documentation, says it "provides read access only". |
| REST API | Can write. |
Good to know
- Sage keeps its tool list and field coverage in its developer portal, which wasn't publicly reachable on 21 Oct 2026, so this page gives no tool count.
Can
- Read general ledger, accounts payable, accounts receivable, cash management, purchasing and order entry data, per Baker Tilly's summary of Sage's docs
- Explore objects, fields and how they relate, per Baker Tilly
- Return only what the signed-in Intacct user's role is permitted to retrieve
- Answer questions and build summaries in Claude, ChatGPT or another MCP client, which Rand Group names as compatible platforms
Cannot
- Post transactions, change records or alter balances: the MCP Server is read-only, per Baker Tilly and Rand Group
- Create or update records: Sage routes writes through its separate REST API, per Baker Tilly
- Explain how your company uses its dimensions or flag inconsistent dimension tagging, per Baker Tilly
- Reach data the signed-in user's role cannot see in Sage Intacct
What access does it get?
It gets whatever the Sage Intacct user who signs in can read under their role. The server's sign-in settings list one scope, offline_access, which only keeps the connection signed in, so the Intacct role is the control.
| Where | Scopes and permissions (as documented) | Admin requirement |
|---|---|---|
| Intacct MCP Server (remote, AI Gateway) | offline_access is the only scope in the server's published OAuth settings; it issues a refresh token so the client stays signed in. Data access is set by Sage Intacct role permissions. Baker Tilly says the connection is "only as constrained as the identity behind it". | Sage doesn't publish who can register the OAuth client in pages reachable on 21 Oct 2026; its setup guide covers it. An Intacct administrator sets up the role. Claude Team/Enterprise: an Owner adds the custom connector and may restrict Claude Code MCP servers. |
How do I connect it?
Get an OAuth client ID and secret for your AI client as Sage's setup guide describes, add https://mcp.intacct.com/mcp in the client with those details, then sign in to Sage Intacct. Each user signs in, so access follows their own role.
- In Sage Intacct, have an administrator set up a role with read permissions limited to the modules and entities the AI should see, and give it to the users who will connect.
- Get an OAuth client ID and secret for Claude, following Sage's MCP setup and connection guide on developer.sage.com. Register https://claude.ai/api/mcp/auth_callback as a redirect URI on that client; Claude's connector authentication docs give this address.
- Free, Pro or Max: open Customize › Connectors › Add custom connector, enter https://mcp.intacct.com/mcp, and put the client ID and secret under Advanced settings. Team/Enterprise: an Owner does this in Organization settings › Connectors (Add, then Custom). On Enterprise, a member whose custom role includes managing the organization's libraries can also add it.
- Each user then opens Customize › Connectors, selects Connect on the Sage Intacct connector, and signs in to Sage Intacct.
Sage Intacct isn't in Claude's connector directory as of 21 Oct 2026. The server offers no automatic client registration, so Claude can't connect without a client ID. Sage's guide wasn't publicly reachable on 21 Oct 2026; confirm how Sage issues the client before rollout. Claude can't edit a connector's OAuth client ID or secret after it's added: to rotate the Sage client secret, remove the connector, add it again with the new details, and have members reconnect.
What should a finance team watch for?
The main watch-points are how broad the signed-in user's Intacct role is, who holds the OAuth client secret and refresh tokens, and that Sage's detailed limits and pricing weren't public on 21 Oct 2026.
- The role is the only boundary: Baker Tilly warns that reusing a convenient existing role, such as an admin role, is a common way pilots exceed approved access. Build a dedicated role with the minimum modules and entities.
- The OAuth client secret is a credential. Keep it in the AI client's secret storage or a password manager and out of shared files and repositories.
- The offline_access scope gives the client a refresh token that keeps it signed in. Sage's published sign-in settings list a token revocation endpoint, so connections can be revoked. When someone leaves or a pilot ends, revoke the connection or deactivate the Intacct user, and ask Sage how long refresh tokens last and whether they rotate.
- Never include access tokens or other credentials in AI prompts, as Rand Group advises.
- Sage doesn't publish rate limits, row caps, pricing or a tool list in pages reachable on 21 Oct 2026, or whether connecting uses a licensed Intacct user seat. Ask Sage before a rollout.
- Sage doesn't document whether one connection can reach more than one Intacct company. Access follows the single Intacct user who signs in, so a firm serving several clients should plan for a separate user, role and connection per client company and confirm this with Sage.
- Availability is regional: the 2026 R2 release notes list the United States, United Kingdom, Canada, Australia, South Africa and Singapore.
- Once data reaches Claude or ChatGPT, that provider's terms govern it. Baker Tilly says prompts and retrieved data "may be retained by that provider"; check Sage's and the AI provider's terms on retention and training.
- Memos and descriptions are free text, and the agent reads them. The server can't write. If the same chat also has write-capable tools for other systems, an instruction planted in a memo could get those tools to post or pay, so keep human approval on them.
- Data gaps come back as they are: Baker Tilly notes inconsistent dimension tagging isn't flagged. Check figures against Intacct reports before they go into a close or board pack.
How could finance teams and accounting firms use it?
The MCP Server only reads, so it suits questions, analysis and reporting on Intacct data. A person still makes every posting in Sage Intacct.
Inside a company
- Ask which customers have invoices more than 30 days past due and get a short list to review with the AR lead.
- Draft a first pass of month-end variance commentary from GL balances for a controller to check.
- Summarise open purchase orders and AP due this week to prepare a cash discussion.
- Pull order entry and receivables figures together to answer a sales leader's question.
At an accounting firm
- Answer a client CFO's question in a meeting from their Intacct data, under a read-only role limited to that client's entities.
- Prepare a draft management pack narrative from a client's GL, then review it against Intacct reports.
- Review a client's AP aging and open bills before a cash-planning call.
- Pull a client's trial balance by entity to prepare year-end questions.
Any change to the ledger stays with a person in Sage Intacct, through its own screens or an approved REST API workflow.
Want Sage Intacct connected to Claude for your team?
We configure scoped connections and a review step before anything changes your books. Fixed fee.
Book a 30-minute setup callChange log
| Date | Change | Source |
|---|---|---|
| 2026-10-21 | Re-checked: the live server signs users in with OAuth, needs a pre-registered client and lists only the offline_access scope | mcp.intacct.com/.well-known/oauth-authorization-server |
| 2026-05-28 | Sage announced general availability of the AI Gateway with 2026 R2 | www.sage.com/en-us/news/press-releases/2026/05/sage-intacct- |
| 2026-05-08 | 2026 Release 2 notes list the Sage Intacct AI Gateway (REST API and MCP Server) in six regions | www.intacct.com/ia/docs/en_US/releasenotes/2026/2026_Release |
FAQ
Is this official?
Yes. Sage builds and hosts the Intacct MCP Server at mcp.intacct.com as part of its AI Gateway, and lists it in its 2026 R2 release notes.
Is it free?
Sage's AI Gateway pricing wasn't publicly reachable on 21 Oct 2026; ask Sage. You also need a Sage Intacct subscription and an AI client that supports remote MCP servers with your own OAuth client.
Does it change data in Sage Intacct?
No. The MCP Server is read-only, per Baker Tilly and Rand Group. Creating or updating records needs Sage's separate REST API.
Is my data used to train models?
Sage's statements on this weren't publicly reachable on 21 Oct 2026. Check Sage's terms and your AI provider's terms, which govern data once it reaches the AI client.
Can my accountant use it on my behalf?
Sage doesn't document this. Access follows the Intacct user who signs in and their role, so ask your Intacct administrator how an outside adviser's access would be set up and whether it uses a licensed user seat.
Sources
- Sage Intacct MCP Server: published OAuth sign-in settings
- Sage Intacct MCP Server: protected resource settings
- Sage developer portal: Intacct MCP setup and connection guide (not publicly reachable on 21 Oct 2026)
- Sage Intacct 2026 Release 2 notes (8 May 2026)
- Sage Intacct AI Gateway product page (not publicly reachable on 21 Oct 2026)
- Sage press release, 28 May 2026 (not publicly reachable on 21 Oct 2026)
- Baker Tilly: Sage Intacct MCP Server for finance leaders (1 Sep 2026)
- Rand Group: Sage Intacct AI Gateway explainer (3 Aug 2026)
- Claude docs: add a connector that isn't in the directory
- Claude docs: authentication for connectors (callback address https://claude.ai/api/mcp/auth_callback)
- Claude Code docs: MCP servers and OAuth client options (redirect http://localhost:8080/callback when --callback-port is 8080)
Verified by theFinanceStack, 21 Oct 2026. Vendor list on the CFO Software Market Map courtesy of Jason Staats; AI connectivity data by theFinanceStack. Not tax, compliance or financial advice.