Reach out to us by saying 👋
hello@auditfriendly.coReceive Updates By Signing Up For The Newsletter
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Yes. At its Sage Future for Partners event on November 4 to 5, 2025, Sage launched the Sage Intacct AI Gateway, a first-party Model Context Protocol server built on the Intacct REST API, though connecting an agent like Claude is still an admin-enabled build rather than a one-click connector.
What it can do. With the AI Gateway enabled and scoped credentials, an AI agent such as Claude can connect over MCP to query Sage Intacct financial data in natural language and invoke the REST API operations the gateway exposes, within whatever the administrator has permitted that application to see and do.
Where it stops. It cannot be connected one-click: Sage Intacct is not listed in Anthropic's connectors directory, so an administrator must enable the gateway and scope credentials first. An agent cannot exceed the permissions granted, and project accounting and fixed assets are reported to still sit on the legacy XML API rather than REST, so coverage there is thinner.
Yes. At its Sage Future for Partners event on November 4 to 5, 2025, Sage announced AI Developer Solutions, and its first phase is the Sage Intacct AI Gateway: a first-party Model Context Protocol (MCP) server built on the Intacct REST API. Sage describes it as a governed, auditable endpoint where the customer controls what an AI application can see and do, which is exactly the framing a finance system needs before anyone lets an agent near the general ledger.
MCP is the open standard AI applications such as Claude use to reach external systems, so a first-party server matters. With the gateway enabled and scoped credentials, an AI agent can query Intacct financial data in natural language and invoke the operations the gateway exposes, within whatever the administrator has permitted that application to see and do. Sage positions the gateway for intelligent orchestration across multiple coordinating agents, says certified third-party AI agents will be integrated directly into the Sage Copilot experience, and is building the surrounding agent infrastructure with AWS on Amazon Bedrock and AgentCore.
The plumbing underneath is the Intacct REST API, which reached general availability in 2025 Release 1. All new objects and features now ship through REST, and the older XML web services API is designated legacy, though it remains supported for existing integrations.
The catches are real:
Where first-party coverage falls short, third-party MCP servers exist from CData, Zapier, and Apideck, plus an open-source read-only server built on the XML web services API. They are useful, but they are not Sage-built and carry their own permission models. The honest summary: Sage Intacct has a genuine first-party MCP server, which puts it ahead of most finance platforms, but connecting an agent today is a scoped, admin-enabled build rather than a toggle.