Packages
The Packages tool lists the Composer packages installed on the Magento instance — one row per shippable extension. Each entry carries the Composer package name, the user-facing title, the installed version, its status, the technical modules it provides, and the other packages it requires.
Access control
Access to this tool is controlled by the MCP Tools -> Built in -> System -> Packages ACL resource. Enable or disable it in System -> Permissions -> User Roles -> [Role] -> Role Resources.
When to use
Use this tool to answer questions about what is installed and how packages relate to each other:
- "Is package X installed?"
- "What version of Y is running?"
- "What depends on Z?"
For the latest-version / license / outdated status of Mirasvit packages specifically, use the Mirasvit Modules Info tool instead — it enriches each package with feed and license data in a single call.
Parameters
| Parameter | Description | Type | Required |
|---|---|---|---|
search | Case-insensitive substring matched against the package name, title, every technical module name, and every entry in the require list. Omit to return all. | string | No |
vendor | Exact-match vendor prefix (the part before / in the package name, e.g. mirasvit). Combinable with search. | string | No |
limit | Cap on the number of returned packages (default 30). Use 0 for no limit — only safe with a narrow search. | integer | No |
offset | Pagination offset into the filtered list (default 0). Use with limit to walk a large result set. | integer | No |
The installed package set does not change during a session. The AI client is expected to call this tool once and reuse the result rather than re-querying.
Example output
Each row includes:
- Package name — the Composer name (e.g.
mirasvit/module-mcp-tool) - Title — the user-facing extension name
- Installed version and status
- Modules — the technical module names the package provides (a multi-module package lists several)
- Requires — the other installed packages it depends on