Adobe Commerce + mcp-use: Complete MCP Integration

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

When integrated with mcp-use, 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-use, 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-use
• 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-use installed and configured
• Compatible operating system (Python 3.8+, Node.js 16+, pip Installation, npm/yarn Installation)

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

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

Explore GraphQL Schema

Introspect Adobe Commerce admin GraphQL schema

Ask mcp-use: "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-use: "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-use: "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-use: "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-use
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 Refused or Server Unreachable

Symptoms: ECONNREFUSED error, Connection timeout, Cannot reach server

Cause: MCP server not running or incorrect URL

Solution:

• Verify MCP server is running and accessible
• Check server URL is correct (protocol, host, port, path)
• Test server URL in browser or with curl to confirm it responds
• Ensure firewall allows connections to server port
• Verify CORS settings if accessing from browser

Import Errors or Module Not Found

Symptoms: ModuleNotFoundError: mcp_use, Cannot find module "mcp-use"

Cause: Package not installed or wrong environment

Solution:

• Verify installation: pip show mcp-use (Python) or npm list mcp-use (JS)
• Ensure using correct Python virtual environment or Node.js project
• Reinstall package: pip install --upgrade mcp-use or npm install mcp-use
• Check package.json or requirements.txt includes mcp-use

Tool Discovery Returns Empty List

Symptoms: list_tools() returns [], No tools available, Tools not found

Cause: MCP server not properly configured or not exposing tools

Solution:

• Verify MCP server is properly initialized and configured
• Check server logs to confirm tools are registered
• Test server directly with MCP inspector or test client
• Ensure server implements MCP protocol correctly
• Verify transport type (HTTP/SSE) matches server configuration

Tool Execution Fails or Returns Errors

Symptoms: Tool call throws exception, Invalid arguments error, Execution timeout

Cause: Incorrect arguments or server-side execution failure

Solution:

• Verify tool arguments match schema definition from list_tools()
• Check required arguments are provided with correct types
• Review server logs for detailed error messages
• Test tool with minimal valid arguments first
• Increase timeout if tool requires longer execution time

LangChain.js Integration Not Working

Symptoms: getLangChainTools() fails, Tools not recognized by agent, Type errors

Cause: Version mismatch or incorrect integration setup

Solution:

• Ensure LangChain.js version is compatible with mcp-use
• Verify TypeScript version meets requirements
• Check tool schema conversion is working correctly
• Use latest versions of both mcp-use and LangChain.js
• Review LangChain.js documentation for agent setup

Transport Type Errors (HTTP vs SSE)

Symptoms: SSE connection fails, HTTP polling not working, Event stream errors

Cause: Mismatch between client transport and server capabilities

Solution:

• Verify server supports the transport type you are using
• Try alternative transport: switch between "http" and "sse"
• Check server documentation for supported transport types
• For SSE, ensure server sends proper Content-Type: text/event-stream
• For HTTP, verify server accepts POST requests with JSON payload

Adobe Commerce not appearing in mcp-use

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

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

Next Steps

Now that Adobe Commerce is integrated with mcp-use:

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

Need Help?

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