By Louis Balla, Chief Revenue Officer, Nuage. Updated October 2026.
To connect Claude to NetSuite, you use Oracle’s NetSuite AI Connector Service. On the NetSuite side, an administrator enables the required features and installs the MCP Standard Tools SuiteApp. Users connect through a non-administrator role that carries the MCP Server Connection permission. In Claude, you add NetSuite as a custom connector and sign in with that role.
The steps below follow Oracle’s NetSuite help center and Anthropic’s Claude help center, linked in each step, and the setups our team has run for clients. Menu labels can differ by role and change as both products update.
What is the NetSuite Claude connector?
The NetSuite AI Connector Service is Oracle’s service for connecting an AI client such as Claude to NetSuite over the Model Context Protocol (MCP), an open standard for connecting AI assistants to business systems. The tools Claude calls come from the MCP Standard Tools SuiteApp. According to Oracle’s MCP Standard Tools SuiteApp overview and its AI Connector Service FAQ, those tools let Claude:
- create and update records
- run reports
- run saved searches
- query data with SuiteQL, which is read-only through the connector
Every tool runs under the NetSuite role the user signed in with. Claude sees and changes only what that role allows.
What you need before you connect Claude to NetSuite
- A Claude plan that supports the connector. Oracle’s getting started page lists Claude Pro or higher. On Team and Enterprise plans, an organization owner adds the connector to the organization and each user then connects to it. Plan terms change, so confirm with whoever manages your Claude account.
- Someone who can enable features and install SuiteApps in NetSuite, usually your administrator. That person sets the connection up, but the Administrator role itself cannot be used to connect Claude.
- A dedicated non-administrator role for the people who will use Claude. Step 3 covers it.
- A sandbox account for the first test, if you have one.
A controller asked us what had to be in place before his IT team came on site to connect the company’s Claude license. We named the SuiteApp and the role prerequisites, he made the connection himself, and he wrote back “It’s amazing.” In the follow-up session we recommended a dedicated non-admin role with view-level permissions, no access to payroll or sensitive employee data, and a gradual rollout with validation steps before anyone uses it to change records. The ticket closed 10 days after the request.
The connector inherits your existing access controls, so the role design you already have decides most of what Claude can reach. Our guide to NetSuite customization and configuration support covers that groundwork.
How to connect Claude to NetSuite, step by step
Step 1: Enable the required features
Go to Setup > Company > Enable Features and open the SuiteCloud subtab. Check these features, then click Save:
- Server SuiteScript
- OAuth 2.0
- REST Web Services, which the MCP Standard Tools SuiteApp needs
Oracle lists them on its required features and permissions page.
Step 2: Install the MCP Standard Tools SuiteApp
Open the SuiteApps tab, enter “MCP Standard Tools” in the search field, click the MCP Standard Tools icon and click Install. Wait for the installation to finish. Oracle’s installation guide notes that this is a managed SuiteApp that updates automatically, and updates can change how its tools behave. If you build workflows on these tools, retest them after an update.
Step 3: Create a dedicated role for Claude users
Go to Setup > Users/Roles > Manage Roles and create a role for Claude users, or edit a suitable non-administrator role. On the Permissions > Setup subtab, add:
- MCP Server Connection
- Log in using OAuth 2.0 Access Tokens, which is a different permission from “Log in using Access Tokens”
- REST Web Services, which lets users create, retrieve and update records through the SuiteApp
Then add the record permissions the users need, and give the role access to the SuiteApp’s folder in the File Cabinet. If that folder is restricted for the role, Claude’s tool calls can return an access denied error. Assign the role to each user who will connect.
Oracle blocks the connector for the Administrator role and for roles with full permissions to NetSuite features. Oracle’s reason is to prevent unwanted results if the AI client’s security is ever compromised.
Two client setups show how this step plays out. At an industrial distributor, Claude’s authorization failed with the selected role until we created a dedicated OAuth integration role. After the data was validated in sandbox and production, we added Claude access to five named roles in both environments. At a home furnishings company whose controller wanted “basically every group” on Claude, we first asked which functions, roles and record types to start with, then set up access for two users with employee Social Security numbers left masked.
Roles also need a check before each NetSuite release. In September 2026, ahead of the 2026.2 release, we sent an advisory to 67 client accounts that roles with Core Administration Permissions might no longer be able to establish the MCP connection, so any integration role in use should be reviewed.
Step 4: Add NetSuite as a custom connector in Claude
On a Pro or Max plan, go to Customize > Connectors in Claude, click Add and choose Add custom connector. Give the connector a name and enter Oracle’s server URL:
https://ACCOUNT_ID.suitetalk.api.netsuite.com/services/mcp/v1/all
Put your NetSuite account ID in place of ACCOUNT_ID. Oracle’s FAQ notes that the URL must end in /all, or the connection will show as disconnected.
On Team and Enterprise plans, an owner adds the connector under Organization settings > Connectors. Each user then finds it under Customize > Connectors and clicks Connect. Anthropic’s custom connector guide has the current screens for each plan.
Step 5: Sign in to NetSuite and approve the connection
Claude opens a NetSuite sign-in. Log in as the user who will work in Claude, use the role from step 3 and approve the access request. Oracle requires this OAuth 2.0 consent for each AI client you connect.
Step 6: Run a test query and check it against NetSuite
Ask for something you can verify on screen, such as “Show me the 10 most recent sales orders.” Compare the answer with the same list in NetSuite. If you have a sandbox, test there first with your sandbox account ID in the URL, then repeat in production.
Troubleshooting the NetSuite Claude connector
| Symptom | Likely cause | What to check |
|---|---|---|
| The connector shows as disconnected in Claude | The server URL is missing /all |
Use the full URL ending in /services/mcp/v1/all |
| The connection is refused when you sign in as an administrator | The Administrator role and full-permission roles are blocked | Sign in with the dedicated role from step 3 |
| Authorization fails with a non-administrator role | The role is missing MCP Server Connection or Log in using OAuth 2.0 Access Tokens | Add both, and check that “Log in using Access Tokens” was not added by mistake |
| Claude reports access denied when it calls a tool | The role cannot reach the SuiteApp’s File Cabinet folder | Give the role access to that folder |
| A tool you expect is missing in Claude | The role lacks a permission that tool requires | Add the record permissions for that tool |
| Claude can read a record type but cannot change it | The role has view-level permission on that record | Raise the permission only if you intend to allow changes |
| Results or tool behavior changed without any change on your side | The managed SuiteApp updated | Retest your standard prompts after the update |
Oracle’s requirements behind each row are on the required features and permissions page and the installation guide.
Using Claude with NetSuite after it is connected
Write prompts the way you would brief someone building a report. “Show me overdue invoices” returns a loose list. “List all invoices overdue by more than 30 days, grouped by customer, sorted by amount descending, with the total outstanding per customer” returns something you can use. Give the time range, grouping, sort order and output format every time.
Point Claude at the saved searches your team already trusts. A saved search carries the filters and business logic your team has already agreed on, which a query written from scratch in a conversation does not.
One of our consultants who has used the Claude connector on several client NetSuite accounts says it is very good at pulling large amounts of data and can make wrong assumptions about what that data means. Her advice is to work inside a Claude project that carries standing instructions about your account. Those instructions can name the subsidiary and the saved searches Claude should use.
Once a prompt gives reliable answers, add it to a shared list with the expected output and the role that should run it. That list keeps results consistent as more people start using the connector.
Is the NetSuite Claude connector secure?
Oracle publishes the controls built into the service on its risks, controls and mitigation strategies page. MCP access is off by default and is granted role by role. Tools run with the user’s own permissions and never as Administrator. NetSuite logs all MCP tool usage, and each AI client needs the user’s OAuth consent before it connects.
The same page lists what Oracle recommends customers add:
- separate roles for MCP use, granted only to the people who need them
- read-only or low-impact tools first, with permissions expanded after you review behavior and logs
- an AI client that asks for explicit confirmation before high-impact actions such as creating, changing, deleting, approving or paying
- regular review of NetSuite’s MCP logs alongside the AI client’s logs
- a written procedure for disabling MCP access or revoking consent quickly
Oracle also states that the AI Connector Service has not been assessed for HIPAA compliance, and that it must not be used for electronic protected health information unless you have independently determined that such use meets your own HIPAA obligations.
For the audit side of AI-assisted work, see our articles on keeping an audit trail when AI is doing the work in NetSuite and internal controls in the age of AI.
How Nuage approaches a Claude connector setup
In recent projects, our team has worked through these steps:
- Scope the first users. Before building anything, we have asked which functions, roles and record types should come first, including when a controller wanted every group in the company on Claude.
- Build a dedicated role. We have recommended a non-admin role with view-level permissions and no access to payroll or sensitive employee data, and in one setup we left employee Social Security numbers masked.
- Validate in sandbox, then production. At the industrial distributor, the data Claude returned was checked in both environments before more roles were added.
- Expand role by role. At the distributor, Claude access went to five named roles after the data was validated. We have recommended validation steps before anyone uses Claude to change records.
- Review integration roles before a release. Ahead of the 2026.2 release, we sent clients the role advisory described in the setup steps above.
Our team does this work as part of ongoing NetSuite optimization and managed services.
NetSuite Claude connector FAQ
How do I connect NetSuite to Claude?
Enable the three features listed in step 1, install the MCP Standard Tools SuiteApp, and create a non-administrator role with the MCP Server Connection and OAuth 2.0 access token permissions. In Claude, add a custom connector with the URL ending in /services/mcp/v1/all, then sign in to NetSuite with that role and approve the connection.
Can Claude update records in NetSuite?
Yes, if the user’s role allows it. The MCP Standard Tools SuiteApp includes tools that create and update records, and they work only within the permissions of the role the user signed in with. SuiteQL queries through the connector are read-only. We have recommended starting with a view-only role and adding edit permissions once the answers have been validated.
Why can’t I connect Claude to NetSuite with the Administrator role?
Oracle blocks the AI Connector Service for the Administrator role and for roles with full permissions to NetSuite features. Oracle’s stated reason is to limit the damage if an AI client’s security were compromised. Create a dedicated role with the MCP Server Connection and Log in using OAuth 2.0 Access Tokens permissions, plus the record access your users need, and connect with that role.
Will Claude see NetSuite data my role can’t see?
No. Every tool call runs under the NetSuite role you signed in with, so Claude can only read or change what that role already allows. A warehouse user connected through a warehouse role sees warehouse records. To limit what Claude can reach, limit the role. Oracle’s guidance is to use separate roles for MCP access and grant them only to the people who need them.
About the author
Louis Balla is Chief Revenue Officer at Nuage, a NetSuite optimization partner that has served 250+ clients since 2011 and holds a 4.9 out of 5 rating on Clutch. The client Claude connector setups in this article are our team’s work.
