Oracle NetSuite
Captain integrates with Oracle NetSuite via the MCP (Model Context Protocol) Standard Tools SuiteApp. Once connected, Captain can search records, run SuiteQL queries, and pull financial reports directly from your NetSuite account in real-time.
What You Can Do
- Search Records — Find customers, sales orders, invoices, items, vendors, and any other NetSuite record type
- Get Record Details — Retrieve full details on a specific record by internal ID
- Run SuiteQL Queries — Execute custom SQL-like queries for analytics and complex data retrieval
- Financial Reports — Run saved reports, list and execute saved searches
Prerequisites
Before connecting, a NetSuite administrator must complete the following steps in your NetSuite account.
1. Enable Required Features
- Go to Setup > Company > Enable Features
- On the SuiteCloud tab, enable Server SuiteScript
- Under SuiteTalk, enable REST Web Services
- Under Manage Authentication, enable OAuth 2.0
- Click Save
2. Install MCP Standard Tools SuiteApp
- Go to the SuiteApps tab
- Search for MCP Standard Tools
- Click Install and wait for installation to complete
3. Set Up a Custom Role
- Go to Setup > Users/Roles > Manage Roles
- Create or edit a role with the following permissions under Permissions > Setup:
- “Log in using OAuth 2.0 Access Tokens”
- “MCP Server Connection”
- “REST Web Services” (Full)
- Assign this role to the user who will connect
4. Find Your Account ID
- Go to Setup > Company > Company Information
- Your Account ID appears at the top (e.g.,
TSTDRV1234567)
Connecting in Captain Studio
- Open Captain Studio and go to the 3rd Party Services panel
- Find Oracle NetSuite and enter your Account ID
- Click Connect — a popup will open for NetSuite login
- Log in with your NetSuite credentials and select the custom role you configured above
- Authorize the connection
Once connected, NetSuite appears as a Live Search source in your chat. Toggle it “in context” to have Captain proactively search your ERP data.
Authentication
NetSuite uses OAuth 2.0 with PKCE (public client). No client secret or environment variables are required — the connection is established entirely through the browser-based OAuth flow. Each user connects with their own credentials and role, so data access respects NetSuite’s role-based permissions.
Tokens are automatically refreshed when they expire.