MCP servers / NetSuite

NetSuite MCP server setup for Claude, ChatGPT and Copilot

Oracle ships an AI Connector that lets Claude and ChatGPT read NetSuite over MCP. It is real and it is free. It is also a role-and-permissions design job: OAuth 2.0, a SuiteApp bundle, a custom non-administrator role, record-level decisions about what the assistant may see and, if you want it to act, what it may change. That is where teams stall, and it is what we set up.

What the official route requires

Enable OAuth 2.0 and REST web services, install the AI Connector SuiteApp.
Create a custom role (administrator roles are blocked) with the three connector permissions.
Decide record by record what the assistant may read, then create the integration record and redirect URIs.
Repeat for each client, environment and assistant.

Where it falls short for a company

The official connector and every community server we have found are read-only or all-or-nothing on writes.
There is no approval step: either the assistant can post a journal or it cannot.
Every assistant needs its own setup, and nothing logs what was asked or changed across them.

What we set up

One MCP server for your NetSuite, hosted or in your cloud, used by Claude, ChatGPT, Copilot and our runbook agents alike.
Tools exposed per your permissions: read the ledger, list payouts, post a journal, update a record.
Named approvers on writes above a threshold you set, and an append-only log of every call.
Live in about a week; listed in your assistants' connector settings the same day.

Questions we get

Can it post transactions?

Yes, under your approvals. Read-only is the default until you switch a tool on.

Does it use Oracle's connector?

Where it helps, yes. Where the connector is read-only, our server adds the write tools with approvals.

Who owns it?

You do. It runs in your stack, and every assistant your team uses goes through the same tools and the same log.

Tell us which systems you run and we will scope the server on the first call.