Announcements

Themeart MCP: A New AI Interface for JTL-Shop

Author

Studio Team

Date Published

Themeart GmbH has released an MCP interface for JTL-Shop, giving AI assistants and AI agents direct, permissioned access to selected parts of a shop's backend. Instead of an admin copying numbers out of the backend for an AI tool to summarise, the AI can now read shop data and, where explicitly allowed, act on it directly — publishing a blog post, checking stock coverage, clearing a cache, moderating a review — through a standard protocol that tools like Claude already speak.

In short: Themeart MCP is an MCP server built directly into JTL-Shop as a plugin — no separate hosting, no extra process. It exposes blog, pages, analytics, reviews, coupons, inventory, shipping, redirects, logs, cache and maintenance mode as modules an AI assistant can query or act on, each independently switchable. Write and delete actions are off by default, customer data is off by default, and every change made through MCP is logged in the shop's Activity area with an admin-only undo.

What Themeart MCP Actually Exposes

The interface is organised into modules, and each one can be switched on or off independently of the others. Depending on which are enabled, a connected AI assistant can:

  • Blog. Read, create, edit, delete and publish posts and categories.
  • Custom pages. Read, create and edit pages and their meta data.
  • Analytics. Query revenue, orders, visitors, conversion rate, search terms, entry pages and other shop metrics.
  • SEO. Check meta titles, meta descriptions and keywords on custom pages.
  • Reviews. List, approve and delete product reviews.
  • Coupons. List existing coupons and create new ones.
  • Inventory. Read stock levels globally and per warehouse.
  • Shipping. Check shipping-class coverage per destination country.
  • Redirects, logs, cache and maintenance mode. List and remove redirects, read and manage the shop log, clear the object and template cache, and read or toggle maintenance mode.
  • Shop status. Surface key shop information and recent setting changes.
  • Customers. Read customer accounts and order history — disabled by default, separate from every other module.

The practical shift is that recurring backend work — drafting a blog post, checking why search rankings dropped, seeing which shipping class is missing coverage for a country, clearing a stale cache after a template change — no longer has to be reconstructed by hand from data pulled out of the shop. The AI works against the shop directly, inside whatever boundaries have been set.

Permissions Are Granular, and Conservative by Default

Every module above is an independent switch, and within a module, read access and write access — create, edit, delete, publish — are separate permissions. An admin can enable an AI assistant to read blog posts and analytics while leaving every create, edit, delete and publish action switched off. Write and delete access are disabled by default across the board, and two areas get an extra layer of caution: customer data and shop status are both switched off out of the box, regardless of what else is enabled, because they carry more risk than a blog draft or a cache flush.

Every Change Is Logged, and the Undo Stays With You

Any write action triggered through MCP is recorded in the JTL-Shop Activity area, showing when the action ran and what it changed. For many changes an undo option is available directly from that log — but reverting is deliberately kept as a step the shop administrator takes, not something the AI can trigger on its own. An assistant can create, edit or publish within its granted permissions; rolling a change back stays a human decision.

No Separate Server to Run

Themeart MCP is not a client that talks to some other MCP backend — it is the MCP server, installed as a JTL-Shop plugin. There is no separate process to deploy or host. The connection runs over Streamable HTTP through a protected endpoint secured with an API key, and access can be further restricted with an IP allowlist. For a shop already running JTL-Shop, this is a plugin install, not an infrastructure project.

Works With Claude and Other MCP-Compatible Assistants

Because it speaks the Model Context Protocol rather than a proprietary API, the interface works with any MCP-capable client — Claude, the JTL-Shop AI, or other agent frameworks that support MCP. The shop becomes a controllable data and work environment for whichever assistant is connected, governed by the same permission set regardless of which client is asking.

Frequently Asked Questions

Do I need to host or run anything myself?

No. It ships as a JTL-Shop plugin and runs the MCP server itself. There is no separate process, container or hosting to set up beyond installing the plugin.

Can a connected AI change things in my shop without me finding out?

No. Write and delete actions are disabled by default in every module, and you decide which modules and which actions to enable. Customer data and shop status stay switched off regardless of what else you turn on, until you explicitly enable them.

Can the AI undo its own changes?

Not on its own. The AI can act within whatever permissions you have granted it, but reverting a change through the built-in undo is kept as a step the shop administrator takes deliberately — it is not something the AI can trigger.

Availability

Themeart MCP is available now for JTL-Shop, licensed per domain at €129 plus VAT, currently at version 0.1.1. Setup documentation is linked from the product page below.

See the full module list and setup docs. View Themeart MCP on themeart.de.