Atlas / MCP servers / joomengine / joomla-mcp

joomla-mcpCAUTION

Name: joomla-mcp
Author: joomengine

mcp/joomengine/joomla-mcp

MCP server by joomengine · joomengine · joomla · joomla mcp · Audited 2026-10-11

A Model Context Protocol (MCP) server that enables AI assistants to securely manage and automate Joomla sites through Joomla APIs and CLI tools.

Verdict

CAUTION

Grade

Trust score

73 /100

Exposed tools

24 18r · 4w · 2d

Transport

stdio · streamable-http

License

NOASSERTION

Stars

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

[](https://github.com/joomengine/joomla-mcp/actions/workflows/ci.yml) [](https://github.com/joomengine/joomla-mcp/actions/workflows/release.yml) [](https://github.com/joomengine/joomla-mcp/actions/workflows/publish-release.yml) [](https://www.npmjs.com/package/@joomengine/joomla-mcp) [](https://www.joomla.org/) [](https://nodejs.org/) [](LICENSE)

Project notice: use the Joomla-native MCP package

This repository started as the TypeScript proof of concept for JoomEngine MCP. Active development has moved to the Joomla-native `mcp_component` and its companion plugins. This is the fourth iteration of the MCP implementation, with broader functionality and native Joomla administration and Joomla Component Builder (JCB) integration. “Fourth iteration” describes the project's development history, not a v4 release number.

For new installations, install the stable [`mcp_package`](https://github.com/joomengine/mcp_package) on your Joomla site. It bundles the MCP component, the console plugin and the webservices plugin in one Joomla extension ZIP. The component release workflow rebuilds the package from the tagged extensions; use a published package tag ZIP and keep receiving updates through Joomla's extension updater.

The current stack is distributed along

Read from source at commit 2418d90ed3bfOBSERVED · 2026-10-11

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.

claude-code

claude mcp add joomla-mcp -- npx -y @joomengine/[email protected]

claude-desktop

{
  "mcpServers": {
    "joomla-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@joomengine/[email protected]"
      ]
    }
  }
}

Exposed tools (24)

18 read · 4 write · 2 destructive. Blast radius: 2 tools can delete or overwrite — an agent that can be talked into calling a tool can be talked into calling this one.

Tool	Risk	Description
`joomla_action_describe`	read
`joomla_action_read`	read
`joomla_action_write_plan`	write
`joomla_actions_search`	read
`joomla_application_config_get_safe`	read
`joomla_capabilities`	read
`joomla_cli_command_help`	read
`joomla_cli_commands_list`	read
`joomla_cli_inventory`	read
`joomla_cli_targets`	read
`joomla_companion_action_read`	read
`joomla_companion_capabilities`	read
`joomla_content_article_create_plan`	write
`joomla_content_article_delete_plan`	destructive
`joomla_content_article_get`	read
`joomla_content_article_update_plan`	write
`joomla_content_articles_list`	read
`joomla_extensions_list`	read
`joomla_permission_approve`	read
`joomla_permission_request`	read
`joomla_permission_revoke`	destructive
`joomla_permissions_list`	read
`joomla_sites_list`	read
`joomla_write_apply`	write

Trust audit

CAUTIONgrade C · trust 73/100 Install with care. The audit found things worth knowing before you trust its output.

Layer	What it checks	Result
L0	Provenance & inventory	PASS
L1	Static analysis of the code	WARN
L2	Instruction surface (what it tells the agent)	PASS
L3	Class-specific surface	WARN
L4	Behavioural (sandbox)	SKIPPED

What the source does

Filesystem: declared (4 observation(s))
Network: declared (5 observation(s))
Shell: declared (2 observation(s))
Dependencies: not all pinned
Secrets in source: found

Findings (18)

MEDIUMHard-coded secrets · secret.generic · CWE-798, CWE-321

scripts/release/test-package-consumer.mjs:92

token: 'not-used-by-this-test',

MEDIUMHard-coded secrets · secret.generic · CWE-798, CWE-321

scripts/release/test-package-consumer.mjs:124

token: 'not-used-by-this-test',

MEDIUMHard-coded secrets · secret.generic · CWE-798, CWE-321

tests/article-text-writes.test.ts:14

approval: { secret: 'a-secret-that-is-at-least-32-bytes-long', ttlMs: 60_000 },

MEDIUMHard-coded secrets · secret.generic · CWE-798, CWE-321

tests/companion-write-input.test.ts:12

approval: { secret: 'a-secret-that-is-at-least-32-bytes-long', ttlMs: 60_000 },

MEDIUMHard-coded secrets · secret.generic · CWE-798, CWE-321

tests/custom-field-writes.test.ts:50

approval: { secret: 'a-secret-that-is-at-least-32-bytes-long', ttlMs: 60_000 },

MEDIUMFilesystem / path · mcp.destructive_tools · CWE-22, CWE-59

joomla_content_article_delete_plan, joomla_permission_revoke

Why it matters. 2 tool(s) can delete or overwrite

Fix. prefer a read-only mode or scoped tokens; the page states the blast radius

LOWFilesystem / path · fs.traversal · CWE-22, CWE-59

scripts/deploy/validate.sh:12

exec "${SCRIPT_DIR}/../../tests/deploy/static-deployment.test.sh"

LOWFilesystem / path · fs.traversal · CWE-22, CWE-59

scripts/fixtures/verify-article-bodies.mjs:7

import { loadConfiguration } from '../../dist/config/load.js';

LOWFilesystem / path · fs.traversal · CWE-22, CWE-59

scripts/fixtures/verify-article-bodies.mjs:8

import { createHttpLiveSession, createStdioLiveSession } from '../../dist/live-test/transports.js';

LOWFilesystem / path · fs.traversal · CWE-22, CWE-59

src/infrastructure/api/joomla-api-client.ts:1

import type { ApiConfig } from '../../config/schema.js';

LOWFilesystem / path · fs.traversal · CWE-22, CWE-59

src/infrastructure/api/joomla-api-client.ts:2

import { JOOMLA_MCP_VERSION } from '../../version.js';