Skip to main content
Glama
elgentos

Magento 2 Development MCP Server

by elgentos

Config Show

config-show

View Magento 2 system configuration values to inspect settings across different scopes like default, website, or store levels for development and troubleshooting.

Instructions

View Magento 2 system configuration values

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoConfiguration path to show (optional, shows all if not specified)
scopeNoConfiguration scope (default, website, store)
scopeIdNoScope ID (website ID or store ID)

Implementation Reference

  • Handler function for the 'config-show' tool. Constructs the magerun2 config:show command based on input parameters (path, scope, scopeId) and executes it using the shared executeMagerun2Command helper, returning formatted results or error.
    async ({ path, scope, scopeId }) => {
      let command = `magerun2 config:show`;
    
      if (path) {
        command += ` "${path}"`;
      }
    
      if (scope) {
        command += ` --scope="${scope}"`;
      }
    
      if (scopeId) {
        command += ` --scope-id="${scopeId}"`;
      }
    
      const result = await executeMagerun2Command(command);
    
      if (!result.success) {
        return {
          content: [{
            type: "text",
            text: result.error
          }],
          isError: true
        };
      }
    
      return {
        content: [{
          type: "text",
          text: `Configuration values:\n\n${result.data}`
        }]
      };
    }
  • Input schema for the 'config-show' tool defining optional parameters: path (config path), scope (e.g., default/website/store), and scopeId (specific ID), validated with Zod.
    {
      title: "Config Show",
      description: "View Magento 2 system configuration values",
      inputSchema: {
        path: z.string()
          .optional()
          .describe("Configuration path to show (optional, shows all if not specified)"),
        scope: z.string()
          .optional()
          .describe("Configuration scope (default, website, store)"),
        scopeId: z.string()
          .optional()
          .describe("Scope ID (website ID or store ID)")
      }
    },
  • src/index.ts:723-774 (registration)
    Registration of the 'config-show' tool on the MCP server, specifying the tool name, schema, and handler function.
    server.registerTool(
      "config-show",
      {
        title: "Config Show",
        description: "View Magento 2 system configuration values",
        inputSchema: {
          path: z.string()
            .optional()
            .describe("Configuration path to show (optional, shows all if not specified)"),
          scope: z.string()
            .optional()
            .describe("Configuration scope (default, website, store)"),
          scopeId: z.string()
            .optional()
            .describe("Scope ID (website ID or store ID)")
        }
      },
      async ({ path, scope, scopeId }) => {
        let command = `magerun2 config:show`;
    
        if (path) {
          command += ` "${path}"`;
        }
    
        if (scope) {
          command += ` --scope="${scope}"`;
        }
    
        if (scopeId) {
          command += ` --scope-id="${scopeId}"`;
        }
    
        const result = await executeMagerun2Command(command);
    
        if (!result.success) {
          return {
            content: [{
              type: "text",
              text: result.error
            }],
            isError: true
          };
        }
    
        return {
          content: [{
            type: "text",
            text: `Configuration values:\n\n${result.data}`
          }]
        };
      }
    );
  • Shared helper utility used by 'config-show' (and other tools) to safely execute magerun2 commands, handle timeouts, parse JSON output, and provide Magento-specific error messages (e.g., not in Magento dir, magerun2 missing).
    async function executeMagerun2Command(command: string, parseJson: boolean = false): Promise<{
      success: true;
      data: any;
      rawOutput: string;
    } | {
      success: false;
      error: string;
      isError: true;
    }> {
      try {
        const { stdout, stderr } = await execAsync(command, {
          cwd: process.cwd(),
          timeout: 30000 // 30 second timeout
        });
    
        if (stderr && stderr.trim()) {
          console.error("magerun2 stderr:", stderr);
        }
    
        if (parseJson) {
          try {
            return { success: true, data: JSON.parse(stdout), rawOutput: stdout };
          } catch (parseError) {
            return {
              success: false,
              error: `Error parsing magerun2 JSON output: ${parseError}\n\nRaw output:\n${stdout}`,
              isError: true
            };
          }
        }
    
        return { success: true, data: stdout.trim(), rawOutput: stdout };
    
      } catch (error) {
        const errorMessage = error instanceof Error ? error.message : String(error);
    
        // Check if magerun2 is not found
        if (errorMessage.includes("command not found") || errorMessage.includes("not recognized")) {
          return {
            success: false,
            error: "Error: magerun2 command not found. Please ensure n98-magerun2 is installed and available in your PATH.\n\nInstallation instructions: https://github.com/netz98/n98-magerun2",
            isError: true
          };
        }
    
        // Check if not in Magento directory
        if (errorMessage.includes("not a Magento installation") || errorMessage.includes("app/etc/env.php")) {
          return {
            success: false,
            error: "Error: Current directory does not appear to be a Magento 2 installation. Please run this command from your Magento 2 root directory.",
            isError: true
          };
        }
    
        return {
          success: false,
          error: `Error executing magerun2 command: ${errorMessage}`,
          isError: true
        };
      }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'view' implies a read-only operation, but does not cover aspects like permissions required, rate limits, error handling, or what happens if parameters are omitted (e.g., showing all values). This leaves significant gaps in understanding the tool's behavior.

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?

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly.

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

Completeness2/5

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

Given the complexity of a configuration tool with 3 parameters and no annotations or output schema, the description is insufficient. It does not explain return values, error cases, or behavioral nuances like how 'scope' and 'scopeId' interact, leaving the agent with incomplete context for effective use.

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?

Schema description coverage is 100%, with clear descriptions for all parameters (e.g., 'path' as optional configuration path, 'scope' as configuration scope). The description adds no additional parameter semantics beyond the schema, so it meets the baseline for adequate but not enhanced coverage.

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

Purpose4/5

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

The description clearly states the verb ('view') and resource ('Magento 2 system configuration values'), making the purpose unambiguous. However, it does not explicitly differentiate from sibling tools like 'config-set' or 'config-store-get', which would require a more specific scope or comparison.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives such as 'config-set' for setting values or 'config-store-get' for store-specific configurations. It lacks context on prerequisites or scenarios where this tool is preferred, leaving usage decisions to inference.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elgentos/magento2-dev-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server