Manage your Online Store with AI

Your online store can now be managed by AI. With Jumpseller’s MCP integration, AI assistants connect directly to your store and handle the work for you. Add products, process orders, organize your catalog, look up customers, get business insights, and more. You talk, the AI acts.

“Add a new product called Summer Dress at $49.99 with sizes S, M, L, upload this image, and put it in the Women’s category”

One sentence. The AI creates the product, sets up the variants, uploads the image, and assigns the category.

This is more than a shortcut. It opens the door to agentic commerce: AI agents that work on your store around the clock. They can monitor your inventory, suggest price changes based on demand, reorganize your catalog for seasonal campaigns, or process batches of orders while you focus on growing your business.

Whether you are a merchant looking to save hours of admin work, or a developer building the next generation of e-commerce automation, the Jumpseller MCP server gives you the tools to make it happen.

Compatible Platforms

Jumpseller works with all major AI platforms:

• Claude (claude.ai, Desktop and Claude Code)
• ChatGPT
• OpenAI Codex
• Gemini CLI
• Grok (Grok CLI and the xAI API)
• Meta Muse (custom connector and Muse Code)
• Cursor
• Devin Desktop (formerly Windsurf)
• GitHub Copilot (VS Code)
• Any tool that supports the Model Context Protocol (MCP)

What Can AI Do for Your Store?

Run your daily operations. Adding products, updating prices, checking order status, fulfilling shipments. Tasks that take minutes in the admin panel take seconds with AI.

Manage in bulk with natural language. Instead of editing products one by one, say “reduce the price of all summer products by 20%” and the agent updates every single one.

Get insights and recommendations. Ask “which products have been out of stock for more than a week?” or “show me the top 5 customers by order count” and get answers instantly.

Automate repetitive workflows. Build agents that process orders every morning, send inventory alerts when stock runs low, or prepare your catalog for a sale event, all without manual intervention.

Improve your catalog with AI. Let the AI review your product descriptions, suggest missing categories, identify products without images, or flag inconsistent pricing across variants.

What is MCP?

The Model Context Protocol (MCP) is an open standard created by Anthropic that lets AI agents use tools on external services. Think of it as a universal plug that connects any AI assistant to your Jumpseller store.

When you connect your store via MCP, the AI agent can see all available tools (list products, create orders, search customers, etc.) and use them intelligently to accomplish what you ask.

Jumpseller joins platforms like Shopify, Stripe, and PayPal in offering MCP support, putting your store at the forefront of AI-powered commerce.

Agentic E-commerce

Beyond interactive use, the Jumpseller MCP enables agentic e-commerce: AI agents that manage your store autonomously. Developers can build agents that:

• Monitor inventory and automatically reorder when stock runs low
• Process incoming orders and update tracking information without manual intervention
• Generate product descriptions and organize categories based on your catalog
• Respond to customer inquiries by looking up order status and account details
• Run scheduled tasks like price adjustments, seasonal catalog changes, or promotional campaigns

Using the MCP tools, any developer can build custom agents with Claude Agent SDK, LangChain, or any framework that supports MCP. The agent connects to https://mcp.jumpseller.com and has access to all 27 store management tools.

Connect Your Store

Pick the AI tool you use below. In Claude, ChatGPT, Claude Code and Codex you only need the server address: you sign in with your Jumpseller account, choose the store and approve access. There are no keys to copy.

Server URL: https://mcp.jumpseller.com

Claude

Connectors you add on claude.ai are also available in the Claude desktop and mobile apps.

1. Open the Jumpseller Store connector in the Claude directory and click Connect to Claude.

   

2. A Jumpseller page opens: sign in, choose your store and click Authorize.

3. Claude shows the Jumpseller tools. Tools that only read your store run straight away; Claude asks you before using a tool that changes something.

   

Now ask Claude about your store in any chat:

On Team and Enterprise plans, an owner of the Claude organisation may need to add the connector first.

Add it as a custom connector

To connect more than one store at the same time, add Jumpseller as a custom connector instead, once per store (see Managing Multiple Stores).

1. Open Customize → Connectors, click Add and choose Add custom connector.

   

2. Enter a Name, such as Jumpseller, and the URL https://mcp.jumpseller.com. Click Continue.

   

3. Keep Sign in now. Under OAuth client, choose Use Claude’s published identity: Jumpseller recognises Claude on its own, so there is no client ID to enter. Click Add.

   

4. Click Connect. A Jumpseller page opens: sign in, choose your store and click Authorize.

ChatGPT

1. Open Plugins in the sidebar, click Add and choose Add custom MCP server. If you don’t see this option, turn on Developer mode in Settings → Security and login.

   

2. Enter a Name and the URL https://mcp.jumpseller.com, and keep OAuth as the authentication. ChatGPT finds Jumpseller’s sign-in settings by itself, so leave Advanced OAuth settings as they are. Tick I understand and want to continue and click Create as a plugin.

   

3. Click Continue to …. A Jumpseller page opens: sign in, choose your store and click Authorize.

   

4. In a chat, click +, pick the plugin, and ask your question.

   

You can also use the Jumpseller GPT, which signs in the same way.

Claude Code

Add the server, then sign in from inside Claude Code:

claude mcp add --transport http jumpseller https://mcp.jumpseller.com

Run /mcp, select jumpseller and choose Authenticate. Your browser opens the Jumpseller sign-in; choose your store and click Authorize.

The AI Toolkit plugin adds this server for you, together with skills for the Jumpseller API, Liquid themes and CLI.

OpenAI Codex

Add the server to ~/.codex/config.toml:

[mcp_servers.jumpseller]
url = "https://mcp.jumpseller.com"

Then run codex mcp login jumpseller and approve access in the browser window that opens.

Gemini CLI

Gemini CLI connects with an API token. Install the Jumpseller extension, which already declares the server, and follow the Gemini CLI steps in the AI Toolkit.

Grok

Grok connects with an API token.

Grok CLI: add the server once. The single quotes keep the variable names in Grok’s configuration, and Grok reads JUMPSELLER_LOGIN_KEY and JUMPSELLER_AUTH_TOKEN from your environment each time it starts:

grok mcp add --transport http jumpseller https://mcp.jumpseller.com \
  --header 'X-LOGIN-KEY: ${JUMPSELLER_LOGIN_KEY}' \
  --header 'X-AUTH-TOKEN: ${JUMPSELLER_AUTH_TOKEN}'

Run /mcps in Grok to check that jumpseller is connected.

xAI API: add Jumpseller as a remote MCP tool in the tools of a request to https://api.x.ai/v1/responses:

{
  "type": "mcp",
  "server_url": "https://mcp.jumpseller.com",
  "server_label": "jumpseller",
  "headers": {
    "X-LOGIN-KEY": "YOUR_LOGIN_KEY",
    "X-AUTH-TOKEN": "YOUR_AUTH_TOKEN"
  }
}

Grok’s web and mobile apps can’t connect yet: Jumpseller’s sign-in currently works with Claude and ChatGPT only.

Meta Muse

Muse app (custom connector): in a Muse chat, ask Muse to create a custom connector for Jumpseller using the Jumpseller REST API, and enter your Login Key and Auth Token when Muse asks for them in its secure credentials prompt. Muse builds this connector itself on the REST API, so it doesn’t use the MCP tools listed below, and Meta doesn’t review custom connectors. Custom connectors are only available where Muse is offered.

Muse Code: add Jumpseller to the mcp_servers block of your Muse Code settings file. Muse Code reads JUMPSELLER_LOGIN_KEY and JUMPSELLER_AUTH_TOKEN from your environment:

{
  "mcp_servers": {
    "jumpseller": {
      "transport": "streamable_http",
      "url": "https://mcp.jumpseller.com",
      "headers": {
        "X-LOGIN-KEY": "${JUMPSELLER_LOGIN_KEY}",
        "X-AUTH-TOKEN": "${JUMPSELLER_AUTH_TOKEN}"
      }
    }
  }
}

Run /mcp in Muse Code to check that jumpseller is connected.

Cursor, Devin Desktop, GitHub Copilot and other tools

These tools connect with an API token. The same configuration works in all of them; only the file changes:

• Cursor: .cursor/mcp.json in your project root
• Devin Desktop (formerly Windsurf): ~/.config/devin/mcp_config.json (%APPDATA%\devin\mcp_config.json on Windows)
• GitHub Copilot (VS Code): your settings.json, under "mcp": { "servers": { … } }

{
  "mcpServers": {
    "jumpseller": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.jumpseller.com/",
        "--header", "X-LOGIN-KEY:YOUR_LOGIN_KEY",
        "--header", "X-AUTH-TOKEN:YOUR_AUTH_TOKEN"
      ]
    }
  }
}

Any MCP client that supports the Streamable HTTP transport can connect the same way. It discovers the tools through tools/list.

Authentication

Sign in with Jumpseller (OAuth)

This is how Claude, ChatGPT, Claude Code and Codex connect: you sign in with your Jumpseller account and the AI tool receives a token of its own. Sign-in on the MCP server is for AI assistants; third-party apps and integrations use the REST API with OAuth 2 instead.

The connection acts as the person who signed in, so it can only use what both of these allow:

• The scopes the AI tool requested:
  • read_products, write_products for product management
  • read_orders, write_orders for order management
  • read_customers for customer access
  • read_categories, write_categories for category management
  • read_pages, write_pages for page management
  • read_store for store information
• The permissions of that person’s account in the store, set in Accounts. An account that can only view orders gets a connection that can only read orders.

Changing an account’s permissions applies to its connections right away, and removing the account from the store disconnects them. To disconnect an AI tool yourself, go to Account → Preferences, click your user name and use Revoke under Connected Apps.

Only accounts that belong to the store can connect it. If Claude or ChatGPT asks you to sign in to Jumpseller again, sign in once more: that is how older connections move to your own account.

API Token

For tools that cannot sign in, such as scripts, CI jobs, Cursor or Devin Desktop.

1. In your Jumpseller Admin, go to Account → Preferences, then click on your user name
2. Scroll down to the API and MCP section
3. Copy your Login Key and Auth Token
4. Send them as HTTP headers on every request:
   • X-LOGIN-KEY
   • X-AUTH-TOKEN

API tokens have full access to all store operations based on your account permissions. Keep them private: anyone who has them can manage your store.

Managing Multiple Stores

Every connection belongs to one store. An API token is issued by a single store, and a sign-in is granted to whichever store you chose when you approved it. The store cannot be changed from inside a conversation.

So if you run more than one Jumpseller store, you need one connection per store. How you set that up depends on the tool.

Give each store its own URL

Alongside the shared address, every store has a server URL of its own:

https://mcp.jumpseller.com/s/STORE-CODE

STORE-CODE is your store’s Jumpseller address, the part before .jumpseller.com. You can read it from the address bar of your admin panel, and it stays the same even if you use a custom domain.

Two things follow from this. AI tools identify a connection by its URL, so giving each store a different one lets you keep several stores connected at the same time instead of switching between them. And a connection made this way is tied to the store in the URL: if it is ever authorized with a different store’s account, it stops and tells you, instead of quietly making changes in the wrong store.

On Claude and ChatGPT

Add one connector (Claude) or plugin (ChatGPT) per store, each pointing at that store’s own URL. Follow the Claude custom connector or ChatGPT steps, but use https://mcp.jumpseller.com/s/STORE-CODE as the URL and give each one a name you will recognise, such as “Jumpseller — Coffee Shop”.

Sign out before authorizing the second one. Go to accounts.jumpseller.com/accounts/sign_out after adding it and before approving it. The authorization uses whatever Jumpseller session you already have open, so without this step you are never asked which store you want, and the second store is connected to the account you already had signed in. When that happens the connection refuses to work and tells you the credentials are for a different store: remove it, sign out, and add it again.

If you point both at the shared https://mcp.jumpseller.com address instead of the per-store one, claude.ai refuses the second with “A server with this URL already exists”: it identifies a connector by its URL, so the two need different addresses.

The Jumpseller GPT connects to one store at a time and its address cannot be changed. To switch stores, sign out at the link above, open the GPT again and sign in with the store you want.

Claude Code and Codex

Add one server per store, each with its own name and URL, and sign in to each once:

claude mcp add --transport http jumpseller-coffee-shop https://mcp.jumpseller.com/s/coffee-shop
claude mcp add --transport http jumpseller-bookstore https://mcp.jumpseller.com/s/bookstore

Both stores are then available at once, and you tell the agent which one you mean: “In the coffee shop, mark order 1042 as paid.”

Cursor, Devin Desktop and other tools with API tokens

Generate an API token in each store’s admin panel and declare one server per store:

{
  "mcpServers": {
    "jumpseller-coffee-shop": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.jumpseller.com/",
        "--header", "X-LOGIN-KEY:COFFEE_SHOP_LOGIN_KEY",
        "--header", "X-AUTH-TOKEN:COFFEE_SHOP_AUTH_TOKEN"
      ]
    },
    "jumpseller-bookstore": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.jumpseller.com/",
        "--header", "X-LOGIN-KEY:BOOKSTORE_LOGIN_KEY",
        "--header", "X-AUTH-TOKEN:BOOKSTORE_AUTH_TOKEN"
      ]
    }
  }
}

What You Can Do

The MCP server provides 27 tools organized by area:

Products (6 tools)

Create, update, search, and delete products. Includes full support for variants (sizes, colors), images, and categories.

Orders (4 tools)

View orders, search by customer or product, update order status, and add shipping tracking information.

Customers (3 tools)

Look up customers by name or email, view their contact details and addresses.

Categories (3 tools)

Manage your product categories and organize your catalog.

Pages (6 tools)

Create and manage store pages like About, Contact, and Policies.

Store (1 tool)

Images (1 tool)

Small images can be sent to the agent directly. Larger ones (over roughly 7 MB) need prepare_upload, which returns a temporary link to upload the file straight to storage. The agent handles this for you.

Help and Navigation (3 tools)

For anything the tools above cannot do, the agent can look up how to do it in the admin panel instead of guessing.

Real-World Examples

Add products faster

“Create 5 products for a coffee shop: Espresso at $3, Latte at $4.50, Cappuccino at $4.50, Americano at $3.50, and Mocha at $5. All with sizes Small and Large. The Large size costs $1 more.”

The agent creates all 5 products with 2 size variants each, adjusting prices automatically.

Process orders efficiently

“Show me all pending orders from this week. Mark the ones from Portugal as paid and add tracking number PT123456 from CTT.”

The agent searches orders, filters by country, and updates each one with the status and tracking info.

Organize your catalog

“Create a category called ‘Black Friday Deals’ and move all products priced over $50 to it”

The agent creates the category, searches for matching products, and reassigns them.

Quick business insights

“How many products do I have? How many are out of stock?”

The agent lists products, counts them, and identifies which ones have zero stock.

Rate Limits

The MCP server allows 100 requests per minute per account. This is more than enough for interactive AI sessions. If you exceed this limit, you’ll receive a 429 Too Many Requests response.