Skip to main content
Glama
elgentos

Magento 2 Development MCP Server

by elgentos

Setup DI Compile

setup-di-compile

Compile Magento 2 dependency injection configuration to update and optimize application dependencies for proper functionality.

Instructions

Compile Magento 2 dependency injection configuration

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the `magerun2 setup:di:compile` command via the shared executeMagerun2Command helper and formats the tool response with success or error content.
    async () => {
      const command = `magerun2 setup:di:compile`;
      const result = await executeMagerun2Command(command);
    
      if (!result.success) {
        return {
          content: [{
            type: "text",
            text: result.error
          }],
          isError: true
        };
      }
    
      return {
        content: [{
          type: "text",
          text: `DI compilation completed:\n\n${result.data}`
        }]
      };
    }
  • The input/output schema for the tool, including title, description, and an empty inputSchema indicating no parameters are required.
    {
      title: "Setup DI Compile",
      description: "Compile Magento 2 dependency injection configuration",
      inputSchema: {}
    },
  • src/index.ts:1026-1054 (registration)
    The server.registerTool call that registers the 'setup-di-compile' tool with its schema and handler function.
    server.registerTool(
      "setup-di-compile",
      {
        title: "Setup DI Compile",
        description: "Compile Magento 2 dependency injection configuration",
        inputSchema: {}
      },
      async () => {
        const command = `magerun2 setup:di:compile`;
        const result = await executeMagerun2Command(command);
    
        if (!result.success) {
          return {
            content: [{
              type: "text",
              text: result.error
            }],
            isError: true
          };
        }
    
        return {
          content: [{
            type: "text",
            text: `DI compilation completed:\n\n${result.data}`
          }]
        };
      }
    );
  • Shared helper function used by 'setup-di-compile' and other tools to safely execute magerun2 commands, handle timeouts, parse JSON output, and provide Magento-specific error messages.
    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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('compile') but doesn't explain what this entails—whether it's a read-only operation, modifies files, requires specific permissions, or has side effects like caching changes. This lack of detail is a significant gap for a tool with potential system impacts.

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 any fluff or redundant information. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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

Completeness3/5

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

Given the tool has no parameters and no output schema, the description provides a basic purpose but lacks completeness. It doesn't cover behavioral aspects like what 'compile' does operationally, potential outputs, or integration with sibling tools, which is important for a setup-related command in a development environment.

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

Parameters4/5

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

The tool has zero parameters, and schema description coverage is 100%, so there's no need for parameter details in the description. The description correctly omits parameter information, earning a high score for not adding unnecessary content, though it doesn't explicitly state 'no parameters required' which could slightly improve clarity.

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 ('compile') and resource ('Magento 2 dependency injection configuration'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get-di-preferences' or 'setup-upgrade', which prevents a perfect score.

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 during development, deployment, or troubleshooting scenarios. There's no mention of prerequisites, related tools, or typical use cases, leaving the agent with minimal context for selection.

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