Stateset MCP Server

What is Stateset MCP Server?

A Model Context Protocol server that provides integration with the StateSet API, enabling LLMs to interact with issue operations, orders, fulfillment, inventory, financial records, and customer data. It is intended for developers using MCP-compatible AI assistants to manage StateSet workflows.

How to use Stateset MCP Server?

Set the required environment variables (STATESET_API_KEY, optionally STATESET_BASE_URL, REQUESTS_PER_HOUR, API_TIMEOUT_MS), install dependencies with npm install, and start the server using npm start. The server exposes a set of MCP tools (e.g., stateset_create_order, stateset_list_products) grouped by domain.

Key features of Stateset MCP Server

• Full CRUD tools for orders, sales orders, and RMAs
• Fulfillment and production tools (shipments, work orders, BOMs)
• Inventory and product management (create, update, delete, get)
• Financial tools for invoices, payments, and cash sales
• Customer management (create, update, delete, get)
• Listing operations for all major entities and API metrics

Use cases of Stateset MCP Server

• Automating order processing and returns management via chat
• Creating and tracking fulfillment orders and shipments
• Managing inventory levels and product catalogs through AI
• Generating invoices and recording payments from conversation
• Querying customer records and sales order lists on demand

FAQ from Stateset MCP Server

What environment variables are required?

STATESET_API_KEY is required; STATESET_BASE_URL (defaults to https://api.stateset.io/v1), REQUESTS_PER_HOUR (default 1000), and API_TIMEOUT_MS (default 10000) are optional.

How does the server handle network errors?

Failed requests due to network or server errors are automatically retried up to three times with exponential backoff.

What runtime and dependencies are needed?

Node.js and npm are required. Install dependencies with npm install and start with npm start.

Where does the data live?

Data is managed through the StateSet API – the server proxies requests between the LLM and the API; no local data storage is provided.

What transport and authentication does the server use?

It uses the MCP protocol over stdio. Authentication is via the STATESET_API_KEY environment variable passed to the StateSet API.