Adobe Commerce + MooPoint: Complete MCP Integration

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

When integrated with MooPoint, 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 MooPoint, 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 MooPoint
• 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
• MooPoint installed and configured
• Compatible operating system (Web Platform, Mobile Web)

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 MooPoint

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

Explore GraphQL Schema

Introspect Adobe Commerce admin GraphQL schema

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

MCP Server Connection Failed

Symptoms: Connection timeout, Server unreachable, Test connection fails

Cause: Invalid server URL or server not accessible

Solution:

• Verify MCP server URL is correct and publicly accessible
• Check server supports HTTP or SSE transport protocol
• Ensure server is running and responding to health checks
• Test server URL in browser or with curl
• Review server logs for connection errors

OAuth Authentication Failing

Symptoms: OAuth redirect errors, Token refresh failures, Permission denied

Cause: Invalid OAuth credentials or misconfigured redirect URLs

Solution:

• Verify OAuth client ID and secret are correct
• Check redirect URL in OAuth provider matches MooPoint configuration
• Ensure all required scopes are configured
• Complete OAuth authorization flow fully
• Check OAuth provider allows the application

Tool Calling Not Working

Symptoms: Tools not appearing, Tool execution fails, LLM cannot access tools

Cause: MCP server not providing tools correctly or model limitations

Solution:

• Verify MCP server exposes tools in correct format
• Check that selected LLM model supports function calling
• Review tool definitions for correct parameter schemas
• Test MCP server independently to ensure tools work
• Try different LLM model that supports tool calling

API Key Errors

Symptoms: Invalid API key, Authentication failed, Rate limit errors

Cause: Incorrect or expired API keys for LLM providers

Solution:

• Verify API keys are correctly entered in Settings
• Check API key has not expired or been revoked
• Ensure API key has sufficient permissions
• Verify you have not exceeded rate limits or quotas
• Regenerate API key if issues persist

Model Switching Issues

Symptoms: Model not loading, Conversation context lost, Inconsistent behavior

Cause: Model compatibility or configuration issues

Solution:

• Ensure API key for selected model is configured
• Start new conversation when switching models
• Verify model supports required features (tool calling, etc.)
• Check model availability and status
• Review model-specific limitations and requirements

Adobe Commerce not appearing in MooPoint

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

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

Next Steps

Now that Adobe Commerce is integrated with MooPoint:

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

Need Help?

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