MCP for Akeeba Ticket System is a free add-on for MCP for J that puts your Akeeba Ticket System help desk in front of your AI client. Thirty tools cover tickets, replies, invited collaborators, managers, categories, statuses, triage reporting and health diagnostics, so you can ask which tickets nobody has answered in a week, or post a reply, without opening the admin at all. It works with the free Core edition and with Professional, and every write goes through Akeeba's own models — so the status rules, the permission checks and the notification emails all fire exactly as they would if you'd clicked the buttons yourself.
Why this exists
A help desk is a queue, and the questions you actually have about a queue are awkward to answer from a ticket list. Which conversations have gone quiet? Who's carrying too much this week? Akeeba Ticket System already stores everything you'd need to answer both, but its admin screens are built for working one ticket at a time, so getting an answer means sorting, filtering, counting, and holding the running total in your head while you do it. This add-on hands the whole surface to your AI client instead, including three reports that exist for nothing but triage. You ask in a sentence and the answer comes back as data.
What Claude can do
Thirty tools, grouped roughly the way you'd reach for them.
| Area | Tools | What you can do |
|---|---|---|
| Tickets | 8 | List with filters, read one in full, create, update, change status, switch public/private, assign to a manager, delete. |
| Posts | 6 | Read a thread, post a reply, edit or unpublish a post, delete one. The opening message of a ticket is a post, so this covers it too. |
| Collaborators | 3 | List who has been invited onto a ticket, invite someone by username, remove them. |
| People | 2 | List ticket managers, and list who can be assigned tickets in a category — with their current open counts, so it's actually useful for routing. |
| Lookups | 3 | Categories with their ATS-specific settings, and the statuses this site actually uses, including any custom ones. |
| Reports | 3 | A summary by status, category, assignee and priority; stale tickets split by who is holding them up; per-agent workload with time spent and oldest unanswered. |
| Diagnostics | 3 | Component and edition info, annotated configuration, and a health check that looks for orphaned rows and broken category links. |
| Table access | 2 | A read-only, column-validated query over the component's own tables for the question no tool anticipated. |
Installing it
You'll need Joomla 5 or 6, PHP 8.2 or later, MCP for J, and Akeeba Ticket System itself — the free Core edition is enough.
- Open Components → MCP for Joomla → Browse MCP Add-Ons and click Install on this add-on. You can also download the ZIP above and install it through System → Install → Extensions.
- That's the whole install. The plugin enables itself, and the tools show up in your connected AI client the next time it lists them.
There's no admin screen for this plugin, by design — it adds tools to MCP for J rather than a place to click. If you go hunting for a menu entry after installing, that's why there isn't one.
Using it
Ask for what you want in plain language. "Which open tickets have had no reply in the last ten days?" runs the stale-ticket report. "How's the support load split across the team right now?" runs the workload report. "Show me ticket 412 and everything on it" pulls the thread, the invited collaborators, the custom field values, and what you personally are allowed to do with it.
Writes work the same way, and they behave like a real reply rather than a database edit. Posting through this add-on sends the notification email and applies Akeeba's own rule about what the ticket status becomes — a manager's reply on someone else's ticket moves it to Pending, the customer's moves it back to Open — then updates the ticket's recorded time from the posts underneath it. If you're new to it, run the health check and one of the list tools first, so you can see the shape of the data before you change any of it.
Permissions and security
Every ticket this add-on hands back is checked against Akeeba's own permission helper before you see it, one row at a time, even when the database query has already filtered. That's deliberate. Akeeba shipped 5.6.0 specifically to fix a case where its list query and its single-ticket check disagreed and private tickets leaked through the JSON API. Re-deriving that logic by hand is how you recreate that bug, so this add-on doesn't try — it asks the component and takes the answer.
Private manager notes are deliberately unreachable. Akeeba Ticket System creates all of its database tables whether or not you own Professional, so most Professional-only tables just sit empty on a Core site and reading them is harmless. Manager notes are the exception. They're private staff commentary, and a site that once ran Professional and later dropped back to Core still holds every note it ever wrote. The component fails safe there and returns nothing before it even builds a query, but a general-purpose table reader wouldn't. So no tool here reads manager notes, the query tool refuses that table by name, and the health check reports only how many rows exist — which is enough to tell you the site is sitting on data its own interface will never show you, without this add-on being the thing that shows it.
Core and Professional
The add-on runs against both editions and works out which one it's looking at from Akeeba's own edition flag. On Core, the Professional-only surface — attachments, canned replies, automatic replies, manager notes, the timecard, the log, scheduling and the mail gateway — is reported as unavailable rather than worked around. None of those tools exist here to be talked into running. A separate Professional add-on is planned for that surface.
This is version 1.0.0. All thirty tools were driven end to end against a live Akeeba Ticket System 5.6.0 Core install on Joomla 6 before release, and that testing is what caught a bug in the post-editing tool and got it fixed before it shipped. Two paths haven't been exercised yet: Akeeba Ticket System Professional, and Joomla 5. The tools are written for both, and the edition check is a faithful copy of the vendor's own, but nobody has actually run them there. If you're on either, you'd be the first, and I'd genuinely like to hear how it goes.
Open source
GPL-2.0-or-later, the same license as Joomla itself. Source lives on GitHub.
Add comment