mcp-magento-cloud
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAGENTO_CLOUD_CLI_TOKEN | No | API token for authentication. If not provided, browser login is used. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List all Magento Cloud projects available to the current user |
| list_environmentsB | List all environments for a Magento Cloud project |
| get_environment_infoA | Get detailed information about a specific Magento Cloud environment (status, URLs, type, etc.) |
| get_environment_urlsB | Get the public URLs of a Magento Cloud environment |
| list_activitiesC | List recent activities (deploys, pushes, crons, etc.) for a Magento Cloud environment or project |
| get_activity_logA | 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. |
| list_variablesB | List variables for a Magento Cloud project or environment |
| list_servicesA | List services (MySQL, Redis, OpenSearch, RabbitMQ, etc.) in a Magento Cloud project with their versions and disk allocation |
| execute_sqlA | Execute a read-only SQL query on a Magento Cloud environment via SSH |
| list_log_typesB | List the available log types for Magento Cloud environments |
| get_environment_logsA | Read logs from a Magento Cloud environment via SSH. Use list_log_types to see available log types. |
| get_environment_relationshipsA | 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. |
| set_cloud_configA | Set a Magento configuration value on a Cloud environment by running |
| create_branchB | Create a new environment branch from integration. The new branch will be a clone of the integration environment. |
| push_branchA | Push a local git branch to a Magento Cloud project. Uses SSH certificate authentication — no separate git credentials needed. The branch must exist locally. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.