# Magento Cloud MCP Server (npm · mcp-magento-cloud)

MCP server for Adobe Commerce Cloud — REST API + SSH, no PHP CLI required

- Trust score: 69/100 (medium)
- Change this week: +23
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `mcp-magento-cloud`: 69/100 (this document), [markdown](https://verifymcp.io/servers/juan-cinto-infracommerce-magento-cloud/mcp-magento-cloud.md), [page](https://verifymcp.io/servers/juan-cinto-infracommerce-magento-cloud/mcp-magento-cloud)

## Channel facts

- Registry: `npm`
- Package: `mcp-magento-cloud`
- Version: `2.4.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (103 of 107), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (103 of 107), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 40 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1246 tokens (~83/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add juan-cinto-infracommerce-magento-cloud -- npx -y mcp-magento-cloud
```

### Codex

```bash
codex mcp add juan-cinto-infracommerce-magento-cloud -- npx -y mcp-magento-cloud
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "juan-cinto-infracommerce-magento-cloud": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-magento-cloud"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add juan-cinto-infracommerce-magento-cloud --command npx --arg -y --arg mcp-magento-cloud
```

### Hermes

```yaml
mcp_servers:
  juan-cinto-infracommerce-magento-cloud:
    command: "npx"
    args: ["-y", "mcp-magento-cloud"]
```

### Other

```json
{
  "mcpServers": {
    "juan-cinto-infracommerce-magento-cloud": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-magento-cloud"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 66, +61)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] Licence: MIT

### 2026-08-01 (score 5, −16)

- [functional regression] Tool coverage: 100 → unverified

### 2026-07-31 (score 21, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 28, +4)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 24, −22)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (15)

### `list_projects` (~19 tokens)

List all Magento Cloud projects available to the current user

### `list_environments` (~30 tokens)

List all environments for a Magento Cloud project

Input parameters:

- `project` (string, required): The Magento Cloud project ID

### `get_environment_info` (~59 tokens)

Get detailed information about a specific Magento Cloud environment (status, URLs, type, etc.)

Input parameters:

- `environment` (string, required): The environment name, e.g. 'staging', 'production'
- `project` (string, required): The Magento Cloud project ID

### `get_environment_urls` (~66 tokens)

Get the public URLs of a Magento Cloud environment

Input parameters:

- `environment` (string, required): The environment name, e.g. 'staging', 'production'
- `primary` (boolean): Only return the URL for the primary route
- `project` (string, required): The Magento Cloud project ID

### `list_activities` (~152 tokens)

List recent activities (deploys, pushes, crons, etc.) for a Magento Cloud environment or project

Input parameters:

- `environment` (string, required): The environment name, e.g. 'staging', 'production'
- `limit` (number): Number of activities to return (default: 10)
- `project` (string, required): The Magento Cloud project ID
- `result` (string): Filter by activity result
- `start` (string): Only list activities created before this date, e.g. '2026-05-01'
- `state` (string): Filter by activity state
- `type` (string): Filter by activity type, e.g. 'push', 'cron', 'environment.backup'

### `get_activity_log` (~98 tokens)

Display the log output for a specific activity on a Magento Cloud environment. If no activity ID is provided, shows the log for the most recent activity.

Input parameters:

- `environment` (string, required): The environment name, e.g. 'staging', 'production'
- `id` (string): The activity ID. Defaults to the most recent activity if omitted. Use list_activities to find IDs.
- `project` (string, required): The Magento Cloud project ID

### `list_variables` (~72 tokens)

List variables for a Magento Cloud project or environment

Input parameters:

- `environment` (string, required): The environment name, e.g. 'staging', 'production'
- `level` (string): The variable level: 'project' or 'environment'. Lists all if omitted.
- `project` (string, required): The Magento Cloud project ID

### `list_services` (~68 tokens)

List services (MySQL, Redis, OpenSearch, RabbitMQ, etc.) in a Magento Cloud project with their versions and disk allocation

Input parameters:

- `environment` (string, required): The environment name, e.g. 'staging', 'production'
- `project` (string, required): The Magento Cloud project ID

### `execute_sql` (~66 tokens)

Execute a read-only SQL query on a Magento Cloud environment via SSH

Input parameters:

- `environment` (string, required): The environment name, e.g. 'staging', 'production'
- `project` (string, required): The Magento Cloud project ID
- `query` (string, required): The SQL query to execute

### `list_log_types` (~19 tokens)

List the available log types for Magento Cloud environments

### `get_environment_logs` (~104 tokens)

Read logs from a Magento Cloud environment via SSH. Use list_log_types to see available log types.

Input parameters:

- `environment` (string, required): The environment name, e.g. 'staging', 'production'
- `lines` (number): Number of lines to return (optional, defaults to 100)
- `project` (string, required): The Magento Cloud project ID
- `type` (string, required): The log type to read, e.g. 'deploy', 'error', 'cron'

### `get_environment_relationships` (~85 tokens)

Get the service relationships (database, redis, opensearch, rabbitmq, etc.) for a Magento Cloud environment via SSH. Returns connection details including host, port, username, password and URL for each service.

Input parameters:

- `environment` (string, required): The environment name, e.g. 'staging', 'production'
- `project` (string, required): The Magento Cloud project ID

### `set_cloud_config` (~202 tokens)

Set a Magento configuration value on a Cloud environment by running `bin/magento config:set` via SSH. Use the scope/scope_code parameters to target a specific website or store view.

Input parameters:

- `encrypted` (boolean): Encrypt the value before saving (for sensitive data like API keys).
- `environment` (string, required): The environment name, e.g. 'staging', 'integration'
- `path` (string, required): The configuration path, e.g. 'web/secure/base_url' or 'general/store_information/name'
- `project` (string, required): The Magento Cloud project ID
- `scope` (string): The configuration scope. Defaults to 'default' (global) if omitted.
- `scope_code` (string): The website code or store view code the scope applies to, e.g. 'base' or 'default'. Required when scope is 'websites' or 'stores'.
- `value` (string, required): The value to set for the configuration path

### `create_branch` (~94 tokens)

Create a new environment branch from integration. The new branch will be a clone of the integration environment.

Input parameters:

- `branch_name` (string, required): The branch name (ID) for the new environment, e.g. 'feature-xyz', 'bugfix-123'
- `project` (string, required): The Magento Cloud project ID
- `title` (string): Human-readable title for the branch. Defaults to the branch name if not provided.

### `push_branch` (~112 tokens)

Push a local git branch to a Magento Cloud project. Uses SSH certificate authentication — no separate git credentials needed. The branch must exist locally.

Input parameters:

- `local_branch` (string, required): Local branch name to push, e.g. 'feature-xyz'
- `project` (string, required): The Magento Cloud project ID
- `remote_branch` (string): Remote branch name. Defaults to the same as local_branch.
- `repo_path` (string, required): Absolute path to the local git repository, e.g. '/home/user/myproject'

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/juan-cinto-infracommerce-magento-cloud/mcp-magento-cloud#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 66
- 2026-08-01: 5
- 2026-07-31: 21
- 2026-07-30: 28
- 2026-07-28: 24
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/mcp-magento-cloud
- Socket report: https://socket.dev/npm/package/mcp-magento-cloud
- Repository: https://github.com/juan-cinto-infracommerce/mcp-magento-cloud
- Changelog RSS feed: https://verifymcp.io/servers/juan-cinto-infracommerce-magento-cloud/mcp-magento-cloud/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/juan-cinto-infracommerce-magento-cloud/mcp-magento-cloud/changelog.json
- HTML version of this page: https://verifymcp.io/servers/juan-cinto-infracommerce-magento-cloud/mcp-magento-cloud