NetSuite overview
Connect NetSuite to search indexed records in Glean and optionally use live NetSuite tools. New setup configures indexing first, connects MCP tools if you choose, and lets you review access before starting the crawl.
Compare indexing and live tools
Indexing and Model Context Protocol (MCP) tools use separate NetSuite integrations and credentials:
| Capability | Indexing | MCP tools |
|---|---|---|
| Purpose | Search NetSuite records indexed in Glean | Retrieve live data or perform operations through NetSuite's MCP server |
| Authentication | Machine-to-machine OAuth with a client ID, certificate ID, certificate, and private key | Separate OAuth client ID and secret, followed by each user's authorization |
| Permissions | NetSuite roles and segment restrictions | The authorizing user's non-admin NetSuite role and record and field permissions |
| New setup | Required | Optional |
| Account | The account entered during indexing setup | In New setup, the same account and environment saved for the connector |
Existing connectors and existing standalone MCP connections keep their original setup flows. To add a connection, follow the setup page shown in Glean. See Choose your NetSuite setup.
Understand indexed content
The search integration indexes customers, vendors, supported transactions, and transaction line items. It also retrieves identity and permission data to enforce access in Glean. Permission data does not appear as searchable content.
Full and incremental crawls update indexed content. Changes become searchable after Glean crawls and indexes them. See Supported objects and data and Crawling strategy.
Understand permissions
Glean applies NetSuite role-based access and segment restrictions to indexed results. Excluding a role from indexing also removes that role from the permission data Glean retrieves. See Permissions and security.
MCP uses each user's own NetSuite authorization. Users need an eligible non-admin role with the MCP permissions and access to the records and fields they use. NetSuite does not allow the Administrator role, or roles with full access to its features, to authorize the AI Connector Service.
The REST Web Services account feature and role permission are separate from the OAuth scope on the MCP integration record. The MCP integration uses only the NetSuite AI Connector Service scope (mcp). See NetSuite MCP for role permissions and tool controls.
Account and setup limits
Keep these constraints in mind:
- New setup requires indexing configuration, even if you start from Tools and only need MCP tools.
- In New setup, MCP uses the indexing account and environment. Once the connector has a linked MCP server, create a separate connector to use another account or environment.
- Skipping MCP does not skip indexing. Deferring the crawl does not remove the indexing configuration.
- Existing standalone MCP connections retain their separate setup and do not require an indexing connector.
For indexing volume limits, see Limitations.