Unchained MCP Server

Unchained Engine. Exposed over MCP by the unchained mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Unchained Engine is a modular, API-first e-commerce platform built as a monorepo with npm workspaces. It provides a complete solution for building custom e-commerce applications with GraphQL APIs, extensible plugin architecture, and support for modern use cases like subscriptions, quotations, and tokenized products.

Its toolset

Everything the assistant can do here goes through one of these:

• Package — Description
• Prerequisites — The Prerequisites tool exposed by this server
• Infrastructure — The Infrastructure tool exposed by this server
• Extensions — The Extensions tool exposed by this server
• Examples — The Examples tool exposed by this server
• Payment — The Payment tool exposed by this server
• Delivery — The Delivery tool exposed by this server
• Pricing — The Pricing tool exposed by this server
• Workers — The Workers tool exposed by this server
• Events — The Events tool exposed by this server
• Commands — The Commands tool exposed by this server
• Testing — The Testing tool exposed by this server

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration

• Node.js >=22 (see .nvmrc) - MongoDB 4.4+ (or use MongoDB Memory Server for development)

When to reach for it

Plenty of payments and commerce 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. Unchained's toolset — Package, Prerequisites, Infrastructure and 10 more — is a fair guide to whether it matches your workflow. It is maintained by unchainedshop; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Unchained.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the unchained mcp server does with a few real requests.