Requirements and installation for evoMCP
Requirements
| Requirement | Value |
|---|---|
| Joomla | 5.0 or later [PENDIENTE: the component installer only checks for 5.0.0, but the product README says 5.3 or later; confirm which is the tested minimum] |
| PHP | 8.1 or later |
| YOOtheme Pro | Only for the page builder tools. If the YOOtheme template is not installed, the YOOtheme plugin does not register its tools. [PENDIENTE: minimum YOOtheme Pro version] |
| Database | Whatever Joomla uses. Installation creates ten tables with your prefix, each with a name starting evomcp_ |
| Site address | HTTPS and public if you want to connect cloud assistants (Claude, ChatGPT). A local or test site only works with clients running on your own machine |
The component installer checks the PHP and Joomla versions and cancels the installation with a message if they are not met.
The /mcp route and the OAuth routes (/oauth/... and /.well-known/...) do not go through the Joomla router. The system plugin handles them, but the request has to reach index.php. The usual Joomla rewrite rules (.htaccess on Apache) are enough. [PENDIENTE: equivalent rule for nginx; it is not documented in the repository]
What the package contains
pkg_evomcp installs ten extensions:
| Extension | What it does |
|---|---|
com_evomcp |
Administration panel: connections, approvals, usage, audit log and connection guide |
plg_system_evomcp |
Serves the /mcp endpoint and the OAuth routes |
plg_evomcp_content |
Article and category tools |
plg_evomcp_joomla |
Menus, modules, media, users, extensions, templates, configuration and scheduled tasks |
plg_evomcp_yootheme |
YOOtheme Pro page builder and theme tools |
plg_evomcp_entities |
Generic entities, component options and pre-change backups |
plg_evomcp_system |
System operations: updates, installation, configuration, cache, logs |
plg_evomcp_advanced |
Advanced SQL and files layer |
plg_privacy_evomcp |
Export and deletion of a user's data for Joomla's privacy tools |
plg_task_evomcp |
Daily maintenance task |
The plugins of other evo extensions (evoLeadGate, evoOrigin, evoYTAccess) register their own tools when they are installed. They arrive with those extensions, not with this package.
Install
- Download
pkg_evomcp-<version>.zipfrom your account. The download key is explained in Licences and updates. - In Joomla, open System → Install → Extensions and upload the ZIP.
- When it finishes, open Components → evoMCP. You can carry on with the first steps.
What is enabled
On a fresh installation, the installer enables:
- the system plugin,
- every plugin in the
evomcpgroup except the advanced layer, - the privacy plugin and the task plugin.
The advanced layer is installed disabled and is never enabled for you, either on install or on update. To use it you must open the three locks described in the reference.
The installer also creates, once, the scheduled task "evomcp: mantenimiento", which runs every 24 hours. You can change or disable it under System → Scheduled Tasks.
On an update, any evomcp group plugins that the new version brings and that did not exist before are enabled, except the advanced layer.
If you get a 401 with a valid token
Apache without Joomla's .htaccess does not pass the Authorization header to PHP. Turn on Joomla's rewrite rules or add this line to the Apache configuration:
SetEnvIf Authorization "(.*)" HTTP_AUTHORIZATION=$1
The endpoint also reads the REDIRECT_HTTP_AUTHORIZATION variant, which Apache sets in some configurations.
Update
The package ships with its Joomla update site. When you update from within Joomla, table migrations run through Joomla's schema system. Back the site up before updating in production.