Manage your Jumpseller store with AI. Products, orders, customers, and more.
Jumpseller MCP server exists for a simple reason — assistants are far more useful when they can act on Jumpseller directly instead of describing what you should do. Manage your Jumpseller store with AI. Products, orders, customers, and more.
The Jumpseller API lets you programmatically create and manage online stores. It covers:
Once Jumpseller is connected, these are the calls the assistant has available:
Stores — Create, configure, and manage online storesProducts — Full CRUD with variants, images, categories, and custom fieldsOrders — Create, update, search, and fulfill ordersCustomers — Manage customer accounts and groupsShipping — Configure shipping methods and ratesPayments — Set up payment gatewaysThemes — Apply and customize store themesWebhooks — Subscribe to store eventsArea — ToolsCategories — list_categories, create_category, delete_categoryPages — list_pages, create_page, delete_pageStore — get_store_infoBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 2 environment variables: YOUR_LOGIN_KEY, YOUR_AUTH_TOKEN. 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.
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. Jumpseller's toolset — Stores, Products, Orders and 10 more — is a fair guide to whether it matches your workflow. It is maintained by com.jumpseller; 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 |
|---|---|
| Stores | Create, configure, and manage online stores |
| Products | Full CRUD with variants, images, categories, and custom fields |
| Orders | Create, update, search, and fulfill orders |
| Customers | Manage customer accounts and groups |
| Shipping | Configure shipping methods and rates |
| Payments | Set up payment gateways |
| Themes | Apply and customize store themes |
| Webhooks | Subscribe to store events |
| Area | Tools |
| Categories | list_categories, create_category, delete_category |
| Pages | list_pages, create_page, delete_page |
| Store | get_store_info |
| Authentication | The Authentication tool exposed by this server. |
{
"mcpServers": {
"admin": {
"command": "npx",
"args": ["-y", "openmcp"],
"env": {
"YOUR_LOGIN_KEY": "your-value",
"YOUR_AUTH_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| YOUR_LOGIN_KEY | Credential the server authenticates with. | Yes |
| YOUR_AUTH_TOKEN | Credential the server authenticates with. | Yes |
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.