Adobe Commerce + MCPOmni-Connect: Complete MCP Integration

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

When integrated with MCPOmni-Connect, 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 MCPOmni-Connect, 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 MCPOmni-Connect
• 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
• MCPOmni-Connect installed and configured
• Compatible operating system (Python 3.9+, Windows, macOS, Linux, Docker)

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 MCPOmni-Connect

1. Open MCPOmni-Connect 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 MCPOmni-Connect:

Explore GraphQL Schema

Introspect Adobe Commerce admin GraphQL schema

Ask MCPOmni-Connect: "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 MCPOmni-Connect: "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 MCPOmni-Connect: "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 MCPOmni-Connect: "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 MCPOmni-Connect
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

Command Not Found

Symptoms: mcpomni-connect: command not found, CLI not accessible

Cause: Package not installed or not in PATH

Solution:

• Verify installation: pip show mcpomni-connect
• Ensure Python scripts directory is in PATH
• Try running with python -m: python -m mcpomni_connect
• Reinstall: pip install --upgrade mcpomni-connect

Configuration File Not Found

Symptoms: FileNotFoundError: mcp_config.yaml, Config not loading

Cause: Config file missing or incorrect path

Solution:

• Verify config file exists at specified path
• Use absolute path: --config /full/path/to/mcp_config.yaml
• Check file name is exactly mcp_config.yaml (case-sensitive)
• Validate YAML syntax with yamllint or online validator

MCP Server Connection Failures

Symptoms: Server not responding, Connection timeout, Transport error

Cause: Invalid server configuration or transport issues

Solution:

• Verify transport type matches server capabilities (stdio, sse, http, docker, npx)
• For stdio: ensure command and args are correct
• For SSE/HTTP: verify URL is accessible and server is running
• For Docker: ensure Docker daemon is running and image exists
• Check environment variables are set (e.g., GITHUB_TOKEN)
• Test server manually outside MCPOmni-Connect

Agent Mode Not Working

Symptoms: Agent fails to execute task, Reasoning loop errors, Tool calls failing

Cause: Insufficient LLM configuration or tool access issues

Solution:

• Ensure LLM API key is configured (OpenAI, Anthropic, etc.)
• Verify agent has access to necessary MCP server tools
• Check task description is clear and actionable
• Review agent logs for detailed error messages
• Try simpler task first to verify agent functionality

Orchestrator Mode Failures

Symptoms: Plan execution fails, Step coordination errors, Agent communication issues

Cause: Invalid plan structure or agent dependencies

Solution:

• Verify plan steps are clearly defined and sequential
• Ensure each step can be completed with available tools
• Check inter-agent communication is working
• Review orchestrator logs for step-by-step execution details
• Test individual plan steps in agent mode first

Docker Transport Errors

Symptoms: Container not starting, Docker connection refused, Port binding errors

Cause: Docker configuration or runtime issues

Solution:

• Verify Docker is installed and running: docker ps
• Check Docker image exists: docker images
• Ensure ports are not already in use
• Review container logs: docker logs <container_name>
• Verify network configuration allows container communication

FastAPI Integration Issues

Symptoms: Import errors, Async execution failures, Endpoint not responding

Cause: Incorrect async configuration or FastAPI version mismatch

Solution:

• Use run_agent_async() for async FastAPI endpoints
• Ensure FastAPI version is compatible (0.100.0+)
• Verify MCPOmniClient is initialized outside request handlers
• Check async event loop configuration
• Review FastAPI logs for detailed error messages

Adobe Commerce not appearing in MCPOmni-Connect

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

• Verify configuration syntax
• Check Adobe Commerce installation
• Restart MCPOmni-Connect
• Check logs for error messages

Next Steps

Now that Adobe Commerce is integrated with MCPOmni-Connect:

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

Need Help?

• Search for Adobe Commerce documentation
• Check the MCPOmni-Connect MCP guide
• Join the MCP community discussions