TypeScript · intelligent systems integration
Joomla MCP
A TypeScript MCP server that maps a source-catalogued Joomla Web Services surface into structured tools with guarded write operations.
- Role
- Project architect, principal implementer and maintainer
- Evidence
- 1 direct public link
Purpose and value
Why this system exists
The project connects agent reasoning to a real application platform while keeping tool contracts, write permissions, audit concerns, and transport boundaries explicit.
Project architect, principal implementer and maintainer
System structure
Architecture
- 01
Route templates are catalogued from source and projected into MCP tools.
- 02
Read and write concerns are separated, with writes placed behind explicit guards.
- 03
Transport supports stdio and HTTP integration modes.
- 04
Companion and API layers isolate Joomla-specific behavior from protocol concerns.
Boundaries
Principal interfaces
Judgement
Engineering decisions
Catalogue routes from source instead of relying on an unverified manual list.
Make mutating operations visibly different and explicitly controlled.
Report validation status accurately; a catalogued route is not automatically a production-certified route.
Confidence model
Delivery, validation, and maintenance
- Typed tool definitions
- Guarded writes
- Audit-aware design
- Public validation status and known limits
Direct sources
Inspect the evidence
83 commits in the complete reviewed history; public @joomengine/joomla-mcp 0.7.0 package; 236 Joomla 6.1 Web Services route templates across 36 resource bases.
Production certification remains explicitly gated; action families are not presented as universally production-verified.