StateSet iCommerce
If you already use Stateset ICommerce, the stateset icommerce mcp server is the piece that lets your assistant work with it directly. StateSet iCommerce.
AI agents that reason, decide, and execute—replacing tickets, scripts, and manual operations across your entire commerce stack.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
framework — neutral runtimes via @stateset/embedded/genericMCP — native clients like Claude Desktop / Cursor / Windsurf via the CLI servercreate-acp-commerce on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: DB_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of database access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Stateset ICommerce's toolset — framework, MCP — is a fair guide to whether it matches your workflow. It is maintained by stateset; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| framework | neutral runtimes via @stateset/embedded/generic |
| MCP | native clients like Claude Desktop / Cursor / Windsurf via the CLI server |
{
"mcpServers": {
"stateset-icommerce": {
"command": "npx",
"args": ["-y", "create-acp-commerce"],
"env": {
"DB_PATH": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| DB_PATH | Filesystem location the server is allowed to use. | Optional |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.