Most people who need something from NetSuite are not NetSuite users: a sales manager wants a customer’s open invoices, operations wants the status of a sales order, a founder wants to know which vendors are waiting on payment. Each question is a license, a saved search or a message to finance.
Oracle offers its own NetSuite AI connector for one NetSuite account. Teams that already use Claude or ChatGPT for everything else also want the assistant to see NetSuite next to their CRM and inbox, under one set of controls.
What has to be true first
- Only the record types the assistant needs, read only by default.
- No NetSuite tokens pasted into a prompt or a config file.
- IT can see who is using it, and every call is recorded.
- The same setup works for Claude, ChatGPT, Cursor and in-house agents.
How engini makes it governable
You connect NetSuite once with token-based authentication, using a role your administrator sets up, and create an engini MCP server that exposes only the tools you choose, for example get records on invoices, customers and sales orders. People add it to Claude, ChatGPT or Cursor and sign in through engini over OAuth, with no key to copy. engini shows who uses each MCP server and records every run under the user who triggered it. For in-house agents, a toolset does the same scoping over the SDK, CLI or REST API, enforced on the server.
NetSuite




