MCP server guide · reviewed by Pravin Bansal, Co-founder & CEO on November 19, 2026

Sage Intacct MCP server

Yes. As of November 2026, Sage Intacct’s official MCP server is the MCP Server in the Sage Intacct AI Gateway, introduced in the 2026 R2 release notes (May 8, 2026) and described by Sage on May 28, 2026 as generally available in the US, UK, Canada, Australia and South Africa. It is built on the Sage Intacct REST API and works within each company’s roles and permissions; Sage partners report that it is read-only and needs an AI Gateway subscription plus a Web Services Developer license, which we have not confirmed on a Sage page. To post bills, invoices or journal entries under your own approval rules, use a hosted platform such as Zapier, Composio or CData Connect AI, or a custom MCP server on the REST API.

Official server: Yes, generally available
Sage Intacct's AI Gateway (REST API plus an MCP Server) has been in the release notes since 2026 R2 (May 8, 2026), and Sage called it generally available in the US, UK, Canada, Australia and South Africa; partners report it is read-only and needs an AI Gateway subscription plus a Web Services Developer license, which was not confirmed on a Sage page.

Building a product that needs Sage Intacct access? Our custom MCP development service covers customer permissions, client testing, deployment and engineering handover.

Without a build, mcpbizapps, AIONDATA’s governed MCP gateway, lists Sage Intacct among its 294 apps and sets it up for your team in a guided pilot: roles per tool, a preview before every change, approval above a set amount and an audit log.

Sage Intacct API facts that shape an MCP server

Sage Intacct API facts that shape an MCP server
FactDetailSource
Official MCP serverSage’s 2026 R2 release notes (May 8, 2026) introduce the Sage Intacct AI Gateway as "secure, scalable connectivity for AI applications through Sage Intacct REST API and MCP Server". They list it for Australia, Canada, Singapore, South Africa, the United Kingdom and the United States, without an Early Adopter label, and link to Sage’s developer portal for the documentation.Sage Intacct: 2026 R2 Release Notes
General availabilitySage’s announcement of May 28, 2026, as carried by CPA Practice Advisor, says the AI Gateway lets tailored AI solutions connect directly with Sage Intacct using REST APIs and the Model Context Protocol standard, within defined roles, permissions and workflow controls. It gives the status as generally available in the US, UK, Canada, Australia and South Africa.CPA Practice Advisor: Sage Intacct Expands Automation Across Finance Systems (May 28, 2026)
How it was launchedSage announced its AI Developer Solutions at the Sage Future for Partners event in November 2025. Sage said the MCP server is built on top of the Sage Intacct REST APIs and would launch that month with the Intacct AI Gateway, and that the program starts with Sage Intacct, with future expansion across Sage’s product portfolio.CPA Practice Advisor: Sage Launches AI Developer Solutions (November 5, 2025)
Sage CopilotSage Copilot is the chat panel inside Sage Intacct, opened from the Copilot button on any page. Its Finance Intelligence Agent became generally available in 2026 R4 for Australia, Canada, Singapore, South Africa, the United Kingdom and the United States, needs the Finance Intelligence Agent subscription, and answers only from data the user’s permissions cover: asking about unpaid bills needs List and View access to AP Bills.Sage Intacct 2026 R4 release notes: Finance Intelligence Agent, general availability
Marketplace agentsMarketplace agents, which users run in Sage Copilot, are available in Canada, the United Kingdom and the United States, in role-based companies only. As of 2026 R4 they support read-only operations, an agent can act only when both its agent role and the user hold the permission, and the API Usage Detail report shows which agent and user were involved.Sage Intacct 2026 R4 release notes: Customize Marketplace agent permissions
REST API and XML APISage Intacct offers a REST API and a legacy XML API. Both need the Web Services subscription and a Web Services user assignment. Sage strongly recommends the REST API for client applications and releases new objects and features through REST, while it continues to support the XML API.Sage Intacct help: REST API, XML API, and developer resources
Sender ID and XML gatewayThe XML Web Services API needs an active Web Services developer license, which includes a sender ID and password, and the company’s administrator must enable the Web Services subscription and authorize that sender ID. Requests are HTTP POSTs to https://api.intacct.com/ia/xml/xmlgw.phtml, and Sage recommends getting a session with getAPISession instead of sending login credentials with every request.Sage Intacct Developer: XML Web Services overview
Web Services usersA Web Services user can call the API but cannot log in to the UI. Single sign-on and multifactor authentication are disabled for it, and its password does not expire until an administrator resets it. Sage says never to share a standard user’s credentials with an integration, and to create a separate Web Services user so its permissions are controlled on their own.Sage Intacct help: Web Services users
Gateway limitsSage Intacct limits concurrent connections to the XML gateway per company: in Sage’s example of 100 simultaneous requests, 5 might be processed while the other 95 are held for about 5 seconds. A large request can time out after 15 minutes, so Sage recommends queries of fewer than 1,000 records with paging, and changes to fewer than 100 records per request.Sage Intacct Developer: XML Web Services overview
API transactionsSage Intacct counts API transactions across REST and XML: each record created, updated or deleted is one transaction (a bill or invoice with many lines still counts once), and each read call, including each further page of results, is one. The API usage tab shows the current month and the previous three by application, where each application is a Web Services sender ID; the page lists no tier sizes or prices.Sage Intacct help: View API usage
Sandbox and previewA sandbox is a copy of production with all transactional data, configurations and customizations, used for testing integrations, and it cannot be refreshed more than four times per subscription period without a fee. Preview companies, for customers in the Preview Program, are available about three weeks before each release.Sage Intacct help: About Sage Intacct company environments
Release cadenceSage Intacct uses a quarterly release cycle and upgrades every customer automatically, with no version choices. 2026 Release 2 arrived on May 8, 2026, and after the November 2026 release every company is on 2026 Release 4 until 2027 Release 1 in February.Sage Intacct: What’s new in Sage Intacct (release list)
MCP Registry and other Sage productsOn November 19, 2026 the official MCP Registry had no server published under a Sage namespace. A search for "sage" returned third-party entries only: superglue’s hosted Sage Intacct server (ai.superglue/sage-intacct, version 1.0.0, published November 4, 2026), Twinn’s read-only Sage 100 Contractor server on a demo company, and a small package that parses ledger exports. No entry names Sage 50, Sage 200 or Sage X3.Official MCP Registry: search for sage

Every way to connect Sage Intacct to AI

Every way to connect Sage Intacct to AI
OptionTypeFits whenLimits
Sage Intacct AI Gateway (MCP Server)OfficialSage Intacct companies in the regions Sage lists that want their finance data available to external AI tools through Sage’s own MCP Server, built on its REST API and working within the company’s roles, permissions and workflow controls.Sage keeps the setup guide, tool list and license terms on its developer portal, and its release notes and announcements name no posting tools and no price. Sage partners report that the MCP Server is read-only and needs an AI Gateway subscription plus a Web Services Developer license, which we have not confirmed on a Sage page.
Zapier MCP for Sage IntacctHostedTeams already on Zapier that want named Sage Intacct actions, such as Create Bill, Create Invoice, Create Vendor Invoice (a purchasing document), Create Customer and Update Bill, next to other apps.You choose from Zapier’s actions rather than the full API, and the page lists no journal entry action. Each MCP tool call uses two tasks from your Zapier plan, and Zapier says its MCP doesn’t currently support the app and action restrictions of Enterprise accounts.
Composio Sage Intacct toolkitHostedDevelopers building agents for Claude, ChatGPT or Cursor who want 26 generic Sage Intacct tools (query, get, create, update and delete records on cataloged objects, and list entities, dimensions and GL accounts) with token refresh handled for them.Composio says Sage Intacct connections must go through your own OAuth app, registered once with Sage Intacct. The catalog includes Execute Workflow (submit, approve, post), a destructive-workflow tool and security administration tools, so allowlist tools before connecting an assistant. The free Hobby plan includes 100,000 tool calls a month, and your Sage Intacct API limits still apply.
CData Connect AIHostedTeams that want a hosted MCP endpoint to live Sage Intacct data next to other CData sources, listed in Sage’s own Marketplace. The listing says it can read, write and update live data and connects under CData’s sender ID, so you don’t need to buy a Web Services developer license from Sage and its calls don’t count toward your API performance tier.Data flows through CData’s cloud, and approval steps and your company’s business rules are yours to add. The listing shows a price from $79 a month and approves the integration for Australia, France, the United Kingdom and the United States.
Unified.to (Unified MCP)HostedSoftware vendors that need real-time, pass-through Sage Intacct access for their own product or agent, next to other accounting systems, with read and write on a unified model (accounts, invoices, bills, journals, payments). Unified.to says it keeps no customer records at rest.A unified accounting model rather than Sage Intacct’s own objects, so check how your dimensions map. Trial balance, profit and loss and balance sheet are list and get only. It connects with OAuth 2.0 and has usage-based pricing with a 30-day free trial.
Custom Sage Intacct MCP serverCustomBusiness-specific tools on the REST API, each person mapped to their own entities and dimensions, writes with a preview and approval by the right role, and workflows that span Sage Intacct and other systems, hosted in your cloud.You own hosting, API credentials, testing after each quarterly release and evaluation, and it uses your company’s API transactions like any other integration.

Tools a Sage Intacct MCP server should expose

Start with read-only tools and add write actions once the team trusts the answers. Every write action below runs with a confirmation or approval step.

Tools a Sage Intacct MCP server should expose
ToolAccessRiskPurposeGuard
find_customerReadLowLook up a customer by name or ID, with open balance, terms and recent AR invoices.Allowlisted fields only; limited to the entities the signed-in user is mapped to.
get_ar_agingReadLowOpen AR invoices by customer and aging bucket, for one entity or all the user may see.Read-only; an entity and as-of date are required, and results are paged below 1,000 records.
list_bills_dueReadLowUnpaid AP bills due in the next N days by vendor and due date, with AP aging totals.Read-only; vendor names, amounts and dates only, no vendor bank details.
get_account_balancesReadMediumGL account balances for a period, filtered by dimensions such as location, department, class or project.Finance roles only; a reporting period is required and dimension values are validated against Sage Intacct.
get_trial_balanceReadMediumTrial balance for an entity and period, with opening balance, debits, credits and closing balance by account.Finance roles only; one entity and period per call; row cap.
get_purchase_order_statusReadLowStatus, amounts and received quantities for purchase orders by vendor or document number.Read-only; a vendor or document number is required.
get_project_summaryReadMediumBudget, actual cost, billed revenue and open commitments for a project.Returns only projects the user is mapped to; row cap.
create_ap_billWriteHighEnter a vendor bill with account and dimension coding from an approved document.Checks for an existing bill with the same vendor and bill number; saved as a draft only after the user confirms the preview, so Sage Intacct’s own AP approval still applies; blocked for dates in a closed period.
create_journal_entryWriteHighPrepare a balanced journal entry with accounts, dimensions and a memo.Saved as a draft, never posted; preview of every line, then approval by a user whose role may post to that journal; refused if the period is closed; logged with user and entry number.

Connect Sage Intacct to Claude, ChatGPT or Copilot Studio

Claude

Sage’s release notes and announcements name no specific AI client and point to the AI Gateway documentation on its developer portal for connection steps. A Sage partner reported in August 2026 that Claude is the client with a direct connector to the AI Gateway, which we have not confirmed on a Sage page. A hosted or custom Sage Intacct server is added as a custom connector; on Team and Enterprise plans an Owner adds it first, and with a per-user OAuth server each person then signs in with their own account. Calls come from Anthropic’s cloud, so a private server must allowlist Anthropic’s IP ranges, and claude.ai and Claude Desktop cap tool results at about 150,000 characters, so keep ledger and aging results paged.

ChatGPT

Sage’s release notes and announcements don’t name ChatGPT, so check the AI Gateway documentation before relying on Sage’s MCP Server there. For a hosted or custom server, use developer mode (Pro, Plus, Business, Enterprise and Education on the web; on Enterprise and Education an admin grants access) and add the server under ChatGPT Plugins over Streamable HTTP with OAuth. Keep Sage Intacct credentials on the server: let it act as ChatGPT’s OAuth server and hold the Web Services user or REST API tokens behind it. ChatGPT asks for confirmation on tools without a readOnlyHint, so mark reads read-only and let writes ask.

Microsoft Copilot Studio

Sage’s release notes and announcements don’t name Microsoft Copilot, and Sage Copilot is a different product: the assistant inside Sage Intacct. Add a hosted or custom server with the MCP onboarding wizard on the agent’s Tools page (Streamable HTTP only; OAuth 2.0, API key or none) and turn on generative orchestration. Use OAuth 2.0 so each person signs in with your company identity and the server maps them to Sage Intacct permissions. Power Platform data policies govern the connection.

Claude implementation · Copilot implementation · ChatGPT implementation

Permissions, identity and audit

  • Sage describes the AI Gateway as working within defined roles, permissions and workflow controls, so review each role an assistant will act under before turning it on. Sage Copilot shows the same rule in practice: a question about unpaid bills needs List and View access to AP Bills.
  • For a custom server, create a dedicated Web Services user instead of sharing a standard user’s credentials, as Sage advises, and give it only the list and view permissions the tools need. It has no single sign-on or multifactor authentication and its password never expires on its own, so keep it in a secrets manager and rotate it on a schedule.
  • A Web Services user is one shared identity, so the MCP server must map each signed-in person (from Entra ID or your identity provider) to the tools, entities and dimensions they may see: receivables staff to customers and AR, payables staff to vendors and bills, controllers to the ledger.
  • In a multi-entity company, open entity-level sessions (getAPISession accepts an entity’s location ID) and make every tool take an entity, so answers never mix entities by accident.
  • The XML API needs your sender ID authorized in each company, and the API usage tab reports each sender ID as its own application, so a sender ID of your own keeps the assistant’s calls separate from other integrations.
  • Keep write tools off until each has a preview, confirmation by a user whose role may approve that document, a duplicate check and an open-period check. Log the user, tool and record numbers for every call, and keep vendor bank details and payment tools out of the first release.

Hosting and network

  • Sage Intacct is a cloud service, so every tool call goes to Sage’s API over HTTPS. A custom MCP server runs in your AWS or Azure account, or with a hosted provider, with the sender ID, Web Services user or OAuth client secret in a secrets manager.
  • Claude, ChatGPT and Copilot Studio connect from their own clouds, so publish the server over HTTPS behind OAuth, or use ChatGPT’s Secure MCP Tunnel for a private deployment.
  • Queue calls per company, because Sage limits concurrent connections per company and holds the excess. Keep queries under 1,000 records and paged, and cache reference data such as accounts, dimensions, customers and vendors so the assistant uses fewer API transactions.
  • Build against a sandbox, which is a copy of production, and retest every tool after each quarterly release; preview companies are available about three weeks ahead. Sage also plans to move its legacy XML API documentation to the Sage Intacct Developer Portal with 2027 R1, without changing the XML API itself.

Cost and timeline

  • Sage’s release notes and announcements give no price for the AI Gateway. The REST and XML APIs need the Web Services subscription, and the XML gateway needs a Web Services Developer License, which Sage sells through your account manager; ask for the AI Gateway terms in the same conversation.
  • Every route uses API transactions: each read call and each record written counts as one, and the API usage tab shows the total by application. CData’s Marketplace listing says calls under its sender ID don’t count toward your API performance tier.
  • A focused read-only Sage Intacct MCP server typically takes two to four weeks including security and evaluation. Write tools with approvals (bills, journal entries), several entities, or workflows across Sage Intacct and other systems are scoped after a short discovery.
  • Hosted platforms price on their own terms: Zapier counts each MCP tool call as two tasks, Composio’s free Hobby plan includes 100,000 tool calls a month, CData Connect AI is listed from $79 a month, and Unified.to offers a 30-day free trial.

Sage Intacct MCP questions

Does Sage Intacct have an MCP server?

Yes. The Sage Intacct AI Gateway, introduced in the 2026 R2 release notes on May 8, 2026, provides connectivity for AI applications through the Sage Intacct REST API and an MCP Server. Sage’s announcement of May 28, 2026 calls it generally available in the US, UK, Canada, Australia and South Africa, and the release notes also list Singapore. As of November 2026 the official MCP Registry has no Sage-published entry, so start from the AI Gateway documentation on Sage’s developer portal.

How do I connect Claude to Sage Intacct?

There are three routes. Sage’s own MCP Server, set up from the AI Gateway documentation on Sage’s developer portal. A hosted platform such as Zapier, Composio, CData Connect AI or superglue, which gives you a server URL to add in Claude as a custom connector. Or a custom MCP server on the Sage Intacct REST API, added the same way, where each person signs in and the server applies your roles and approval rules.

What license does the Sage Intacct MCP server need?

Sage’s release notes don’t list license terms for the AI Gateway; they link to its documentation on the developer portal. A Sage partner reported in August 2026 that it needs an AI Gateway subscription plus a Web Services Developer license, which we have not confirmed on a Sage page, so check with your Sage account manager or partner. Sage’s help does state that the REST and XML APIs need the Web Services subscription and a Web Services user, and that a Web Services Developer License supplies the sender ID for the XML gateway.

Can an AI assistant post bills or journal entries in Sage Intacct?

Not through Sage’s MCP Server, according to Sage partners, who describe it as read-only; Sage’s release notes and announcements name no posting tools. Through the Sage Intacct API, yes: Zapier lists Create Bill and Create Invoice actions, superglue lists create and update tools for journal entries, AR invoices and AP bills, and a custom server can do the same. We build those tools to save a draft after the user confirms a preview, so Sage Intacct’s own approval rules still decide what posts.

Does it work with ChatGPT and Microsoft Copilot?

Sage’s release notes and announcements name no specific AI client. A Sage partner reported in August 2026 that Claude has a direct connector and that Sage had not yet published setup instructions for other tools, which we have not confirmed on a Sage page. A hosted or custom Sage Intacct MCP server with OAuth can be added in ChatGPT developer mode and in Copilot Studio over Streamable HTTP. Microsoft Copilot is separate from Sage Copilot, the assistant inside Sage Intacct.

How is the AI Gateway different from Sage Copilot?

Sage Copilot is the assistant inside Sage Intacct: you open it from the Copilot button, and its Finance Intelligence Agent, generally available since 2026 R4, answers questions about your financial data under your own permissions. The AI Gateway faces outward: it connects Sage Intacct data to external AI tools and custom applications through the REST API and the MCP Server. Use Copilot for questions inside Sage Intacct, and the AI Gateway or another MCP server when the work happens in Claude, ChatGPT or your own agent.

Do Sage 50, Sage 100, Sage 200 or Sage X3 have an MCP server?

We found none published by Sage. As of November 2026 the official MCP Registry has no server under a Sage namespace; its Sage-related entries are third-party, such as superglue’s Sage Intacct server and Twinn’s read-only Sage 100 Contractor server. Sage said in November 2025 that its AI Developer Solutions start with Sage Intacct, with future expansion across its product portfolio. For Sage 50, Sage 100, Sage 200, Sage X3 or Sage Accounting, plan on a hosted platform or a custom server on that product’s API, and ask Sage about its roadmap.

Should we use Sage’s server or build our own?

Use Sage’s MCP Server if answers from your finance data are enough, you are in a region Sage lists and the license terms suit you: it runs on Sage’s REST API within your existing roles and permissions. Build if you need write actions with approvals, tools shaped around your dimensions and entities, workflows that span Sage Intacct and other systems, or a client or region Sage doesn’t cover. AIONDATA is independent and not a Sage partner, so we will tell you when the official server is the better choice.

Connect Sage Intacct to your AI assistants.

Tell us which Sage Intacct questions and actions matter. We’ll say whether the official route is enough and scope a custom server where it isn’t.

Please share the workflow and the systems involved—not credentials or employee or customer records.

AIONDATA colleagues gathered in front of arched windows during a team outing.The people behind the work.Get to know our team and life at AIONDATA. Meet the team
NVIDIA Inception

NVIDIA Inception member

Part of NVIDIA’s program for startups building with AI and accelerated computing.

About the program
Pravin BansalSravan Modugula

Bay Area roots. Enterprise experience.

Pravin’s experience includes Google and SmartBear. Sravan previously held leadership roles at JPMorgan Chase and First Republic Bank.

Meet the founders

San Francisco Bay Area, California

9110 Alcosta Blvd Ste H345, San Ramon, CA 94583

US-led delivery, with engineering in India. Supporting US and international organizations.
Prefer email? info@aiondata.io

Scope your Sage Intacct MCP server.

Just your name and email to get started. Your details are handled under our Privacy Policy.

Prefer email? info@aiondata.io