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. NetSuite shipped a first-party Model Context Protocol integration, the AI Connector Service, in its 2025.2 release, and the companion MCP Standard Tools SuiteApp lets an AI client such as Claude run SuiteQL queries and saved searches and create or update records within the connected role's permissions, though an administrator must install and configure it before anything connects.
What it can do. Through the AI Connector Service and the MCP Standard Tools SuiteApp, an agent can run read only SuiteQL queries, list and run saved searches and standard or custom reports, read record type metadata, and retrieve, create, or update records within the permissions of the connected NetSuite role.
Where it stops. It cannot exceed the connected role's permissions, cannot write through the read only SuiteQL tools, handles bulk writes poorly because the underlying REST layer is one record per request with no batch endpoint, and does not connect at all until an administrator installs the SuiteApp and configures roles and OAuth.
Yes, and it is first-party rather than a community wrapper. NetSuite launched the AI Connector Service in its 2025.2 release, a Model Context Protocol (MCP) integration that lets external AI clients such as Claude and ChatGPT connect to a NetSuite account while preserving NetSuite's role based permissions. Oracle documents the capability itself; the global availability date, reported as around August 2025, comes from third parties. That combination makes NetSuite one of the few legacy scale ERPs with a genuine first-party MCP server an agent can actually connect to.
The working surface is the companion MCP Standard Tools SuiteApp, which exposes a set of named tools:
Everything runs inside the connected NetSuite role's permissions, so an agent sees and touches exactly what that role can and nothing more. For auditors that scoping is the headline feature; for agent builders it is the boundary to design around. Beneath the MCP layer, integrators still have SuiteTalk REST and SOAP web services, SuiteScript for server side automation, and SuiteAnalytics for reporting.
Now the honest catches. It is not turnkey: an administrator has to install the SuiteApp, grant the MCP Server Connection permission and REST Web Services access, and set up OAuth before any agent can connect at all. The SuiteQL tools are read only, so an agent cannot write through SQL; every write goes through the record tools. And those record writes ride on SuiteTalk REST, which is one record per request with no batch create or update endpoint and real concurrency limits, so single record workflows are fine while high volume updates strain it.
We score NetSuite 4 out of 5 on agent readiness, unusually strong for an ERP of this vintage. Note that the MCP path is separate from NetSuite's own embedded AI, such as the 2026.1 Intelligent Close Manager and EPM AI agents; the connector is what lets your agents, not just Oracle's, work the system. The sensible rollout is a narrowly scoped role, read only SuiteQL and saved searches first, and write permissions added deliberately.