beginner⏱️ 15-25 minutes📅 Updated June 2026

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

Adobe Commerce + Amazon Q CLI: Complete MCP Integration

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

When integrated with Amazon Q CLI, 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 Amazon Q CLI, 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 Amazon Q CLI
  • 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
  • Amazon Q CLI installed and configured
  • Compatible operating system (Windows, macOS, Linux)

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 Amazon Q CLI

  1. Install Amazon Q CLI

Download and install Q CLI for your platform

Visit: https://docs.aws.amazon.com/amazonq/latest/qdeveloper-ug/command-line-installing.html

  1. Authenticate

Set up authentication with AWS Builder ID or IAM Identity Center

q auth

Note: Follow interactive authentication flow

  1. Verify Installation

Test Q CLI installation and configuration

q doctor
  1. Install MCP Server

Install the MCP server you want to integrate

Note: Ensure server is accessible from command line

  1. Configure MCP Integration

Add MCP server configuration to Q CLI

Note: Use q config commands to set server parameters

  1. Test Integration

Verify MCP server works with Q CLI

q chat "Use Adobe Commerce to help me"

Configuration Details

Configure MCP servers through Q CLI commands:

# Configure MCP server integration
q config set mcp.servers.adobe-commerce.command "npx"
q config set mcp.servers.adobe-commerce.args ""-y", "@rafaelcg/adobe-commerce-dev-mcp@latest""
q config set mcp.servers.adobe-commerce.env ""

# Verify configuration
q config list mcp.servers

Examples

Once configured, you can use Adobe Commerce in Amazon Q CLI:

Explore GraphQL Schema

Introspect Adobe Commerce admin GraphQL schema

Ask Amazon Q CLI: "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 Amazon Q CLI: "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 Amazon Q CLI: "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 Amazon Q CLI: "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. Run q doctor to verify system health
  2. Start Q CLI chat session
  3. Ask Q to list available MCP tools
  4. Test specific Adobe Commerce functionality

Test commands:

q doctor

q chat

q config list mcp.servers

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

Installation Failed

Symptoms: Q command not found, Installation errors

Cause: Incomplete installation or PATH issues

Solution:

  • Verify installer completed successfully
  • Check PATH environment variable includes Q CLI
  • Try running q doctor for diagnostics
  • Reinstall using platform-specific method

Authentication Problems

Symptoms: Auth errors, Cannot connect to AWS services

Cause: Invalid credentials or network issues

Solution:

  • Run q auth to re-authenticate
  • Verify AWS Builder ID or IAM credentials
  • Check network connectivity to AWS
  • Ensure proper AWS permissions are set

MCP Server Not Found

Symptoms: Server command not found, MCP tools unavailable

Cause: Server not installed or not in PATH

Solution:

  • Verify MCP server installation
  • Check server executable permissions
  • Use absolute path in configuration
  • Test server independently with direct command

Configuration Errors

Symptoms: Config commands fail, Settings not persisting

Cause: Invalid configuration syntax or permissions

Solution:

  • Check Q CLI configuration file permissions
  • Verify configuration syntax is correct
  • Use q config list to review current settings
  • Report issues with q issue command

Adobe Commerce not appearing in Amazon Q CLI

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

  • Verify configuration syntax
  • Check Adobe Commerce installation
  • Restart Amazon Q CLI
  • Check logs for error messages

Next Steps

Now that Adobe Commerce is integrated with Amazon Q CLI:

  • Explore all Adobe Commerce capabilities through Amazon Q CLI
  • Check out other MCP servers that work with Amazon Q CLI
  • 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 Amazon Q CLI

Need Help?

Join the MCP community for support and discussions

Adobe Commerce + Amazon Q CLI: MCP Setup Guide (2026)