Skip to main content
Oct 25–28SuiteWorld 2026 — Meet our team
Category
NetSuite
Published
Reading time
14 min read

How to Connect NetSuite to Claude (2026 Step-by-Step)

Connect NetSuite to Claude in five steps: enable features, install the MCP Standard Tools SuiteApp, build a non-admin role, add the connector, verify.

Contents14 sections ↓

Connecting NetSuite to Claude takes an administrator about an hour, and the connection itself is an Oracle feature rather than a third-party add-on. This guide follows Oracle's own documentation, step by step, and adds the errors people hit on the first attempt. If you want the background on what the NetSuite AI Connector Service is and how MCP works, read our NetSuite MCP explainer first.

Direct answer: To connect NetSuite to Claude, enable Server SuiteScript, REST Web Services and OAuth 2.0 in NetSuite, install the free MCP Standard Tools SuiteApp, give a non-administrator role the "MCP Server Connection" and "Log in using OAuth 2.0 Access Tokens" permissions, then add the NetSuite connector in Claude (Pro plan or higher, per Oracle) and sign in with that role.

What you need before you start

RequirementExact nameWhere
NetSuite featureServer SuiteScriptSetup > Company > Enable Features > SuiteCloud
NetSuite featureREST Web ServicesSetup > Company > Enable Features > SuiteCloud
NetSuite featureOAUTH 2.0Setup > Company > Enable Features > SuiteCloud
SuiteAppMCP Standard ToolsSuiteApps tab (managed SuiteApp, free)
Role permissionMCP Server ConnectionManage Roles > Permissions > Setup
Role permissionLog in using OAuth 2.0 Access TokensManage Roles > Permissions > Setup
Role permissionREST Web ServicesNeeded for the record create/update tools
Role typeAny non-administrator roleAdministrator and full-permission roles are blocked
Claude planPro or higher, per Oracleclaude.ai, Claude Desktop, Cowork, Claude Code

Sources: Oracle's Required Features and Permissions, Installing the MCP Standard Tools SuiteApp and the NetSuite AI Connector Service FAQ.

Two notes on the plan requirement. Oracle's Get Started page says the NetSuite connector in Claude needs "the Pro plan (or higher)". Anthropic's help center lists web connectors as available for all users on Claude, Cowork, Claude Desktop and mobile, with Free accounts limited to one custom connector. If you are on a Free plan, expect Oracle's statement to be the one that applies to you.

One more: Oracle states the service "has not been assessed for compliance with HIPAA" and tells you not to send electronic protected health information through it.

Step 1: Enable the three NetSuite features

  1. Log in with an Administrator role.
  2. Go to Setup > Company > Enable Features and open the SuiteCloud subtab.
  3. Under SuiteScript, check Server SuiteScript.
  4. Under SuiteTalk (Web Services), check REST Web Services.
  5. On the same subtab, check OAUTH 2.0.
  6. Click Save.

Oracle lists Server SuiteScript and OAuth 2.0 as required for the AI Connector Service itself, and REST Web Services as required to install the SuiteApp. Enable all three in one pass.

Step 2: Install the MCP Standard Tools SuiteApp

  1. Click the SuiteApps tab.
  2. In Search SuiteApps, type MCP Standard Tools.
  3. Open the SuiteApp page and click Install (top right).
  4. Wait for the installation to finish.

The SuiteApp is a managed SuiteApp, so Oracle updates it automatically. Oracle's FAQ answers the cost question directly: the AI Connector Service is not a paid feature and the SuiteApp is free. What you may pay for is the Claude subscription.

If the Install button is missing or the tool list is empty afterwards, check the installation status under the SuiteApps tab and make sure your role can see the SuiteApp's folder in the File Cabinet, which Oracle names as a cause of "access denied" errors.

Step 3: Create a role for AI access

Oracle blocks the Administrator role and any role with full permissions. Build a role with only what Claude should be able to see.

  1. Go to Setup > Users/Roles > Manage Roles > New (or copy an existing non-admin role).
  2. On the Permissions > Setup subtab add:
    • MCP Server Connection
    • Log in using OAuth 2.0 Access Tokens (Oracle warns not to confuse it with "Log in using Access Tokens")
    • REST Web Services, only if you want the create/update/transform tools
  3. Add the record, report and search permissions the role should have. A tool only appears in Claude if the role holds every permission that tool requires.
  4. Save the role and assign it to the user who will connect from Claude (Setup > Users/Roles > Manage Users > Access subtab).

For finance users, Oracle ships preconfigured "MCP-ready roles" (CFO, Controller, AR/AP Analyst, Treasury) in the NetSuite AI Connector Service Companion SuiteApp. We still recommend reading what each one grants before you use it.

Step 4: Add the connector in Claude

Oracle documents the claude.ai path in Connect to the NetSuite AI Connector Service:

  1. Log in to claude.ai.
  2. Go to Search and tools > Add connectors.
  3. Under the Web tab, select the NetSuite connector and click Connect.
  4. Paste the server URL with your account ID: https://<accountid>.suitetalk.api.netsuite.com/services/mcp/v1/suiteapp/com.netsuite.mcpstandardtools
  5. Click Continue, then go to Search and tools > Manage connectors and click Connect under NetSuite.
  6. On first connection, NetSuite shows the risks page and asks you to allow or deny access. Pick the non-administrator role from Step 3 when you sign in.

Two details about the URL. Your account ID is on Setup > Company > Company Information > Company URLs; Oracle says to copy it from there rather than build the domain yourself, because sandbox IDs such as 123456_SB1 become 123456-sb1 in the domain (underscore to hyphen, lowercase) per URLs for Account-Specific Domains. And the path matters: /services/mcp/v1/suiteapp/com.netsuite.mcpstandardtools returns only the Standard Tools, while /services/mcp/v1/all returns every custom tool in the account. Oracle's FAQ notes that leaving the suffix off entirely makes the connector show as disconnected.

If you built custom tools and want to add them as a separate connector, use Add custom connector (Anthropic's help center puts this under Customize > Connectors > + Add), enter a name and the /all URL, click Add, then Connect. On Team and Enterprise plans an Owner adds connectors under Organization settings > Connectors first, and members then connect individually.

After the first successful connection, NetSuite creates an integration record automatically. You can see it at Setup > Integration > Manage Integrations: Public Client checked, Authorization Code Grant checked, the NetSuite AI Connector Service scope enabled.

Step 5: Verify, then watch the log

Ask something that only your account can answer: "How many open sales orders do we have this month?" Oracle's best practice is to tell the model to use real data from your NetSuite account, so it does not fall back to sample data.

Then open the integration record and its Execution Log tab. The AI Connector Service (MCP) subtab lists every call with date, duration, status, user, HTTP status and URL path. Retention is 21 days in production and 7 days in sandbox, so export anything you need for an audit.

Want this set up with the right roles from day one?

We have been connecting AI to NetSuite since before MCP existed. We scope the roles, install the SuiteApp, connect Claude and hand you a tested, logged setup.

Talk to a NetSuite AI developer

claude.ai vs Claude Desktop vs Claude Code

The connection is the same NetSuite endpoint in all three; what changes is where you add it.

  • claude.ai (web) is the path Oracle documents. Connectors you add here are shared with Claude Desktop and Cowork under the same account, per Anthropic's help center.
  • Claude Desktop uses the same connector list. There is nothing NetSuite-specific to install on the desktop app.
  • Claude Code picks up connectors automatically when you are logged in with a claude.ai subscription: run /mcp to see them. That does not happen when you authenticate with an API key or a third-party provider such as Bedrock. You can also add the server directly:
claude mcp add --transport http netsuite https://<accountid>.suitetalk.api.netsuite.com/services/mcp/v1/suiteapp/com.netsuite.mcpstandardtools

Then run /mcp inside Claude Code and complete the OAuth login in the browser. The command syntax and the connector behaviour come from the Claude Code MCP documentation; Oracle also links a SuiteAnswers article for Claude Code from its connection page (SuiteAnswers requires a NetSuite login).

NetSuite skills for Claude

Oracle publishes two business-user skills for MCP clients in its netsuite-suitecloud-sdk repository and documents how to load them in Using Skills with Claude, ChatGPT, and Other MCP Clients:

  • netsuite-ai-connector-instructions: tool-selection order (reports first, then saved searches, then records, SuiteQL last), output formatting, multi-subsidiary and currency handling, and a SuiteQL safety checklist.
  • netsuite-finance-analyst: income statement, balance sheet, cash flow, budget vs actual, AR/AP aging and close support, defaulting to read-only analysis.

To load one in Claude: download the skill folder as a ZIP (the root must contain SKILL.md), enable code execution under Settings > Capabilities (an organization owner does this on Team and Enterprise), then go to Customize > Skills > + Create skill and upload the ZIP. Claude invokes the skill when a request matches its description. In our experience the instructions skill is the one to load first: it stops the model from writing SuiteQL for questions a standard report already answers, which is also Oracle's own best-practice advice.

What works and what does not

The MCP Standard Tools SuiteApp exposes 26 tools in seven groups, listed in Oracle's Available Tools page:

GroupToolsWhat Claude can do
Reportsns_listAllReports, ns_runReport, plus subsidiary, accounting book, context and nexus lookupsRun standard and custom reports
Saved searchesns_listSavedSearches, ns_runSavedSearchRun any saved search the role can see
SuiteQLns_runCustomSuiteQL, ns_getSuiteQLMetadataRead-only queries across tables
Recordsns_getRecord, ns_createRecord, ns_updateRecord, ns_transformRecord, metadata toolsRead and, if the role allows, create or update records
Record actionsns_getRecordActionMetadata, ns_executeRecordActionRun actions available on a record
File Cabinetns_searchFiles, ns_attachFile, ns_detachFile, path lookupsFind and attach files
Runtimens_getSessionInfoReport the connected role, features and permissions

Limits Oracle states in its FAQ and connection docs:

  • SuiteQL is read-only. Oracle also advises against using SuiteQL to rebuild financial reports, because standard reports apply business rules SuiteQL does not.
  • Reports accept only date and subsidiary filters. Accounting-period filters are not supported.
  • Roughly 5,000 rows per call is the typical AI-client ceiling, and large queries can hit token limits or time out.
  • Concurrency is shared. The connector draws on the same concurrent-request pool as your other integrations; each prompt that calls a tool counts as one main request plus the protocol's extra requests. See concurrency governance.
  • No administrator role, no Suitelets, no SuiteScript with elevated privileges, no HTTP requests to external destinations, per Oracle's risks and controls page.

What people underestimate: Claude does well on questions that map to an existing report or saved search, and on exploratory joins over a few thousand rows. It is not a replacement for a scheduled integration, and Oracle's own guidance is to review the tool calls and the answer, because "LLMs may sometimes make up information."

Troubleshooting

Every row below comes from Oracle's AI Connector Service FAQ or the SuiteApp installation page.

SymptomLikely causeFix
Claude says connected, NetSuite shows disconnectedURL missing the /all or SuiteApp suffix; SuiteApp not installed; wrong roleCorrect the URL, install the SuiteApp, sign in with the configured role
Cannot connect after adding permissionsWrong permission ("Log in using Access Tokens" instead of OAuth 2.0), admin role, feature offUse "Log in using OAuth 2.0 Access Tokens", switch to a non-admin role, re-check the three features
Connection fails with AdministratorOracle blocks admin and full-permission rolesCreate a custom role (Step 3)
No tools listedRole lacks a tool's permissions; SuiteApp folder restricted in File Cabinet; install incompleteAdd permissions, unrestrict the folder, check installation status
"Too Many Requests"Concurrency limit exceededRetry; have an administrator assign a concurrency limit to the integration record
Integration record stuck in pendingRecord created by a SuiteApp install, not yet enabledAn administrator enables it at Setup > Integration > Manage Integrations
Client will not add the connectorSome clients and ChatGPT plans need Developer ModeTurn it on in the client, then retry
Sample-looking numbers in answersModel used placeholder dataTell it to use real data from your NetSuite account

Role design and security

Oracle's security model is explicit: MCP is off for everyone until an administrator grants the permission, every call runs with the connected user's role, and every call is logged. The design decisions that matter are yours:

  1. Start read-only. Leave REST Web Services off the role until you have a workflow that needs record creation. Without it, the create, update and transform tools do not appear.
  2. One role per job. Oracle recommends separate roles for different MCP tools instead of reusing broad operational roles. A "Claude AR analyst" role and a "Claude inventory" role are easier to audit than one wide role.
  3. Set an external ID when creating records. Oracle's best-practice page asks for externalId on every ns_createRecord call to prevent duplicates.
  4. Review consent grants and logs periodically. Oracle suggests reviewing users with the permission, the installed tools, authorized AI agents and active consent grants on a schedule, and keeping a written procedure for revoking access fast.
  5. Keep NetSuite tools away from broad local tools. Oracle warns against combining NetSuite MCP tools with tools that have wide access to file systems, browsers, email or databases in the same agent, because of prompt-injection risk.

For the full list of risks Oracle names (prompt injection, hallucination, tool poisoning, tool drift) see the risks, controls and mitigation page, and our NetSuite MCP explainer for how we apply them.

What changes when you connect ChatGPT instead

Oracle documents ChatGPT on the same connection page:

  • In ChatGPT, open Apps in the sidebar, search for NetSuite, click Connect, then Sign in to NetSuite, and select the non-administrator role.
  • Custom tools in ChatGPT require a new integration record for every connection, which Claude does not.
  • Some ChatGPT plans need Developer Mode before MCP connectors can be added.
  • The NetSuite side (features, SuiteApp, role) is identical.

Oracle's skills load into ChatGPT through the profile menu (Skills > New skill > Upload from your computer).

FAQ

What clients ask before signing

Sources

Get your integration scoped

Tell us what systems you need to connect. We'll recommend the right approach and ballpark the cost.

We respond within 24 hours.

Share
BR.

BrokenRubik

Company

Independent NetSuite consultancy: implementation, SuiteCommerce, custom SuiteScript, and integrations for mid-market companies. 100+ companies served since 2017.

Related