Adobe Commerce + OpenSumi: Complete MCP Integration

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

When integrated with OpenSumi, 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 OpenSumi, 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 OpenSumi
• 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
• OpenSumi installed and configured
• Compatible operating system (Web (Browser-based), Electron Desktop, Container (Docker/K8s), Framework Integration)

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 OpenSumi

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

Explore GraphQL Schema

Introspect Adobe Commerce admin GraphQL schema

Ask OpenSumi: "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 OpenSumi: "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 OpenSumi: "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 OpenSumi: "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 OpenSumi
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

Dependency Installation Failures

Symptoms: Yarn/npm install errors, Missing packages, Version conflicts

Cause: Incompatible Node.js version or network issues

Solution:

• Ensure Node.js 16+ is installed
• Use yarn for standard installation, npm for lite version
• Clear package cache: yarn cache clean or npm cache clean --force
• Check network connectivity and proxy settings

Workspace Not Loading

Symptoms: Empty workspace, Files not showing, Permission errors

Cause: Incorrect workspace path or permissions

Solution:

• Verify MY_WORKSPACE environment variable is set correctly
• Check file system permissions for workspace directory
• Use absolute path for workspace location
• Default workspace is tools/workspace in repository

VSCode Extension Compatibility

Symptoms: Extension not loading, Extension errors, Missing features

Cause: Extension API incompatibility or missing dependencies

Solution:

• Verify extension is compatible with VSCode extension API used by OpenSumi
• Check extension documentation for known issues
• Try downloading extensions via yarn run download-extension
• Some extensions may require OpenSumi-specific adaptation

WebWorker Compilation Errors (Lite Version)

Symptoms: Compile-worker fails, Language service not working, Syntax highlighting broken

Cause: WebWorker build configuration issues

Solution:

• Run npm run compile-worker before starting
• Ensure all dependencies are installed correctly
• Check browser console for WebWorker loading errors
• Clear browser cache and rebuild

MCP Client Connection Failures

Symptoms: Cannot connect to MCP server, Tool discovery fails, MCP errors in console

Cause: MCP server not running or incorrect configuration

Solution:

• Verify MCP server is running and accessible
• Check MCP server URL in OpenSumi configuration
• Review MCP client integration code for errors
• Check browser/Electron console for detailed error messages

Electron App Not Starting

Symptoms: Electron window not opening, White screen, App crashes on launch

Cause: Electron build issues or IPC communication errors

Solution:

• Ensure Electron dependencies are installed correctly
• Check Electron version compatibility (15+)
• Review IPC communication setup in configuration
• Check Electron dev tools console for errors

Adobe Commerce not appearing in OpenSumi

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

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

Next Steps

Now that Adobe Commerce is integrated with OpenSumi:

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

Need Help?

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