Sign Up

Seller2Go MCP – AI assistants for JTL-Shop

Last updated: October 25, 2026

Seller2Go MCP connects your JTL-Shop to AI assistants such as Claude, ChatGPT, Claude Code, Codex, Cursor, GitHub Copilot or Gemini. The assistant can then work in your shop directly: read figures, build landing pages with the OnPage Composer, write blog posts, create redirects, clear the cache – with the same permissions and checks as the backend.

The plugin is the server itself. It runs in your shop, on your hosting. There is no extra service and no shop data stored anywhere else.

What you can do with it

A few everyday examples:

  • “Why did revenue drop last week?” The assistant compares periods, visitors, traffic sources and abandoned carts and tells you what changed.
  • “Build me a landing page for the autumn sale.” It finds matching products, assembles a page from portlets and saves it as a draft. Nothing goes live until you say so.
  • “Customers can't get through checkout.” It checks shipping and payment methods and finds, for example, a shipping method with no payment method enabled.
  • “What is wrong with this shop?” 36 system checks, the log grouped by frequency, missing scheduled tasks, pages without meta data.
  • “Create an autumn coupon for 10 % off orders over €50.” It creates it – switched off. You enable it yourself.

Requirements

  • JTL-Shop 5.5 to 5.8
  • PHP 8.2 or newer
  • HTTPS (SSL certificate) in production
  • An AI assistant with MCP support, e.g. Claude, ChatGPT (developer mode), Claude Code, Codex, Cursor, VS Code with GitHub Copilot or Gemini CLI
  • A JTL-Shop backend account with permissions for the areas the assistant should use
  • Optional: the DC Portlets plugin. If installed, the assistant can use its 20+ building blocks in addition to the shop's core portlets.

✓ Note: For Claude and ChatGPT in the browser, your shop must be reachable from the internet. Programs on your computer (e.g. Cursor or Claude Code) can also reach a local test shop.

Installation

  1. Get Seller2Go MCP from the JTL Extension Store. Your shop must be linked to your JTL customer center so the license reaches the shop.
  2. In the shop backend, open Plugins → Plugin manager and install Seller2Go MCP. Alternatively upload the ZIP file under Upload plugin and install it afterwards.
  3. After installation you will find the plugin under Plugins → Seller2Go MCP with the tabs Start, Activity and Documentation.

The Start tab checks on its own whether AI assistants can reach your shop and shows the address your assistant needs at the top – for example:

https://your-shop.com/seller2go-mcp

✓ Note: Many hosts do not pass an assistant's login on to the shop (typical signs: “401”, “unauthorized”, or in ChatGPT “Authentication succeeded, action discovery failed”). The plugin brings its own entry point for this. If the Start tab detects the problem, it shows the matching fallback address automatically, e.g. https://your-shop.com/plugins/seller2gojtlshopmcp/mcp/rpc. Always use the address shown there.

Connecting your AI assistant

There are two ways:

  • With one click (Claude, ChatGPT, Claude Code, Codex): you only enter the address. The program sends you to your shop backend, where you see who is asking, tick what is allowed and click Allow connection.
  • With a key (Cursor, VS Code, GitHub Copilot, Gemini CLI, Windsurf, Antigravity and all others): you create an access key in the Start tab. The plugin then shows a ready-made snippet for each program, with address and key already filled in.

Claude (claude.ai or desktop app)

  1. Open the connectors in Claude (depending on the version under Settings or Customize → Connectors).
  2. Choose Add custom connector.
  3. Enter a name, e.g. “My shop”, and the address from the Start tab.
  4. Click Connect. Your shop backend opens: log in, tick what Claude may do and click Allow.

ChatGPT

  1. Open Settings → Apps & Connectors → Advanced and enable Developer mode.
  2. Under Apps & Connectors, click Create.
  3. Name, e.g. “My shop”, the address from the Start tab, authentication OAuth.
  4. Save. Your shop backend opens: log in, tick what ChatGPT may do and click Allow.

Claude Code

In a terminal, with your address:

claude mcp add --transport http seller2go-mcp https://your-shop.com/seller2go-mcp

Then start Claude Code with claude, type /mcp, select seller2go-mcp and choose Authenticate. Your shop backend opens in the browser – click Allow.

Codex

In the Codex app or IDE extension: Settings → MCP servers → Add server, type Streamable HTTP, name seller2go-mcp, address from the Start tab. Log in and click Allow in the shop backend.

On the command line, one after the other:

codex mcp add seller2go-mcp --url https://your-shop.com/seller2go-mcp

codex mcp login seller2go-mcp

Cursor, VS Code, Gemini CLI and other programs

  1. In the Start tab, under “Connected assistants”, click Create access with key.
  2. Enter a name (e.g. “Cursor on my laptop”), pick your backend account and tick what the assistant may do. Less is better – you can add more at any time.
  3. Click Create.
  4. Click your program in the list. It shows where the snippet goes and the snippet itself. Copy, paste, save.

✓ Note: The key is shown only once. Close the page only when everything is pasted. Lost it? Revoke the access and create a new one.

Features at a glance

More than 100 tools cover the areas of the backend. Each change is saved the way the backend page itself saves it – with the backend permission that page requires.

Content and OnPage Composer

  • Build landing pages, category and product pages with the OnPage Composer – as drafts, with grids, rows and columns
  • Add, move, edit and remove portlets; upload images
  • Create, edit and publish custom pages and translate them into missing languages
  • Write and publish blog posts
  • Maintain link groups, banners, sliders, boxes and the contact form

Marketing and sales

  • Create and evaluate coupons and campaigns
  • Build newsletter templates and send test mails (no sending to subscribers)
  • Edit shop emails and email reports
  • Read and moderate reviews

Statistics and analysis

  • Revenue, orders, visitors, traffic sources and bestsellers
  • Timelines and period comparisons
  • Abandoned and saved carts
  • Your customers' search queries
  • Orders and customers – only once you enable it, and shortened (see Privacy)

SEO

  • Check meta titles and meta descriptions per language
  • Maintain SEO URLs, meta data and redirects
  • Regenerate the sitemap and RSS
  • Edit robots.txt, llms.txt and .htaccess – only when enabled in the settings, every change with approval

Checkout, payment and shipping

  • Shipping methods, shipping costs, packaging, countries and postcodes
  • Payment methods and checkout options
  • Customer fields and checkout checkboxes

Design and template

  • Template settings, logo and watermark
  • Edit TPL and CSS files in the child template – only when enabled, every change with approval
  • Template checklist for redesigns (tab Activity → Checklist): per shop page desktop and mobile implementation, comparison with the design, review and done. The assistant works through it; you set review and done.

System and maintenance

  • System health with 36 checks and a shop report
  • Read and analyse the log, clear and configure the cache
  • Cron jobs, exports and export formats, maintenance mode
  • Shop settings, language variables and settings of other plugins
  • Lock a backend account in an emergency

Security and control

The plugin is built so that an assistant can never do more than the person behind it and never does anything consequential on its own.

One access belongs to one person

Every access is tied to a backend account and can never do more than that account may do in the shop. Remove a permission from the account and the access loses it with the next request. On top of that, you decide per access which areas it may use – e.g. only read statistics or only draft pages.

Approvals

The assistant does not simply carry out consequential actions. It prepares them and describes what would happen. In the Start tab under Approvals you see the action with all its details and decide. Each approval applies exactly once and expires after 24 hours.

How strict this is you set under Settings → Confirm consequential actions:

  • Always (default): every consequential action waits for you.
  • Only settings and money: content such as pages, OPC drafts, blog and redirects goes through without asking. Settings, payment methods, shipping costs, coupons, emails, design and maintenance mode still wait for you.
  • Never: the assistant carries out everything immediately. Then only the operating mode applies.

Operating mode

  • Restricted (default): always read, build drafts and edit what visitors cannot see. Anything visitors would see immediately is refused.
  • Full: all actions are allowed – with approval, as the confirmation level requires.

Log and kill switch

The Activity tab shows every call, including the read-only ones. For changes, the previous state is stored in full – your way back if something goes wrong.

Under Settings there is the switch “AI assistants may connect”. Off means off: the shop no longer answers any assistant, regardless of all accesses.

Privacy

  • Customer data is switched off by default – for customer accounts, orders, withdrawals and saved carts. Even when enabled, phone, address, date of birth and full surname are never returned; names appear as “Maria K.”, email addresses only with the domain. Payment data is not queried at all.
  • No credentials: payment provider keys, mail login, FTP or Wawi sync credentials are neither shown nor set.
  • Legal texts locked: by default the assistant cannot change terms, privacy policy, withdrawal policy or imprint.
  • Deliberate limits: no newsletter sending to subscribers, no user management, no free SQL, no plugin installation. Products and prices stay in JTL-Wawi.

✓ Note: Your shop only sends the assistant what it asks for. The assistant runs with the provider you connected – whether processing there is permitted is your decision.

Troubleshooting

  • 503: The plugin is switched off. Under Settings, turn on “AI assistants may connect”.
  • 401 or “unauthorized”: The key is wrong, revoked or expired – create a new access. Or your hosting blocks the login: use the fallback address from the Start tab.
  • 403 “not under HTTPS”: Your shop runs without https://. Enable an SSL certificate with your host.
  • “Scope … was not granted to this access”: This permission was not ticked when creating the access. Add it in the Start tab under “Connected assistants”.
  • “Account … lacks the required permissions”: Your backend account may not do this itself. Change it under User management → Groups.
  • “… is not possible in Restricted mode”: Switch to “Full” under Settings – or leave it that way on purpose.
  • “License expired” in the plugin manager: The shop cannot find a valid license. Check that the shop is linked to your JTL customer center and refresh the licenses in the backend.

Uninstalling

  1. First remove the connection in your AI programs: delete the connector in Claude or ChatGPT, or remove the seller2go-mcp entry from the configuration of Cursor, VS Code or Claude Code.
  2. To pause the plugin only: deactivate it in Plugins → Plugin manager. Accesses, settings and the log are kept; no assistant can connect.
  3. To remove it completely: in Plugins → Plugin manager, select Seller2Go MCP and choose Uninstall.

Uninstalling removes all plugin data: accesses and keys, connections, settings, pending approvals and the log. All assistants lose access immediately.

✓ Note: Whatever the assistant created or changed in the shop – pages, blog posts, coupons, redirects, settings – stays. It belongs to your shop, not to the plugin. If you want to keep the log with the state before each change, deactivate the plugin instead of uninstalling it.