beginner⏱️ 10-20 minutes📅 Updated June 2026

Step-by-step guide to integrate Adobe Commerce MCP server with Msty Studio. Includes graphql schema introspection and graphql operation development.

Adobe Commerce + Msty Studio: Complete MCP Integration

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

When integrated with Msty Studio, 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 Msty Studio, 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 Msty Studio
  • 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
  • Msty Studio installed and configured
  • Compatible operating system (Desktop (Windows), Desktop (macOS), Desktop (Linux), Web Application)

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 Msty Studio

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

Explore GraphQL Schema

Introspect Adobe Commerce admin GraphQL schema

Ask Msty Studio: "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 Msty Studio: "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 Msty Studio: "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 Msty Studio: "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 Msty Studio
  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 Not Connecting

Symptoms: Server shows disconnected status, Tool calls fail, Timeout errors

Cause: Invalid configuration or server not accessible

Solution:

  • Verify MCP server URL or command is correct
  • For STDIO servers, ensure Node.js and npx are installed
  • Check firewall settings allow connections
  • Review server logs in Toolbox dashboard
  • Test server independently outside Msty

Local Model Performance Issues

Symptoms: Slow response times, High memory usage, System freezes

Cause: Model size exceeds hardware capabilities

Solution:

  • Use smaller model variants (e.g., Llama 3 8B instead of 70B)
  • Enable quantization for reduced memory footprint
  • Close other applications to free resources
  • Consider using cloud models for complex tasks
  • Check system requirements for selected model

Privacy Mode Not Working

Symptoms: Data appears to be sent externally, Telemetry detected, Unexpected network activity

Cause: Cloud models or online MCP servers configured

Solution:

  • Ensure using only local models (Llama.cpp-based)
  • Configure STDIO MCP servers instead of HTTP/SSE
  • Disable internet connection to verify offline capability
  • Review Insights dashboard for token usage (should be zero for local)
  • Check Privacy settings are configured correctly

Turnstile Workflow Failures

Symptoms: Workflow stops mid-execution, Steps not triggering, Incorrect branching

Cause: Logic errors or MCP server issues

Solution:

  • Test each workflow step individually
  • Verify all MCP servers in workflow are connected
  • Review workflow logic and conditions
  • Check Turnstile logs for execution errors
  • Simplify complex workflows for debugging

Cross-Device Sync Problems

Symptoms: Settings not syncing, Conversations missing, Inconsistent state

Cause: Sync service issues or Aurum plan not active

Solution:

  • Verify Aurum plan is active and current
  • Check internet connection on all devices
  • Manually trigger sync from settings
  • Review sync logs for errors
  • Contact support if issues persist

Adobe Commerce not appearing in Msty Studio

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

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

Next Steps

Now that Adobe Commerce is integrated with Msty Studio:

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

Need Help?

Related Resources

More Integrations

Explore other MCP servers that work with Msty Studio

Need Help?

Join the MCP community for support and discussions

Adobe Commerce + Msty Studio: MCP Setup Guide (2026)