> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/integrations/netsuite-mcp-connector.md).

# NetSuite MCP Connector

### Overview

The NetSuite MCP connector links Transform to NetSuite through Console.

This connection brings ERP data into Transform workflows.

It reduces manual re-entry and supports governed sync patterns.

### Key Concepts

* **MCP connector**: connection layer between Transform and NetSuite
* **OAuth 2.0**: authorization flow used to grant access securely

### How It’s Used

Use this connector when ERP data must inform work in Transform.

Common examples include employees, customers, contacts, and projects.

Console can query this data before creating or updating records.

### Benefits

* Reduces duplicate entry across systems
* Improves record accuracy through source data access
* Supports controlled sync patterns through Console
* Helps connect ERP context to Projects, Organizations, and Teammates

### Setup Steps

Before starting, confirm these prerequisites:

* NetSuite Administrator access
* The NetSuite **Account ID**
* Transform account access with permission to manage connectors
* A NetSuite role configured for OAuth 2.0 and API access

{% hint style="warning" %}
This integration uses OAuth 2.0.

A standard NetSuite Administrator role cannot be used directly.

Create or update a dedicated integration role first.
{% endhint %}

{% stepper %}
{% step %}

### Create the NetSuite integration record

In NetSuite, navigate to **Setup → Integration → Manage Integrations → New**.

Configure these values:

* **Grant Type**: `Authorization Code Grant`
* **Client Type**: `Public Client`
* **Redirect URI**: `https://app.transform.ai/api/mcp-server-connections/oauth/callback`
* **Access Token Validity**: `720`
* **Refresh Token Validity**: `720`
* **Scope**: `NetSuite AI Connector Service`

Save the integration record.

NetSuite generates a **Client ID** and **Client Secret**.

{% hint style="warning" %}
Copy the **Client ID** and **Client Secret** immediately.

NetSuite does not display the Client Secret again.

If the secret is lost, reset the integration credentials and use the new values.
{% endhint %}
{% endstep %}

{% step %}

### Configure a NetSuite role

In NetSuite, navigate to **Setup → Users/Roles → Manage Roles**.

Open the target role and confirm these capabilities:

* Access to the record types required for sync
* **OAuth 2.0 login** enabled
* **Web Services** or **REST Web Services** access enabled

If needed, update an existing integration role instead of creating a new one.

For example, an existing ERP integration role may already have the right record access.

After updating the role, assign it to the relevant NetSuite user.
{% endstep %}

{% step %}

### Create the connector in Transform

In Transform, navigate to **Account Settings → Connectors**.

Then complete these steps:

1. Select **New Connector**.
2. Set the connector type to **MCP**.
3. Enter a connector name, such as `NetSuite`.
4. Enter the **MCP Server URL** using this pattern:

```
http://<accountid>.suitetalk.api.netsuite.com/services/mcp/v1/all
```

5. Enter the **Client ID** and **Client Secret** from the integration record.
6. Save the connector.

{% hint style="info" %}
The MCP Server URL is account-specific.

Find the NetSuite Account ID under **Setup → Company → Company Information**.

It also appears in the NetSuite browser URL.
{% endhint %}
{% endstep %}

{% step %}

### Authorize the connector in Console

Open **Console** in Transform.

Then complete these steps:

1. Open **Connectors**.
2. Locate the NetSuite connector.
3. Select **Authorize**.
4. Complete the NetSuite login flow.
5. Select the OAuth 2.0-enabled role configured earlier.

A confirmation message indicates that the connection is active.
{% endstep %}

{% step %}

### Test the connection

Start with a small read-only query.

For example:

> Get one employee record from NetSuite and show the available fields. Confirm before creating anything.

Review the result before attempting broader sync actions.

Validate field names and record shape first.

Then move to larger workflows.

{% hint style="warning" %}
Use explicit confirmation language in Console prompts until the workflow is validated.

For example, include `confirm before creating anything`.
{% endhint %}
{% endstep %}
{% endstepper %}

### Troubleshooting

#### Invalid login attempt

The selected role may not have OAuth 2.0 login enabled.

The user may also be missing that role assignment.

Review the role under **Setup → Users/Roles → Manage Roles**.

#### Does not support OAuth 2

The authorization flow used a role without OAuth 2.0 login enabled.

Authorize again with the correct role, or update the existing role.

#### Client ID or Client Secret not accepted

The credentials may be incorrect.

The integration record credentials may also have been reset.

Generate new credentials in NetSuite, then update the connector in Transform.

#### Incorrect or missing MCP Server URL

Confirm the Account ID in the URL.

Remove extra spaces or characters.

Validate the Account ID in **Setup → Company → Company Information**.

#### Console returns empty or unexpected results

Start with narrower queries.

Specify the record type, field, or time range.

Validate one small sample before running a broad sync.

### Best Practices

* Use a dedicated integration role for connector access.
* Start with read-only validation before record creation.
* Keep prompts explicit when testing create or sync actions.
* Limit role access to the record types needed for the workflow.
* Assign an owner for credential rotation and connector maintenance.

### Related articles

* [Business Tools](/integrations/business-tools.md)
* [Connectors](/administration/connectors.md)
* [Console Overview and Access](broken://spaces/bO5MkvlsUXaVsGsjqKWy/pages/IHr5D4941EfyTqBdCYqy)
* [AI Tools](/integrations/ai-tools.md)

### Summary

The NetSuite MCP connector gives Console governed access to ERP data.

This supports better sync accuracy and reduces manual data entry.

After setup, use small validation queries first.

Then expand to approved sync workflows for Teammates, Organizations, and Projects.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.transform.ai/integrations/netsuite-mcp-connector.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.