Adobe Commerce + mcp-agent: Complete MCP Integration

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

When integrated with mcp-agent, 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-agent, 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-agent
• 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-agent installed and configured
• Compatible operating system (Python 3.9+, pip Installation, uv Installation, Temporal (Optional))

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-agent

1. Open mcp-agent 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-agent:

Explore GraphQL Schema

Introspect Adobe Commerce admin GraphQL schema

Ask mcp-agent: "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-agent: "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-agent: "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-agent: "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-agent
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

Import Error - Module Not Found

Symptoms: ModuleNotFoundError: No module named mcp_agent, Import fails

Cause: mcp-agent not installed or wrong Python environment

Solution:

• Verify installation: pip show mcp-agent
• Ensure using correct Python environment/virtualenv
• Reinstall: pip install --upgrade mcp-agent
• Check Python version is 3.9 or higher

MCP Server Connection Failures

Symptoms: Server not starting, Connection timeout, Tool execution errors

Cause: Invalid MCP server configuration or missing dependencies

Solution:

• Verify npx is installed and accessible (required for stdio servers)
• Check MCP server package name and arguments are correct
• Test server independently: npx -y @modelcontextprotocol/server-filesystem /path
• Review agent logs for detailed error messages
• Ensure required environment variables are set

LLM API Authentication Errors

Symptoms: 401 Unauthorized, API key invalid, Provider authentication failed

Cause: Missing or incorrect API keys for LLM provider

Solution:

• Set environment variables: ANTHROPIC_API_KEY, OPENAI_API_KEY, etc.
• Verify API key is valid and has correct permissions
• Check API key format matches provider requirements
• Pass api_key parameter explicitly in Agent initialization

Workflow Execution Failures

Symptoms: Workflow hangs, Timeout errors, Incomplete results

Cause: Workflow pattern misconfiguration or task complexity

Solution:

• Increase timeout values for long-running tasks
• Break complex workflows into smaller steps
• Verify all workflow dependencies are available
• Check Temporal backend is running (for production deployments)
• Review workflow logs for specific error messages

Temporal Backend Connection Issues

Symptoms: Cannot connect to Temporal, Workflow registration fails, Worker errors

Cause: Temporal server not running or misconfigured

Solution:

• Verify Temporal server is running: temporal server health
• Check Temporal connection settings (host, port, namespace)
• Ensure Temporal workers are registered correctly
• Review Temporal server logs for connection errors
• Start local Temporal dev server: temporal server start-dev

Performance Issues with Large Workflows

Symptoms: Slow execution, High memory usage, Timeout errors

Cause: Inefficient workflow design or resource constraints

Solution:

• Use map-reduce pattern for parallelizable tasks
• Implement batching for large data processing
• Enable Temporal backend for better resource management
• Monitor agent memory usage and optimize task size
• Consider streaming responses for large outputs

Adobe Commerce not appearing in mcp-agent

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check Adobe Commerce installation
• Restart mcp-agent
• Check logs for error messages

Next Steps

Now that Adobe Commerce is integrated with mcp-agent:

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

Need Help?

• Search for Adobe Commerce documentation
• Check the mcp-agent MCP guide
• Join the MCP community discussions