At a Glance — NetSuite MCP Options
- Native: NetSuite’s AI Connector Service with the MCP Standard Tools SuiteApp: tools for records (including create and update), reports, saved searches and read-only SuiteQL, limited by the user’s role
- Celigo MCP Server: a defined set of narrow queries across connected systems, scoped tokens, read-only enforcement at the MCP layer, query-level logging
- n8n MCP Server Trigger: any n8n workflow becomes a tool, so you can add validation, transformation and approvals
- Our rule of thumb: NetSuite-only and role-based, start native. Multi-system or must-be-read-only, Celigo. Custom logic, n8n.
- Applies to all three: the AI’s access is only as safe as the role or token behind it, and prompt injection through free-text fields is still yours to design around
What NetSuite’s native MCP support is
Oracle’s documentation says NetSuite has adopted the Model Context Protocol so that supported AI clients can access and interact with NetSuite data and functionality. In practice that is two pieces. The NetSuite AI Connector Service is the MCP endpoint. The MCP Standard Tools SuiteApp is the set of tools NetSuite ships for it, and you can build your own custom tools as well.
Oracle lists the standard tools in four groups:
- Records: create a record, get a record, update a record, and get record-type metadata including fields and data types.
- Reports: list all standard and custom reports, run a report, and list the accounting books, accounting contexts, nexuses and subsidiaries used to filter report results.
- Saved searches: list saved searches and run an existing one.
- SuiteQL: run a custom SuiteQL query (Oracle says only read-only queries are supported) and get SuiteQL metadata.
Two points from Oracle’s pages matter most. First, the SuiteApp “includes tools that can create and update records in NetSuite using REST Web Services,” so a connected assistant is not read-only by default. Second, access follows the role: the tools use the same access controls as the NetSuite UI and don’t provide access beyond what the role allows, and a tool shows up in the AI client only if the role has all the permissions it needs.
What Oracle says about roles, setup and logging
- Permissions. Roles that already have the MCP Server Connection permission can perform actions on any records available through REST, if their permissions allow. Oracle suggests reviewing which users and roles hold that permission before installing the SuiteApp, and creating a separate role with the permission plus specific record permissions.
- Which role you sign in with. For ChatGPT, Oracle’s instructions say to select a non-administrator role. For Claude, Oracle says you need the Pro plan or higher.
- Endpoint. Oracle gives the standard-tools address as
https://<accountid>.suitetalk.api.netsuite.com/services/mcp/v1/suiteapp/com.netsuite.mcpstandardtools, and a second address for all custom tools. - Integration record. The first connection from Claude installs an integration record (Public Client, Authorization Code Grant, with the AI Connector Service scope). Its State and Concurrency Limit fields can be edited, so you can disable it or give it a share of your concurrency limit.
- Logging. An AI Connector Service (MCP) subtab in the execution log shows call date and time, duration, status, user email, HTTP status code, method and URL path, kept for 21 days in production and 7 in sandbox.
- Compliance. Oracle states the service has not been assessed for HIPAA compliance and must not be used for ePHI unless you have independently determined that use is consistent with your obligations.
NetSuite AI Connector vs Celigo MCP Server vs n8n
The three are not interchangeable. The difference is who decides what the AI can ask for. The first two rows below come from Oracle’s documentation, our own Celigo MCP Server article and our n8n MCP Server article.
| NetSuite AI Connector | Celigo MCP Server | n8n MCP Server Trigger | |
|---|---|---|---|
| What it reaches | NetSuite, through the MCP Standard Tools SuiteApp or your own custom tools | Systems connected in Celigo, such as NetSuite and Salesforce | Whatever your workflows touch |
| Who defines the tools | Oracle ships the standard tools; you can build custom ones | You, as a set of queries with fixed inputs and outputs | You, as workflows |
| Access control | The signed-in user’s NetSuite role, via the MCP Server Connection permission | A scoped token managed by Celigo; read-only enforced at the MCP layer | Bearer token on the trigger endpoint; OAuth for instance-level access |
| Can it write? | Yes, create and update tools exist; SuiteQL is read-only | Only if you define a write; read-only tokens block writes | Only if you build one; best added behind validation and approval |
| Logging | Execution log: time, duration, status, user email, HTTP status, method, URL path | Each query: timestamp, model or token identity, input parameters, response hash | n8n’s execution history for each workflow run |
| Setup effort | Install the SuiteApp, set up a role, connect the client | Define the queries and tokens in Celigo | Build and test the workflows |
Which one to use
- Start native when the work is NetSuite-only and the users already have the right roles. Finance and operations staff asking questions of their own data, with NetSuite’s permissions doing the gatekeeping, is what it is built for.
- Choose Celigo’s MCP Server when the tools must be narrow and read-only by design, or span systems. “Order status by order number” and “inventory by SKU” as fixed queries are a smaller surface than a role that can reach every record.
- Choose n8n when the tool needs logic. Validation, joining NetSuite with another system, transformation, or a human approval step before a write are workflow jobs.
- Combine them. Native for exploratory questions, Celigo or n8n for the governed tools an agent uses repeatedly. They don’t conflict, as long as each AI client has its own access and role.
What stays your problem with any of them
Whatever sits between the AI and NetSuite, the AI reads what is in NetSuite. A customer memo or item description containing hidden instructions can steer a model, and a role that can reach too much quietly undoes the scoping. Our MCP security article covers the risks, and our system of record vs system of action guide explains why we put the control in a layer you own. For the cost side, see AI agent NetSuite integration cost.
Review which roles hold the MCP Server Connection permission. Create a separate role with only the record permissions the work needs. Install the MCP Standard Tools SuiteApp. Connect the AI client with the endpoint from Oracle’s documentation and a non-administrator role. Check the integration record and its concurrency limit, then read the execution log. Oracle’s pages cover the required features and permissions in detail, so follow them rather than a third-party summary.
Frequently Asked Questions
What is NetSuite MCP? NetSuite MCP means connecting an AI assistant such as Claude or ChatGPT to NetSuite through the Model Context Protocol. NetSuite offers this natively through its AI Connector Service and the MCP Standard Tools SuiteApp, which expose tools for records, reports, saved searches and SuiteQL. You can also build the same access with Celigo's MCP Server or with n8n's MCP Server Trigger.
Can an AI assistant change NetSuite records through the AI Connector Service? Yes. Oracle's documentation says the MCP Standard Tools SuiteApp includes tools that can create and update records in NetSuite using REST Web Services. The SuiteQL tool is read-only. What the assistant can do depends on the NetSuite role you sign in with, so Oracle recommends a separate role with only the permissions the work needs.
Which AI clients work with NetSuite's AI Connector Service? Oracle's documentation describes connecting Claude, which requires the Pro plan or higher, and ChatGPT, where you choose a non-administrator role at sign-in. For other clients, Oracle points to that provider's own documentation and to building custom tools.
How is NetSuite MCP access logged? Oracle's documentation describes an execution log with an AI Connector Service (MCP) subtab showing the call date and time, duration, status, user email, HTTP status code, method and URL path. Retention is 21 days in production and 7 days in sandbox. Celigo's MCP Server logs each query with a timestamp, the model or token identity, the input parameters and a hash of the response.
Should I use NetSuite's AI Connector, Celigo or n8n for NetSuite MCP? Entech's view: use NetSuite's native connector when the work is NetSuite-only and role-based access is enough, Celigo's MCP Server when you want a small set of narrow, read-only tools across NetSuite and other systems with query-level logging, and n8n when the tools need custom logic, validation or transformation. Many teams use more than one.
Sources
- Get Started with the NetSuite AI Connector Service (Oracle NetSuite Help)
- MCP Standard Tools SuiteApp (Oracle NetSuite Help)
- Available Tools in the MCP Standard Tools SuiteApp (Oracle NetSuite Help)
- Connect to the NetSuite AI Connector Service (Oracle NetSuite Help)
Oracle’s documentation changes with each release. We reviewed these pages on October 15, 2026, and will re-check them as NetSuite updates the service.
Entech Solutions is a certified Celigo partner and builds n8n workflows, including governed AI access to NetSuite. See our AI Agents & MCP Server page, or talk to an integration expert about which option fits your setup.