MCP Server

$49.00

Select Billing Option

1 Year

2 Years

Stop Copy-Pasting Your Store Into ChatGPT Like a Cave Person

Your AI assistant is brilliant. Your Joomla ecommerce store is full of data. Between them: a gap you're currently filling manually, one order number at a time. The J2Commerce MCP Server closes that gap. Your AI asks. Your store answers. You make decisions.

AI-callable store tools

Pre-built AI workflows

60s

Setup time, no kidding

Write permissions by default

What Your AI Can Now Do With Your Store

Twelve live data tools. Four read-only context feeds. Three pre-built workflows that run on a single instruction. All talking directly to your live J2Commerce data — no exports, no copy-paste, no 48-hour-old snapshots.

Product Catalog Access

Browse products, filter by category, price, or stock status. Get full variant detail on any item. "What's my cheapest in-stock option under $30?" — answered, in seconds, from live data.

Order Management

Filter orders by date, status, customer, or value range. Pull any order's full detail: line items, payment info, shipping notes, complete history. Every order question answered without opening the admin.

Customer Intelligence

Top customers by lifetime value. New signups who haven't ordered. Buyers from a specific country. Full profile including addresses, order count, and total spent — so the re-engagement email you've been putting off finally happens.

Revenue Analytics

Total revenue, order count, and average order value over any date range. Top products by what they actually earned. "What did I sell last week?" is now a 4-second question, not a 15-minute report adventure.

Coupon Management

See every active coupon with usage counts and expiry dates. Validate any coupon code instantly. No more digging through the coupon list to find out why that promo "isn't working." Just ask.

Store Structure at a Glance

Shipping methods, payment gateways, your full category tree, order status definitions, and store configuration — all readable by your AI before it answers anything operational. It knows your store before you ask.

Three Workflows That Just Work

You do not need to be clever about prompting. Three pre-built AI instruction sets handle your most common store tasks out of the box. One sentence. Actual results.

Sales Analysis — Without the Spreadsheet

Give it a date range. The AI chains three separate data pulls automatically — overall revenue, top product rankings, order pattern analysis — and comes back with a complete sales summary. Monday morning, coffee in hand, 11 seconds.

Total revenue and order count for any period
Top products by revenue or units sold
Average order value and pattern analysis

Support Request Handler — Handle Sandra in 45 Seconds

Drop in an order number and a brief description of the customer's complaint. The AI retrieves the full order, reads the customer's history, and drafts a professional reply you can send as-is or edit in under a minute. What used to take 12 minutes now takes less than one.

Full order detail with every line item
Customer profile and order history for context
Draft response, ready to send or tweak

Inventory Audit — At 3am If You Want

Set a stock threshold. Get a prioritized low-stock list with reorder quantity suggestions based on actual sales velocity. The store doesn't care that it's midnight. The AI doesn't care. The reorder list is ready when you wake up, no login required.

Products below your chosen stock threshold
Sales velocity to prioritize reorder urgency
Suggested reorder quantities, ready to forward

Real Stores. Real Questions. Answered.

8:47 AM. Coffee in hand. AI client already connected to the store. One message: "What were my total sales last week and which three products sold the most?" The AI pulls live order data, calculates revenue, identifies top performers, and returns a clear summary.

No login. No navigation. No report menu. Elapsed time: 11 seconds. The rest of the morning is spent actually thinking about what the numbers mean — not gathering them.

Customer emails at 11:32 AM about order #5107. Wrong item shipped. You're away from the desk. At 12:15, phone out: "Customer says they got the wrong item on order 5107, please look it up and draft a reply." The AI retrieves the full order, reads what was selected, and writes a professional response with a proposed resolution.

One sentence edited. Sent. Done before the second half of lunch. And your customer feels taken care of in under an hour instead of waiting until tomorrow morning.

A developer building a custom J2Commerce extension needs to reference the store's live order status list. With the MCP Server running on the dev site, they ask from inside their IDE: "What are the current order statuses in this store?" The AI retrieves the live status codes and labels, and the developer uses those values directly in the code.

No manual lookup. No asking the store owner for screenshots. The right values in the code on the first try. No rework.

The supplier order window closes tomorrow. You forgot to run the stock review. It's late. One message: "Inventory audit — anything with under 15 units in stock, give me a reorder list based on what's been selling." The AI queries the catalog, cross-references with order history for velocity, and returns a prioritized list.

Forwarded to the supplier at 11:23 PM. Crisis averted. Nobody ever needs to know how close that was.

An agency manages Joomla ecommerce for three clients. Each store has the MCP Server installed. Monday morning, the account manager connects to each store in the same AI conversation thread and asks: "Which store had the best week last week?" Three revenue summaries return in under a minute.

Comparative intelligence across three stores. One coffee. No logging into three separate admin panels. No remembering which store is which browser tab. Just answers.

Security That Doesn't Require a PhD to Understand

"I connected an AI to my store" sounds alarming until you see how the controls actually work. Read-only by default. Six independently configurable tool groups. Full audit logging. Your data, your server, your rules.

Eyes, Not Hands

By default, the AI can read your data. It cannot modify anything. No orders created. No products changed. No refunds issued. Read-only until you explicitly flip the write-access switch.

Six Configurable Tool Groups

Products, orders, customers, analytics, coupons, and shipping/payment can each be enabled or disabled independently. Don't want the AI seeing customer data? One toggle, off. That's it.

Complete Audit Logging

Every AI request is logged. Every one. Configurable retention from 1 to 365 days. If something unexpected happens, you have receipts. Full records, always.

Rate Limiting — Your Ceiling

Set how many AI requests per minute your server will accept. Default is 100. Adjust up or down based on your usage patterns. Runaway AI sessions don't happen because you decide the cap.

Joomla ACL Controls Access

The same user group and permission structure you use for everything else in your Joomla site governs who can trigger the AI connection. You're not learning a new security model. You're using the one you already trust.

Your Data Stays on Your Server

No third-party relay. No SaaS middleware layer. No data warehouse ingesting your customer records. The AI client connects to your Joomla installation. Your database answers. That is the entire path.

Questions You Are Definitely Thinking Right Now

No. By default, every operation is read-only. The AI cannot create orders, change product prices, update customer records, issue refunds, or process payments. It reads. That is all. There is a write operations switch in the admin settings — it is off by default, and it stays off until you, the store owner, explicitly decide otherwise.

Only in the sense that any server response leaves the server. The AI client connects to your Joomla site. Your site runs the query. Your site returns the result. There is no intermediary. No data warehouse quietly ingesting your customer records. No SaaS layer between your database and your AI. Your data goes from your server to your AI client, full stop.

Any AI client that supports the Model Context Protocol standard — Claude Desktop, Cursor, Continue.dev, and a growing list of others. The protocol is open and adoption is expanding. You are not locked to one AI provider or betting on one company's roadmap.

Both. Joomla's standard ACL permission system governs who can trigger the connection. You can configure it so your support team can access order and customer tools, your marketing person can access analytics, and nobody can touch coupon data unless you specifically allow it. Same flexibility as every other Joomla permission you've already configured.

There is a write operations toggle in the plugin admin settings. When enabled, the AI can perform actions that modify store data. The documentation covers what that means in detail. The recommendation: test on a staging installation first. The default is off because that is the sensible starting point.

AI requests go through your existing web server. Rate limiting (configurable, default 100 requests per minute) ensures no AI session can flood your server with queries. In normal usage the load is negligible — you are making one or two requests to look something up, not running a data pipeline. Set the rate cap to what makes sense for your hosting environment.

Yes. Install and enable the plugin on a staging copy of your Joomla site. Connect your AI client to the staging endpoint. Everything works identically — the only difference is the data is test data. Confirm the behavior you want before enabling on production. Standard practice. Highly recommended.

Your Joomla Store Has Been Waiting for This Conversation

Every order question answered in seconds. Every customer insight available on demand. Every inventory gap caught before the supplier window closes. Your AI has been ready. Now your Joomla ecommerce store is too. It's about time.

Translated In The Following Languages

Arabic Unitag (ar-AA), Chinese, Traditional (zh-TW), Danish (da-DK), Dutch (nl-NL), English (en-GB), English, USA (en-US), Finnish (fi-FI), French (fr-FR), German (de-DE), Greek (el-GR), Hebrew (he-IL), Italian (it-IT), Japanese (ja-JP), Norwegian Bokmål (nb-NO), Persian Farsi (fa-IR), Polish (pl-PL), Portuguese, Brazil (pt-BR), Portuguese, Portugal (pt-PT), Russian (ru-RU), Spanish (es-ES), Swedish (sv-SE), Turkish (tr-TR)

License Information

An active license entitles you to updates, downloads, and support for the duration of the license period. You may continue using this plugin indefinitely without an active license; however, support, updates, and downloads will not be available while your license is inactive.

Developer J2Commerce
J2Commerce Version 6.x
Joomla Version 6.x

Language Translations

Arabic Unitag

Chinese, Traditional

Danish

Dutch

English

English, USA

Finnish

French

German

Greek

Hebrew

Italian

Japanese

Norwegian Bokmål

Persian Farsi

Polish

Portuguese, Brazil

Portuguese, Portugal

Russian

Spanish

Swedish

Turkish

User Guide (Version 6)

Improvement Hold coupon and voucher writes to the order-editing permission the admin uses

Improvement Require a whole voucher code to search for one, not a fragment

Improvement Require the publish permission to create a product already published

Improvement Enforce the API login permission on every way of connecting, not just report it

Improvement Name a voucher by its subject, not its code, when adjusting its balance

Improvement Record resource reads and prompt fetches in the action log, refusals included

Fix Fix a stock search treating an underscore in an SKU as a wildcard

Update Upgrading: a non-Super-User needs the API login permission to connect

Improvement Hold sign-in with a Joomla account to the same account checks a token answers to

Improvement Hold a prompt to the same consented scope a tool and a resource answer to

Improvement Lower the product-image size limit to 12 megapixels, refused with the limit named

Improvement Escape markup characters in every response and label it as JSON

Fix Fix a product search for a term containing % or an apostrophe finding nothing

Improvement Restore the earlier release history to this changelog

New Feature Add product creation, editing, publishing and deletion from an AI assistant

New Feature Add store settings editing, limited to a fixed list of safe settings

New Feature Add sign-in with your Joomla account instead of pasting a token (OAuth)

Improvement An assistant is now held to what you approved, even where your account allows more

New Feature Add a consent screen listing exactly what an assistant can see and change

New Feature Add a per-group write switch, off by default and left off by upgrades

New Feature Add two-step confirmation before any destructive change

New Feature Add stock and price editing, per product, per variant, or across a range

New Feature Add bulk price, stock and publish changes, previewed and capped before they run

New Feature Add draft orders: build an order for a customer from a list of products

New Feature Add order cancellation, with a reason and no money movement

New Feature Add three order write tools: add note, change status, save tracking

New Feature Add customer record editing — name, address and contact details

New Feature Add coupon creation and editing, and a switch to turn one on or off

New Feature Add gift vouchers, and balance adjustments recorded in the voucher history

New Feature Add product image upload, straight from a conversation, with alt text required

New Feature Add alt-text editing for every product image, main and gallery

New Feature Add SEO meta description and keywords to product create, edit and read

New Feature Add Joomla tag and custom-field editing on products

New Feature Add an MCP dashboard: activity, changes, refusals and who is connected

New Feature Add live views of pending orders and low stock

New Feature Add a one-click AI token, with the client configuration ready to paste

New Feature Add a J2Commerce dashboard tile linking to the MCP dashboard

New Feature Add a way for other J2Commerce plugins to add their own tools

New Feature Add a preview of exactly what each setting changes from and to, before it runs

New Feature Add a bulk change limit setting, so one instruction cannot reprice the catalog

New Feature Add the action logger: every tool call recorded, refusals and errors included

New Feature Add the MCP action log table, recording every tool call for the dashboard

New Feature Add automatic action-log retention, with a configurable window in days

New Feature Add j2c_search_products, free-text search over name, SKU and description

New Feature Add four prompts: product copy, price anomalies, churn risk and SEO audit

New Feature Add tool annotations so clients can tell a safe read from a risky write

New Feature Add structured tool output alongside the text block for typed clients

New Feature Add ready-to-paste settings for remote clients, and for older ones via a bridge

Improvement Connect from anywhere: the web connection now works with modern AI clients

Improvement Refuse a web request from another website, so only this store's pages can call it

Improvement Show the API token as a masked field and drop its copy button

Improvement Stop sending the API token in every dashboard refresh

Improvement Require the edit permission, not the view permission, to reset a token

Improvement Refuse a bulk change that matches more products than the store allows in one go

Improvement An edit now changes only the fields you name; everything else is left as it was

Improvement Product deletion no longer removes variants belonging to other products

Improvement The tool list is now sent in pages, so large stores no longer send one response

Improvement Re-read plugin settings per request on the CLI, so changes take effect at once

Improvement Both connections now share one permission check instead of keeping a copy each

Improvement Read through the component models the admin UI and REST API already use

Improvement Move the whole tool, resource and prompt catalog into one shared registry

Improvement Advertise MCP 2025-06-18, still accepting 2025-03-26 and 2024-11-05 clients

Improvement Rename j2c_apply_coupon to j2c_validate_coupon; the old name still works

Improvement Chart data now readable without relying on colour, and by a screen reader

Improvement Warn on the dashboard when sign-in is switched on but the web connection is off

Improvement List only the tools, resources and prompts the signed-in account can actually use

Improvement Hold a browser session to the same account groups an API token answers to

Improvement Refuse the desktop connection script when it is reached over the web

Improvement Report the server version from the manifest so clients see the right one

Improvement Clear the Joomla 7 deprecation warnings ahead of the next major

Fix Fix the desktop connection failing on the first call every client makes

Fix Fix the first extra product image failing on a product with no image row yet

Fix Fix an over-long image description failing with an unreadable database error

Fix Hold order tools to the same component permission the rest of the catalogue uses

Fix Make a confirmation token strictly single-use under concurrent calls

Improvement Blank the token display when the token is switched off

Fix Fix AI-made changes being recorded against no user at all

Fix Fix the desktop connection returning internal error detail to the client

Fix Fix creating a product failing outright on the desktop connection

Fix Fix tags silently not saving when the assistant runs on the desktop connection

Fix Fix a coupon edit switching off free shipping and resetting its usage limits

Fix Fix a customer edit being refused when only one field was changed

Fix Fix the product tool returning only the master variant instead of all of them

Fix Fix the categories resource always coming back empty

Fix Fix store statistics counting cancelled and failed orders as revenue

Fix Fix change times shifting timezone when the dashboard refreshed

Fix Fix impossible dates silently charting an empty period

Fix Fix the inventory-audit prompt pointing at the wrong tool for stock levels

Fix Fix the CLI dying on any model-backed tool, and PHP notices corrupting its output

Improvement Narrow the store configuration resource to non-credential fields

Update Sign-in with a Joomla account needs the separate OAuth plugin installed

Fix Hold the web connection to the same credential check as the desktop one

Improvement Breaking: both transports now require a credential (Bearer token / JOOMLA_API_KEY)

Improvement Breaking: HTTP transport is now off by default — enable it deliberately

Fix Check the desktop connection's API key against the stored one

Fix Hold a tool call to the enabled tool groups on both connections

Fix Return an explicit column list for customer records on both connections

Fix Withhold payment and gateway fields from order responses

Fix Answer a failed call with a generic message instead of internal detail

Fix Fix order line items and history always coming back empty

Fix Fix six tools and one resource failing outright on missing columns

Fix Fix store configuration resource reading the wrong data source

Fix Fix CLI reporting expired and disabled coupons as valid

Improvement Breaking: resource j2commerce://zones renamed to j2commerce://geozones

Improvement Authorise every tool and resource against a com_j2commerce permission

Improvement Share one implementation between both transports so fixes apply once

New Feature Add reference_data tool group for store configuration and geo zones

Improvement Use searchable multi-select for Allowed Transports and Enabled Tools

Deletion Remove Rate Limit, Audit Log Days and Write Operations settings, never read

Deletion Remove the Permissions tab, superseded by the per-tool permission checks

Deletion Remove eight unreachable internal methods incl. plugin scaffolding

Update Upgrading: create a Joomla API token, and re-enable HTTP transport if you use it

Update Requires the Joomla API Authentication - Token and User - Token plugins enabled

Update Requires Joomla 6.x + J2Commerce 6.x + an MCP-compatible AI client

Fix Fix HTTP transport now requires authentication before serving any data

Fix Fix CLI transport validates the API key on every request

Fix Fix Disabled tool groups are now enforced on both transports

Fix Fix User tools omit internal credential fields from responses

Fix Fix Order tools omit internal payment-gateway fields from responses

Fix Fix Error responses are now generic and do not surface internal detail

Fix Fix order line items and history always coming back empty

Fix Fix six tools and one resource failing outright on missing columns

Fix Fix store configuration resource reading the wrong data source

Fix Fix Coupon validity check now correctly rejects expired and disabled codes