Skip to main content

Mirasvit Modules Info

The Mirasvit Modules Info tool returns every installed Mirasvit package enriched with its latest stable version (from the Mirasvit feed) and its license status (from the Mirasvit license server). One call answers questions that would otherwise require scraping each module's changelog.

Access control​

Access to this tool is controlled by the Mirasvit Modules Info ACL resource, found under MCP Tools -> Built in in System -> Permissions -> User Roles -> [Role] -> Role Resources.

note

Unlike the other built-in tools, this one is provided by Mirasvit Core rather than the System group, so it appears under its own branch in the permissions tree.

When to use​

  • "Which of my Mirasvit modules are outdated?"
  • "Is my license for extension X active?"
  • Any combined version + license question across multiple Mirasvit extensions.

For a plain list of all installed Composer packages (not just Mirasvit), use the Packages tool.

Parameters​

ParameterDescriptionTypeRequired
searchCase-insensitive substring matched against the Composer package name and the user-facing title. Omit to return all Mirasvit packages.stringNo
outdated_onlyWhen true, returns only packages classified as outdated (installed version below the latest stable, and not a pre-release). Default false.booleanNo
include_licensesWhen true (default), includes license_active and license_message per package. Set to false to skip license checks when only versions are needed.booleanNo
tip

Package status changes slowly (the feed is cached for 1 hour, and an active license status for 24 hours), so the AI client is expected to call this tool once per session and reuse the result.

Example output​

Each row carries:

  • installed_version / latest_version
  • is_outdated — installed version is below the latest stable
  • is_off_stable — installed version is a pre-release / dev branch (bumping it changes Composer constraints rather than just the version)
  • license_active / license_message
  • family — the parent extension grouping (via the package's Composer require[])
  • modules — the Magento module names the package ships
  • Marketplace metadata — sku, url, docs_url, changelog_url