One sentence can create a product, set up its variants, upload an image and file it under a category, and the same tools are what an agent uses to work through orders on a schedule. Running more than one store means one connection per store: the store is fixed by the credentials, and cannot be switched inside a conversation.
Jumpseller's hosted MCP server at https://mcp.jumpseller.com. It gives an AI client the store-management surface of a Jumpseller shop over Streamable HTTP, with tools auto-discovered through tools/list.
- 27 store management tools, covering products, orders, customers, categories, pages and store information
- Bulk changes stated once instead of edited one product at a time — a price cut across a whole seasonal set, for example
- Catalog and customer questions answered against live data: what has been out of stock for a week, who orders most
- A per-store URL at https://mcp.jumpseller.com/s/STORE-CODE, so more than one store stays connected at the same time
- A connection made on a store URL that stops and tells you if it is ever authorized with a different store's account
Either a store API token — the Login Key and Auth Token from Admin under Account, Preferences, in the API and MCP section, sent as the X-LOGIN-KEY and X-AUTH-TOKEN headers — or OAuth 2.0 for an app acting on a merchant's behalf. OAuth tokens carry named scopes such as read_products, write_orders and read_customers, and reach only what both the app and the merchant approved. Transport is Streamable HTTP and the server is stateless, so each request stands on its own.
One command plus a key — npx -y mcp-remote https://mcp.jumpseller.com/ --header X-LOGIN-KEY:YOUR_LOGIN_KEY --header X-AUTH-TOKEN:YOUR_AUTH_TOKEN, then supply credentials