NetSuite MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETSUITE_CLIENT_ID | Yes | Your OAuth client ID | |
| NETSUITE_ACCOUNT_ID | Yes | Your NetSuite account ID | |
| OAUTH_CALLBACK_PORT | No | OAuth callback port (optional, default: 8080) | 8080 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| netsuite_authenticateA | Authenticate with NetSuite to access MCP tools. Required before using any NetSuite tools. If NETSUITE_ACCOUNT_ID and NETSUITE_CLIENT_ID environment variables are set, they will be used automatically. |
| netsuite_logoutA | Clear NetSuite authentication session |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have distinctly opposite purposes: authenticate vs logout. There is no overlap or ambiguity.
Both tools follow a consistent verb_noun pattern with the 'netsuite_' prefix, e.g., netsuite_authenticate and netsuite_logout.
The server only provides authentication tools, which is too narrow for a 'NetSuite MCP Server'. A typical integration would require many more tools for CRUD operations.
The tool set is severely incomplete; it lacks any tools for actual NetSuite data operations like reading, writing, or searching records, making it practically unusable for real tasks.