Model Context Protocol server for Swell e-commerce platform integration with AI assistants
Model Context Protocol server for Swell e-commerce platform integration with AI assistants. Exposed over MCP by the swell mcp mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
A Model Context Protocol server that integrates AI assistants with Swell's e-commerce platform. Built on a production-ready TypeScript foundation, it provides comprehensive access to Swell stores for product management, order processing, and customer management through both CLI and MCP tool interfaces.
Model Context Protocol (MCP) is an open standard for securely connecting AI systems to external tools and data sources. This server implements the MCP specification to provide AI assistants with comprehensive access to Swell's e-commerce platform, enabling intelligent store management and customer service automation.
Installation goes through your MCP client rather than a global install: point it at swell-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Everything the assistant can do here goes through one of these:
swell_list_products — List products with filtering and paginationswell_get_product — Get detailed product informationswell_search_products — Search products with multiple criteriaswell_check_inventory — Check product inventory levelsswell_list_orders — List orders with filtering optionsswell_get_order — Get detailed order informationswell_update_order_status — Update order statusswell_list_customers — List customers with search capabilitiesswell_get_customer — Get detailed customer informationswell_search_customers — Search customers with multiple criteriaPurpose — MCP tool definitions that AI assistants can invokeImplementation — Zod schema validation with structured responsesYou will need 5 environment variables: DEBUG, SWELL_STORE_ID, SWELL_SECRET_KEY, TRANSPORT_MODE, PORT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
claude_desktop_config.json: Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Swell MCP's toolset — swell_list_products, swell_get_product, swell_search_products and 11 more — is a fair guide to whether it matches your workflow. It is maintained by devkindhq; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Swell MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| swell_list_products | List products with filtering and pagination |
| swell_get_product | Get detailed product information |
| swell_search_products | Search products with multiple criteria |
| swell_check_inventory | Check product inventory levels |
| swell_list_orders | List orders with filtering options |
| swell_get_order | Get detailed order information |
| swell_update_order_status | Update order status |
| swell_list_customers | List customers with search capabilities |
| swell_get_customer | Get detailed customer information |
| swell_search_customers | Search customers with multiple criteria |
| Purpose | MCP tool definitions that AI assistants can invoke |
| Implementation | Zod schema validation with structured responses |
| Example | swell_list_products tool with filtering and pagination options |
| Pattern | Define schema → Validate args → Call controller → Format MCP response |
{
"mcpServers": {
"swell-mcp": {
"command": "npx",
"args": ["swell-mcp"],
"env": {
"DEBUG": "false",
"SWELL_STORE_ID": "your_store_id",
"SWELL_SECRET_KEY": "your_private_token"
},
"disabled": false
}
}
}Configuration as documented by the project. Restart the client after saving.
claude_desktop_config.json: | Variable | Description | Required |
|---|---|---|
| DEBUG | Configuration value read at startup. | Optional |
| SWELL_STORE_ID | Configuration value read at startup. | Optional |
| SWELL_SECRET_KEY | Credential the server authenticates with. | Yes |
| TRANSPORT_MODE | Configuration value read at startup. | Optional |
| PORT | Configuration value read at startup. | Optional |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.