NetSuite API facts that shape an MCP server
| Fact | Detail | Source |
|---|---|---|
| Official endpoint | The NetSuite AI Connector Service is a remote MCP server per account: https://<accountid>.suitetalk.api.netsuite.com/services/mcp/v1/all returns all tools, and /services/mcp/v1/suiteapp/<applicationid> returns one SuiteApp’s tools. Without /all the connection appears disconnected. | Oracle NetSuite Help: AI Connector Service FAQ |
| Authentication and roles | OAuth 2.0 authorization code grant with PKCE. The role needs the MCP Server Connection and OAuth 2.0 Access Tokens permissions, plus REST Web Services for the Standard Tools. Administrator roles are not supported. | Oracle NetSuite Help: AI Connector Service FAQ |
| Standard tools | 14 tools: create, get and update records and read record metadata; list and run reports with accounting book, context, nexus and subsidiary helpers; list and run saved searches; run SuiteQL (read-only queries only) and read SuiteQL metadata. There is no delete tool, and MCP Apps add interactive UI. | Oracle NetSuite Help: MCP Standard Tools |
| Cost | Oracle says the AI Connector Service is not a paid feature and the MCP Standard Tools SuiteApp is free; your AI client may need a paid plan. | Oracle NetSuite Help: AI Connector Service FAQ |
| Concurrency | AI Connector calls share the account’s integration concurrency limit, set by service tier and SuiteCloud Plus licenses, unless an admin gives the integration record its own limit. Over the limit, calls fail with "Too Many Requests", and one prompt can trigger several protocol requests. | Oracle NetSuite Help: Concurrency governance |
| Report limits | Report tools support only date and subsidiary filters; accounting periods are not supported. Oracle notes that AI clients usually handle about 5,000 rows per call. | Oracle NetSuite Help: AI Connector Service FAQ |
| Custom tools | Custom tools are SuiteScript 2.1 Custom Tool scripts with a JSON-RPC schema and a toolset SDF object. The N/http, N/https, N/llm and N/sftp modules are not supported in them, so a custom tool can’t call outside systems. From the September 2026 release, the older tool XML definitions can no longer be deployed. | Oracle NetSuite Help: Custom tool script requirements |
| Audit log | Each integration record has an AI Connector Service (MCP) execution log with request time, duration, status, user, HTTP response and request details. Entries are kept 21 days in production and 7 days in sandbox. | Oracle NetSuite Help: AI Connector Service FAQ |
| Claude directory | Claude’s directory lists an Anthropic-verified NetSuite connector made by Oracle NetSuite, added November 2025, with the Standard Tools and MCP Apps. | Claude directory: NetSuite connector |
| HIPAA | Oracle states the AI Connector Service has not been assessed for HIPAA compliance and must not be used for ePHI unless you have made your own determination. | Oracle NetSuite Help: AI Connector Service FAQ |
Every way to connect NetSuite to AI
| Option | Type | Fits when | Limits |
|---|---|---|---|
| AI Connector Service with MCP Standard Tools | Official | Most finance and operations questions: records, saved searches, reports and SuiteQL under each user’s own role, at no extra NetSuite cost. | No deletes, reports filter only by date and subsidiary, and generic tools leave the model to compose queries. It shares concurrency with your other integrations. |
| Custom SuiteScript tools on the connector | Custom | Single-call business operations inside NetSuite, such as approving a vendor bill after checks or building a cash position, with your validation and under the user’s role. | No outbound HTTP, LLM or SFTP modules; deployed only through SDF; must use the toolset SDF object from the September 2026 release. |
| Oracle’s custom tool samples | Official | A starting point for custom tools and MCP Apps built with SuiteScript 2.1 and the toolset SDF object. | Samples to adapt, not finished tools; the 2026.1 toolset samples can’t be deployed to 2025.2 accounts. |
| Zapier MCP for NetSuite | Hosted | Teams already on Zapier that want a few named NetSuite actions, such as attaching a file, transforming a record or a CSV import, next to other apps. | You pick Zapier’s actions rather than NetSuite’s tools, the calls run through Zapier’s NetSuite connection, and each tool call uses two tasks from your Zapier plan. |
| External custom MCP server | Custom | Workflows that span NetSuite and other systems (CRM, WMS, banks), approvals outside NetSuite, caching, or rate control across many users. | You host and secure it. It calls REST web services, SuiteQL or RESTlets through its own integration record, so it needs its own share of the concurrency limit. |
Tools a NetSuite MCP server should expose
Start with read-only tools and add write actions once the team trusts the answers. Every write action below runs with a confirmation or approval step.
| Tool | Access | Risk | Purpose | Guard |
|---|---|---|---|---|
get_customer_balance | Read | Low | Open balance, overdue amount and credit limit for a customer. | Runs under the user’s NetSuite role; subsidiary filter enforced. |
find_transactions | Read | Low | Find sales orders, invoices or bills by customer or vendor, status and date. | Parameterized SuiteQL template only; no free-form queries; row cap. |
get_ap_aging | Read | Medium | Vendor aging by subsidiary as of a date. | Read-only saved search; results capped and paged. |
get_item_availability | Read | Low | On hand, committed and available quantity by location. | Read-only; location filter required. |
compare_period_results | Read | Medium | Compare actuals with budget or a prior accounting period for chosen accounts. | Read-only; uses accounting periods through SuiteQL, which the standard report tools can’t filter by. |
create_sales_order | Write | Medium | Build a sales order from customer, items and quantities and show totals before saving. | Saves only after the user confirms; pricing and tax come from NetSuite. |
approve_vendor_bill | Write | High | Approve a pending vendor bill after a purchase order and receipt match. | Checks the match and the user’s approval limit first; explicit approval; recorded in the execution log. |
update_customer_contact | Write | Medium | Change a customer’s email, phone or address. | Confirmation with before-and-after values. |
Connect it to Claude, ChatGPT or Copilot Studio
Claude
Oracle’s NetSuite connector is in Claude’s directory (Anthropic-verified, made by Oracle NetSuite): add it, paste your account’s MCP URL and sign in with a non-administrator role. Custom tools use a custom connector with the /all or SuiteApp URL; on Team and Enterprise plans an Owner adds custom connectors first. claude.ai and Claude Desktop cap tool results at about 150,000 characters, so keep saved searches and SuiteQL results paged.
ChatGPT
Oracle documents a NetSuite app in ChatGPT: open Apps, search for NetSuite and sign in with a non-administrator role. Oracle notes some ChatGPT plans need developer mode for MCP connectors, and ChatGPT with custom tools needs a new integration record for every new connection because the callback URLs are dynamic. In developer mode, ChatGPT asks for confirmation on tools that aren’t marked read-only.
Microsoft Copilot Studio
Add the account’s endpoint as an existing MCP server (Streamable HTTP) with OAuth 2.0; Oracle’s help points to a SuiteAnswers article on connecting Copilot Studio to the AI Connector. Generative orchestration must be on, and Power Platform data policies govern the connection.
Claude implementation · Copilot implementation · ChatGPT implementation
Permissions, identity and audit
- Every call runs with the NetSuite role the user signs in with. A tool appears only if the role has all of that tool’s permissions, and data access still follows the role.
- Create dedicated AI roles with MCP Server Connection, OAuth 2.0 Access Tokens (not Access Tokens), REST Web Services, Perform Search and only the record permissions the tools need. Administrator roles are refused.
- Custom tools declare the permissions needed to see them in the toolset object; set them tighter than the role where you can.
- To switch the connector off, remove MCP Server Connection from a role, or disable the integration record to cut all AI Connector access at once.
- An external server should use its own integration record and a least-privilege role, never a person’s token.
Hosting and network
- Oracle hosts the official server inside NetSuite; there is nothing to deploy beyond the SuiteApp, roles and the integration record.
- Claude and ChatGPT reach the endpoint at suitetalk.api.netsuite.com over the internet, so no firewall work is needed for the official route.
- An external MCP server runs in your cloud and calls NetSuite REST web services, SuiteQL or RESTlets. Give its integration record a fixed concurrency allocation so AI traffic can’t starve other integrations.
- Review the MCP execution log next to your AI client’s logs, and export it if you need more than 21 days of history.
Cost and timeline
- The official connector and Standard Tools cost nothing extra in NetSuite; the work is roles, testing and user training.
- A set of custom SuiteScript tools or a focused external NetSuite MCP server typically takes two to four weeks including security and evaluation.
- Cross-system tools and multi-step agent workflows take longer and are scoped after a short discovery.
- Zapier’s route bills each tool call as two tasks against your Zapier plan, per Zapier, so compare it on call volume.
NetSuite MCP questions
Does NetSuite have an official MCP server?
Yes. The NetSuite AI Connector Service is Oracle’s remote MCP server, and the MCP Standard Tools SuiteApp supplies the default tools. Oracle also lets you publish your own tools on the same endpoint with SuiteScript.
Is the NetSuite MCP server free?
Oracle says the AI Connector Service is not a paid feature and the Standard Tools SuiteApp is free. Your AI client may need a paid plan, and heavy use competes with your other integrations for concurrency.
Can it write data?
The Standard Tools can create and update records but not delete them, and each change runs under your role. The AI client asks your permission before it uses a tool. Custom tools can do more, so give custom write tools their own approval step.
Why can’t I connect with the Administrator role?
Oracle blocks Administrator roles for the AI Connector for access control. Use a custom role with MCP Server Connection and OAuth 2.0 Access Tokens, plus REST Web Services for the Standard Tools.
Does it work with Claude and Copilot?
Yes. Claude has an Oracle-built NetSuite connector in its directory, ChatGPT has a NetSuite app, and Copilot Studio can add the endpoint as an MCP server; Oracle points to a SuiteAnswers article for that setup.
Do AI users need NetSuite licenses?
Each person signs in to NetSuite with their own login and a non-administrator role, so they need NetSuite access like any other user. The connector adds no NetSuite fee; check user licensing with Oracle or your partner.
When do I need custom tools?
When a task needs several steps or rules in one call (approvals, matching, period-based reporting), when you want deletes under strict control, or when it must reach another system. Oracle’s custom tools can’t make outbound HTTP calls, so cross-system work belongs in a separate MCP server that calls NetSuite through REST web services, SuiteQL or RESTlets.
How is sensitive data protected?
Queries respect the role’s permissions, and Oracle notes that once data leaves NetSuite, the AI provider’s policies apply. Keep sensitive fields out of AI roles, review the MCP execution log, and remember Oracle hasn’t assessed the connector for HIPAA.
