Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-magento-cloud List environments for project abc123"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP (Model Context Protocol) server for Adobe Commerce Cloud. Allows AI agents to interact with Magento Cloud projects — query databases, read logs, list environments, inspect activities, and more.
No PHP CLI required — uses the REST API and SSH directly.
Version | Description | Requirements |
v2.x (latest) | REST API + SSH directly. Browser login or API token. | Node.js 20+, |
v1.x | Wraps the | Node.js 20+, |
# Latest (v2.x)
npx -y mcp-magento-cloud
# v1.x (requires magento-cloud CLI)
npx -y mcp-magento-cloud@1.0.1Related MCP server: Magento MCP Server
Node.js 20+
ssh binary — Available by default on Linux/macOS
No setup required. The first time you use any tool, a browser window will open automatically for OAuth2 login via your Adobe/Magento account. Credentials are stored locally in ~/.config/mcp-magento-cloud/credentials.json and refreshed automatically.
You can also login manually:
npx -y -p mcp-magento-cloud mcp-magento-cloud-loginIf you prefer using an API token (e.g. for CI/CD), create one at https://accounts.magento.cloud/user/api-tokens and pass it as an environment variable (MAGENTO_CLOUD_CLI_TOKEN). When a token is set, browser login is skipped.
Security note: API tokens grant full access to all projects your account has access to. Treat them as sensitive secrets. If a token is compromised, revoke it immediately at the URL above.
In ~/.config/kilo/kilo.json:
{
"mcp": {
"magento-cloud": {
"type": "local",
"command": ["npx", "-y", "mcp-magento-cloud"]
}
}
}If using an API token instead of browser login, add the environment key:
{
"mcp": {
"magento-cloud": {
"type": "local",
"command": ["npx", "-y", "mcp-magento-cloud"],
"environment": {
"MAGENTO_CLOUD_CLI_TOKEN": "your-api-token-here"
}
}
}
}In claude_desktop_config.json:
{
"mcpServers": {
"magento-cloud": {
"command": "npx",
"args": ["-y", "mcp-magento-cloud"]
}
}
}In ~/.gemini/settings.json:
{
"mcpServers": {
"magento-cloud": {
"command": "npx",
"args": ["-y", "mcp-magento-cloud"]
}
}
}Tool | Description |
| List all projects available to the current user |
| List all environments for a project |
| Get detailed info about an environment |
| Get the public URLs of an environment |
| List recent activities with filters |
| Display the full log for an activity |
| List project or environment variables |
| List services with versions and disk allocation |
Tool | Description |
| Execute a read-only SQL query on the remote database |
| Read server logs (deploy, error, cron, etc.) |
| Get service connection details (host, port, credentials) |
| List available log types |
Tool | Description |
| Set a Magento config value via |
| Create a new environment branch cloned from integration |
| Push a local git branch to the project using SSH certificate auth |
SQL queries are validated — only SELECT, SHOW, DESCRIBE, and EXPLAIN are allowed
SQL comments are stripped and multiple statements are blocked to prevent injection
Production is protected — set_cloud_config refuses to run against the production environment; such changes must be made manually
SSH authentication uses temporary Ed25519 certificates signed by the Magento Cloud API
Browser login stores refresh tokens locally with 0600 permissions
API tokens should be treated as sensitive secrets — they grant full access to all projects
# Browser login will open automatically on first tool use
npx @modelcontextprotocol/inspector node dist/main.js
# Or with API token
MAGENTO_CLOUD_CLI_TOKEN=your-token npx @modelcontextprotocol/inspector node dist/main.jsgit clone https://github.com/juan-cinto-infracommerce/mcp-magento-cloud.git
cd mcp-magento-cloud
npm install
npm run build
npm startMIT
Create a new environment branch from integration. The new branch will be a clone of the integration environment.
Inputs: project (required), branch_name (required), title.
Execute a read-only SQL query on a Magento Cloud environment via SSH
Inputs: query (required), project (required), environment (required).
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.
Inputs: project (required), environment (required), id.
Get detailed information about a specific Magento Cloud environment (status, URLs, type, etc.)
Inputs: project (required), environment (required).
Read logs from a Magento Cloud environment via SSH. Use list_log_types to see available log types.
Inputs: type (required), project (required), environment (required), lines.
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.
Inputs: project (required), environment (required).
Get the public URLs of a Magento Cloud environment
Inputs: project (required), environment (required), primary.
List recent activities (deploys, pushes, crons, etc.) for a Magento Cloud environment or project
Inputs: project (required), environment (required), type, limit, +3 more.
List all environments for a Magento Cloud project
Inputs: project (required).
List the available log types for Magento Cloud environments
Inputs: no named parameters.
List all Magento Cloud projects available to the current user
Inputs: no named parameters.
List services (MySQL, Redis, OpenSearch, RabbitMQ, etc.) in a Magento Cloud project with their versions and disk allocation
Inputs: project (required), environment (required).
List variables for a Magento Cloud project or environment
Inputs: project (required), environment (required), level.
Push a local git branch to a Magento Cloud project. Uses SSH certificate authentication — no separate git credentials needed. The branch must exist locally.
Inputs: project (required), repo_path (required), local_branch (required), remote_branch.
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.
Inputs: path (required), value (required), project (required), environment (required), +3 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 15 tools
Each tool targets a distinct aspect of Magento Cloud management—projects, environments, activities, logs, variables, services, SQL, configuration, and branching. There is no functional overlap or confusion between tool purposes.
All tool names follow a consistent pattern: action_resource (e.g., list_log_types, get_environment_info, execute_sql, create_branch). The naming is uniform, using snake_case and clear verbs, ensuring predictability.
With 15 tools, the server covers the core operations needed for Magento Cloud management—from listing projects and environments to executing SQL, managing branches, and retrieving logs. The count is well-scoped for its domain.
The tool set covers major areas but has notable gaps: variables can only be listed (no create/update/delete), there is no tool for deleting branches or environments, and project-level creation/deletion is missing. This may hinder full lifecycle management.
Hosted Magento MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Deploy and manage Jade Hosting projects from AI clients. Jade account and OAuth required.
Develop, manage, and debug Railway projects, services, and deployments from within agents.
Persistent cloud workspaces for AI agents: run commands, edit files, use git and a browser.
