Adobe Commerce + Amp: Complete MCP Integration

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

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

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 Amp

1. Locate your configuration file:

2. Add server configuration:

Configure MCP servers in VS Code/Cursor settings.json:

```json
{
  "amp.mcpServers": {
    "playwright": {
      "command": "npx",
      "args": ["-y", "@playwright/mcp@latest", "--headless", "--isolated"]
    },
    "semgrep": {
      "url": "https://mcp.semgrep.ai/mcp"
    },
    "sourcegraph": {
      "url": "${SRC_ENDPOINT}/.api/mcp/v1",
      "headers": {
        "Authorization": "token ${SRC_ACCESS_TOKEN}"
      }
    },
    "linear": {
      "command": "npx",
      "args": ["mcp-remote", "https://mcp.linear.app/sse"]
    }
  }
}

Or add servers via CLI:

# Add HTTP-based server
amp mcp add sourcegraph --header "Authorization=token your-token" https://sourcegraph.example.com/.api/mcp/v1

# Add SSE-based server
amp mcp add linear https://mcp.linear.app/sse

# OAuth login for authenticated servers
amp mcp oauth login my-server \
  --server-url https://example.com/.api/mcp/v1 \
  --client-id your-client-id \
  --client-secret your-client-secret \
  --scopes "openid,profile,email"

3. **Restart Amp**

Completely quit and restart Amp to load the new configuration.



## Examples

Once configured, you can use Adobe Commerce in Amp:

### Explore GraphQL Schema

Introspect Adobe Commerce admin GraphQL schema

**Ask Amp:** "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 Amp:** "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 Amp:** "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 Amp:** "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 Amp
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 not appearing in tools, Connection timeout, Authentication errors

**Cause:** Invalid configuration, missing credentials, or network issues

**Solution:**
- Verify server URL and command are correct
- Check environment variables are set properly
- For OAuth servers, run amp mcp oauth login
- Review amp logs for error messages

#### Tool Execution Fails

**Symptoms:** MCP tools available but not working, Error messages during execution

**Cause:** Server dependencies missing or permission issues

**Solution:**
- Verify required environment variables are configured
- Check amp.permissions settings for tool restrictions
- Test MCP server independently
- Review server-specific documentation

#### Permission Denied

**Symptoms:** Tool blocked by permission system, Ask prompts for every action

**Cause:** Permission rules restricting MCP tool usage

**Solution:**
- Review amp.permissions in settings.json
- Add allow rules for trusted MCP servers
- Use amp permissions edit to modify rules

#### Adobe Commerce not appearing in Amp

**Symptoms:** Server not listed, Tools not available

**Cause:** Configuration or installation issue

**Solution:**
- Verify configuration syntax
- Check Adobe Commerce installation
- Restart Amp
- Check logs for error messages



## Next Steps

Now that Adobe Commerce is integrated with Amp:

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

## Need Help?

- Search for [Adobe Commerce documentation](https://www.mcpstack.org)
- Check the [Amp MCP guide](https://www.mcpstack.org/clients)
- Join the MCP community discussions