Adobe Commerce + MCP Inspector: Complete MCP Integration

Adobe Commerce is a MCP server that Adobe Commerce MCP server.

When integrated with MCP Inspector, you can:

• Analyze and explore Adobe Commerce GraphQL schema structure
• Write and test GraphQL queries and mutations for Adobe Commerce
• Interact with Adobe Commerce business logic through GraphQL

This guide provides step-by-step instructions to set up Adobe Commerce in MCP Inspector, including configuration, examples, and troubleshooting.

What You'll Achieve

After completing this setup:

• Adobe Commerce will be fully integrated and operational
• You can use Adobe Commerce tools directly in MCP Inspector
• All Adobe Commerce capabilities will be available for your workflows
• Access to 4 different tools

Prerequisites

Before starting, ensure you have:

• Node.js
• npm
• Adobe Commerce environment
• MCP Inspector installed and configured
• Compatible operating system (CLI Tool)

Installation

Step 1: Install Adobe Commerce

Install using npm:

npx -y @rafaelcg/adobe-commerce-dev-mcp@latest

Verify installation:

npx @rafaelcg/adobe-commerce-dev-mcp@latest --help

Configuration

Step 2: Configure MCP Inspector

1. Open MCP Inspector settings
2. Navigate to MCP server configuration
3. Add Adobe Commerce server with appropriate settings
4. Save and restart if needed

Examples

Once configured, you can use Adobe Commerce in MCP Inspector:

Explore GraphQL Schema

Introspect Adobe Commerce admin GraphQL schema

Ask MCP Inspector: "Show me the available GraphQL schema for product management in Adobe Commerce"

Expected Result: Detailed schema information including product types, fields, and available operations

Create Product Query

Build GraphQL query to retrieve product information

Ask MCP Inspector: "Help me write a GraphQL query to get product details including name, price, and inventory status"

Expected Result: Well-formed GraphQL query with proper field selection and structure

Customer Management Operation

Develop customer-related GraphQL operations

Ask MCP Inspector: "Create a GraphQL mutation to update customer profile information"

Expected Result: GraphQL mutation with proper input types and customer field updates

Order Processing Query

Build order management GraphQL operations

Ask MCP Inspector: "Write a GraphQL query to retrieve order history with product details and shipping information"

Expected Result: Complex GraphQL query with nested relationships and order data structure

Testing Your Setup

1. Launch MCP Inspector
2. Verify Adobe Commerce is available in the tools list
3. Test basic Adobe Commerce functionality

Troubleshooting

Common Issues

Schema Introspection Failed

Symptoms: Schema not accessible, GraphQL endpoint errors, Authentication failures

Cause: Invalid GraphQL endpoint URL or authentication token

Solution:

• Verify Adobe Commerce GraphQL endpoint is accessible
• Check admin integration token has proper permissions
• Test endpoint manually with GraphQL client
• Ensure Adobe Commerce instance is running and configured

NPM Package Installation Error

Symptoms: Package not found, Installation timeouts, Version conflicts

Cause: Network issues, package registry problems, or dependency conflicts

Solution:

• Clear npm cache: npm cache clean --force
• Try alternative registry: npm install --registry https://registry.npmjs.org/
• Check network connectivity and proxy settings
• Update npm to latest version: npm install -g npm@latest

GraphQL Operation Syntax Error

Symptoms: Syntax validation errors, Malformed query messages, Parser errors

Cause: Invalid GraphQL syntax or schema incompatibility

Solution:

• Validate GraphQL syntax with online validator
• Check field names match schema definitions
• Ensure proper query structure and formatting
• Use introspect_admin_schema to verify available fields

Windows Command Execution Error

Symptoms: Command not recognized, Execution policy errors, Path issues

Cause: Windows-specific command execution or security policy restrictions

Solution:

• Use cmd configuration: "command": "cmd", "args": ["/c", "npx", ...]
• Check PowerShell execution policy: Set-ExecutionPolicy RemoteSigned
• Verify Node.js and npm are in system PATH
• Run terminal as administrator if needed

Connection Failed

Symptoms: Inspector UI shows "Disconnected"

Cause: Server process exited or failed to start.

Solution:

• Check the terminal where you ran npx ... for error output from your server.
• Ensure your server prints JSON-RPC messages to stdout.

Tools Not Showing

Symptoms: Tool list is empty

Cause: Server did not send tools/list response or capabilities negotiation failed.

Solution:

• Check the "Console" or "Logs" tab in the Inspector to see the raw communication.
• Verify your server code correctly implements the ListToolsRequest handler.

Adobe Commerce not appearing in MCP Inspector

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check Adobe Commerce installation
• Restart MCP Inspector
• Check logs for error messages

Next Steps

Now that Adobe Commerce is integrated with MCP Inspector:

• Explore all Adobe Commerce capabilities through MCP Inspector
• Check out other MCP servers that work with MCP Inspector
• Join the MCP community for tips and support
• Consider contributing to Adobe Commerce development

Need Help?

• Search for Adobe Commerce documentation
• Check the MCP Inspector MCP guide
• Join the MCP community discussions