mcp-netsuite-practice
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-netsuite-practice How much stock do we have for SKU ASAFE-BARRIER-01?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP NetSuite Practice
Python MCP server that exposes read-only NetSuite tools for agents such as Claude Desktop or Claude Code. It lets an LLM query warehouse stock and order status without putting API keys in the client.
Tool | Arguments | Description |
|
| Available units for a SKU in warehouse |
|
| Current status of an order |
| (none) | Admin-only mock catalog reload (RBAC demo) |
NetSuite access goes through a stable client interface. Local development uses a mock with sample inventory data; the same interface can later target a real sandbox via environment variables.
Product specification: project.md.
Agent quality harness: AGENTS.md (also CLAUDE.md).
Stack
Python 3.12+
Official
mcpSDK (stdioand HTTP/SSE)FastAPI + Uvicorn for remote transport
OAuth2 authorization-code + PKCE (demo IdP) and JWT bearer auth
Pydantic / pydantic-settings for schemas and config
Docker, Kubernetes manifests, Terraform module for cluster deploy
Related MCP server: MCP API Tool Demo
Architecture
flowchart TD
Agent[Agent: Claude Desktop / Claude Code]
OAuth[OAuth2 PKCE demo IdP]
MCP[MCP Server FastAPI SSE]
RBAC[RBAC by role]
Tools[Tools: stock / order / admin]
Schemas[Pydantic schemas]
Client[NetSuite client interface]
Mock[Mock data]
Sandbox[NetSuite sandbox]
Agent -->|stdio local| MCP
Agent -->|HTTP SSE + Bearer JWT| MCP
Agent --> OAuth
OAuth -->|access token| Agent
MCP --> RBAC
RBAC --> Tools
MCP --> Schemas
Tools --> Client
Client --> Mock
Client -.-> SandboxThe MCP server exposes typed tools to the agent. Remote mode validates a JWT from the PKCE flow and enforces least privilege (for example sales cannot call admin_reload_catalog). Tools call a NetSuite client interface so the protocol layer stays decoupled from the ERP.
How to use
Requirements: Python 3.12+, uv.
Local stdio (Claude Desktop / Claude Code)
uv sync
uv run python -m mcp_netsuite_practice{
"mcpServers": {
"netsuite-practice": {
"command": "uv",
"args": [
"--directory",
"C:/Users/antonio/Desktop/MCP-netsuite-practice",
"run",
"python",
"-m",
"mcp_netsuite_practice"
]
}
}
}Example prompts:
“How much stock do we have for SKU BARRIER-01?”
“What is the status of order SO-10042?”
Remote SSE (FastAPI)
cp .env.example .env
uv run python -m mcp_netsuite_practice --transport sseEndpoints:
Path | Purpose |
| Liveness/readiness |
| PKCE authorize (demo login via query params) |
| Exchange code + |
| MCP SSE transport |
| MCP SSE message endpoint |
Obtain a token (PKCE), then call MCP with Authorization: Bearer <token>.
Roles: sales, ops, admin. Sales may use stock/order tools only.
Docker
docker compose up --buildKubernetes / Terraform
Manifests:
deploy/k8s/Terraform module:
deploy/terraform/(see its README)
Variable | Purpose |
|
|
| Issuer / resource base URL for OAuth metadata |
| HS256 signing secret |
| Public PKCE client id |
| Enable bearer auth on SSE ( |
|
|
uv run pytestAvailable Tools
2 toolsget_order_statusA
Return the current status of a global sales order.
Use when the user asks about an order, shipment progress, or fulfillment state for an order id (for example SO-10042).
Inputs: order_id (required). Returns: Current status of a sales order.
get_stock_levelA
Return available warehouse units for an A-SAFE product SKU.
Use when the user asks about inventory, stock on hand, or availability for a specific SKU (for example ASAFE-BARRIER-01).
Inputs: sku (required). Returns: Available warehouse stock for a single SKU.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools target completely distinct domains: inventory (stock levels by SKU) and order fulfillment (order status by ID). There is no overlap in purpose or arguments, so an agent can easily select the correct tool.
Both tools follow a consistent get_noun_noun pattern (get_stock_level, get_order_status), using snake_case and a clear verb prefix. The naming is predictable and uniform.
With only two tools, the server feels minimal. For a practice server this may be intentional, but it borders on too sparse to represent a meaningful integration, though each tool covers a distinct, useful query.
The tool surface only provides single-record lookups (by SKU and order ID) with no list, create, update, or delete operations. This is a significant gap for an ERP domain like NetSuite, where typical workflows require broader coverage.
Related MCP Connectors
MCP server for SkuVault — products, inventory, sales, purchase orders and stock adjustments.
MCP server for MarketTime — wholesale orders, customers, catalog and shipment tracking.
An MCP server that provides read access to your cloud storage providers, bank accounts and more.
Related MCP Servers
- AlicenseAqualityCmaintenanceA Model Context Protocol (MCP) server providing access to NetSuite data through OAuth 2.0 with PKCE authentication. Works seamlessly with any MCP-compatible client including Claude Code, Cursor IDE, and Gemini CLI.241 npm22MIT
- FlicenseNot gradedqualityDmaintenanceDemo MCP server that exposes order and customer data as read-only tools for AI assistants, simulating a business API or internal data source.-
- AlicenseNot gradedqualityDmaintenanceA lightweight, local inventory-intelligence MCP server that enables querying structured inventory schemas with read-only, zero-config tools for stock levels, velocity metrics, and purchase orders.4 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server that provides mock APIs and deterministic seed data for ERP/OMS, WMS, and CRM systems, enabling supply chain data exploration and integration testing.-