mcp-magento-cloud

set_cloud_config

Set a Magento Cloud environment configuration value using SSH, with optional scope and scope_code to target specific websites or stores.

Instructions

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>",
      "environment": "<environment>",
      "path": "<path>",
      "value": "<value>"
    },
    "name": "set_cloud_config"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.0Jul 29, 2026

TDQS

A4/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears full responsibility. It accurately describes the SSH command execution and scope targeting, but omits details about potential side effects, permissions, or error behavior. It is adequate but lacks depth.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences front-load the action and provide essential scope guidance with no wasted words. Efficiently structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the high schema coverage and no output schema, the description covers the core purpose and scope usage. It lacks details on encrypted flag behavior or success/failure response, but is mostly complete for a mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the baseline is 3. The description adds minor context about scope/scope_code beyond the schema, but does not significantly enhance understanding of other parameters like path or encrypted.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Set' and the resource 'Magento configuration value on a Cloud environment', and specifies the method 'by running bin/magento config:set via SSH'. It differentiates from siblings by focusing on a write/config operation, and mentions scope targeting.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context on when to use scope/scope_code parameters, but does not explicitly list alternatives or when not to use the tool. It implies usage for configuration setting without exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server