NetSuite MCP
Connect NetSuite MCP to BotDojo through Oracle's NetSuite AI Connector Service, authorize it with OAuth 2.0, and control the tools agents can use.
Connect Oracle NetSuite to BotDojo through the NetSuite AI Connector Service. BotDojo treats NetSuite as a remote Model Context Protocol (MCP) Connection, discovers the tools available to the authorized NetSuite role, and applies BotDojo Connection access and approval controls to those tools.
The recommended setup uses Oracle's MCP Standard Tools SuiteApp and BotDojo's built-in NetSuite Connection.
Use a dedicated NetSuite role. The MCP Standard Tools SuiteApp can create and update records as well as read reports, saved searches, records, and SuiteQL results. Use a non-Administrator role with only the permissions the agent needs. NetSuite's Administrator role cannot authorize the AI Connector Service.
Review compliance before connecting. Oracle states that the NetSuite AI Connector Service has not been assessed for HIPAA safeguards. Do not use it to store, process, or transmit electronic protected health information (ePHI) unless your organization has independently determined that the use complies with its obligations. Review Oracle's requirements and associated risks, controls, and mitigation strategies.
Before You Start
You need:
- permission to enable NetSuite features and install SuiteApps;
- permission to create or review NetSuite integration records;
- a dedicated non-Administrator NetSuite role for the BotDojo connection;
- permission to add a Connection in the intended BotDojo project or personal workspace; and
- the NetSuite account ID used in your account-specific SuiteTalk domain.
If NetSuite does not appear under Connections → Add Connection, ask a BotDojo administrator to allow Remote MCP Connections for the project or personal workspace.
Prepare NetSuite
Enable the required features
- In NetSuite, go to Setup → Company → Enable Features.
- Open the SuiteCloud subtab.
- Enable Server SuiteScript.
- Enable OAuth 2.0.
- Under SuiteTalk (Web Services), enable REST Web Services.
- Save the changes.
Install MCP Standard Tools
- Open the SuiteApps tab.
- Search for MCP Standard Tools.
- Open the SuiteApp and select Install.
- Wait until the installation completes.
MCP Standard Tools is a managed SuiteApp. Oracle can update its tool surface over time, so refresh and review the discovered tools in BotDojo after a SuiteApp update.
Create a least-privilege role
Create a role for the NetSuite user who will authorize the Connection. BotDojo users and agents receive access separately through BotDojo Connection permissions. Under the role's Permissions → Setup subtab, add:
- MCP Server Connection;
- Log in using OAuth 2.0 Access Tokens — not the similarly named Log in using Access Tokens permission; and
- REST Web Services when the role needs the Standard Tools record operations.
Add only the record, report, saved-search, and SuiteAnalytics permissions required for the intended use case. A tool is visible only when the selected role has its required permissions, and every operation remains limited by that role.
Verify the OAuth integration record
Go to Setup → Integration → Manage Integrations and look for an integration record installed for the NetSuite AI Connector Service. If the record is Pending, an administrator must open and enable it. If no suitable record exists, create one for BotDojo with:
| NetSuite setting | Value |
|---|---|
| State | Enabled |
| Authorization Code Grant | Enabled |
| Redirect URI | https://app.botdojo.com/integrations/remotemcp/oauth_redirect |
| Public Client | Enabled |
| Dynamic Client Registration | Enabled |
| Client Name for Dynamic Client Registration | BotDojo |
| OAuth 2.0 Scope | NetSuite AI Connector Service only |
Use the BotDojo URL for your environment if you are connecting from a custom or non-production deployment. The redirect URI must match exactly.
For an AI Connector integration record, leave Token-based Authentication, Client Credentials, and the other OAuth 2.0 scopes such as REST Web Services, RESTlets, and SuiteAnalytics Connect cleared. This is separate from assigning REST Web Services permission to the NetSuite role.
Connect NetSuite In BotDojo
-
Choose where the Connection should be owned:
- For a project Connection, open the project and select Context → Connections → Add Connection.
- For a personal Connection, open Personalization → Connections and select Add beside My Connections.
-
Search for and select NetSuite.
-
Enter the account-specific NetSuite MCP endpoint:
https://<accountid>.suitetalk.api.netsuite.com/services/mcp/v1/suiteapp/com.netsuite.mcpstandardtools -
Keep OAuth - Dynamic Client Registration selected.
-
Select Connect and complete the NetSuite sign-in and consent window.
-
Choose the dedicated non-Administrator role when NetSuite asks which role to authorize.
-
Wait for BotDojo to save the Connection and discover its tools.
The SuiteApp-specific endpoint exposes only tools from MCP Standard Tools. To expose all MCP tools installed in the account, including custom tools, use:
https://<accountid>.suitetalk.api.netsuite.com/services/mcp/v1/all
Use /all only when the broader tool surface is intentional.
Review Tool Access
After authorization, open the saved NetSuite Connection and review Tools before assigning it to an agent:
- Select Refresh if tool discovery has not completed.
- Disable every tool the agent does not need.
- Set each enabled tool to Deny, Ask, or Allow.
- Prefer Ask for tools that create or update records.
- Set Default Approval to Deny for tools Oracle may add later. Use Ask only when your organization has deliberately accepted that broader default.
- Save the Connection.
- Grant the intended users and agents access, or enable the Connection in the intended workspace.
BotDojo approvals add a control around tool calls, but the NetSuite role remains the primary data-access boundary. Use a read-only NetSuite role when the agent should never write records.
Verify the Connection
- Confirm that the NetSuite Connection shows discovered tools in BotDojo.
- From an authorized workspace, run a low-risk read request such as listing saved searches or executing a bounded, read-only SuiteQL query.
- Confirm that tools marked Ask require approval.
- In NetSuite, open Setup → Integration → Manage Integrations and select the BotDojo integration record.
- Open Execution Log → AI Connector Service (MCP) and confirm the request status, user, response code, and URL path.
Troubleshooting
| Symptom | What to check |
|---|---|
| NetSuite is missing from Add Connection | A BotDojo administrator must allow Remote MCP Connections for the project or personal workspace. |
| OAuth registration fails | Confirm that the integration record is enabled, Public Client and Dynamic Client Registration are enabled, the redirect URI matches exactly, and the DCR client name is BotDojo. |
| The integration record stays Pending | A NetSuite administrator must open and enable the installed integration record. |
| NetSuite rejects the selected role | Use a non-Administrator role without full-access permissions. |
| No tools are discovered | Confirm that MCP Standard Tools is installed, the SuiteApp-specific endpoint is correct, and the selected role has the permissions required by at least one tool. |
| Access denied when listing tools | Confirm that the role can access the SuiteApp folder in the NetSuite File Cabinet. |
| A tool is missing | Review that tool's required NetSuite permissions, update the role if appropriate, then select Refresh in the BotDojo Connection. |
| A tool call fails or is rate-limited | Review the BotDojo error and the NetSuite AI Connector Service (MCP) execution log. NetSuite integration concurrency limits also apply to MCP calls. |
If the NetSuite account cannot use Dynamic Client Registration, choose OAuth - Pre-registered Client in BotDojo instead. Register the exact BotDojo redirect URI in NetSuite, then enter the integration record's client ID and any client secret required by its token authentication method.