Adobe Commerce + Klavis AI: Complete MCP Integration
Adobe Commerce is a MCP server that Adobe Commerce MCP server.
When integrated with Klavis AI, 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 Klavis AI, 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 Klavis AI
- 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
- Klavis AI installed and configured
- Compatible operating system (Cloud (klavis.ai), Self-Hosted (Docker), Python SDK, TypeScript SDK)
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 Klavis AI
- Open Klavis AI settings
- Navigate to MCP server configuration
- Add Adobe Commerce server with appropriate settings
- Save and restart if needed
Examples
Once configured, you can use Adobe Commerce in Klavis AI:
Explore GraphQL Schema
Introspect Adobe Commerce admin GraphQL schema
Ask Klavis AI: "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 Klavis AI: "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 Klavis AI: "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 Klavis AI: "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
- Launch Klavis AI
- Verify Adobe Commerce is available in the tools list
- 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
API Authentication Failed
Symptoms: 401 Unauthorized errors, Invalid API key message
Cause: Missing or incorrect API key
Solution:
- Verify API key is correctly copied from klavis.ai dashboard
- Check API key is set in environment variable or code
- Ensure API key has not expired
- Regenerate API key if necessary
OAuth Authorization Errors
Symptoms: OAuth redirect failures, Authentication loop, Token refresh errors
Cause: OAuth credentials not configured or expired
Solution:
- Complete OAuth authorization flow for required services
- Check redirect URLs are correctly configured
- Verify OAuth app credentials in service provider settings
- Contact Klavis support for OAuth troubleshooting
Tool Call Failures
Symptoms: Tool not found errors, Execution timeouts, Rate limit errors
Cause: Tool not properly configured or service rate limits exceeded
Solution:
- Verify tool name matches available tools list
- Check service-specific rate limits and quotas
- Ensure required parameters are provided correctly
- Review Klavis API logs for detailed error messages
Context Window Overload
Symptoms: Too many tools error, Context length exceeded, Slow responses
Cause: Too many tools exposed to AI agent at once
Solution:
- Use Strata Progressive Discovery to expose tools hierarchically
- Reduce number of simultaneous MCP servers in Strata configuration
- Filter tools based on current task context
- Enable intelligent tool filtering in Strata settings
Docker Deployment Issues
Symptoms: Container fails to start, Port conflicts, Connection refused
Cause: Docker configuration or port binding errors
Solution:
- Ensure Docker is installed and running
- Check port 5000 is not already in use (or change port mapping)
- Verify Docker image pulled successfully
- Check container logs: docker logs <container-id>
Adobe Commerce not appearing in Klavis AI
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Adobe Commerce installation
- Restart Klavis AI
- Check logs for error messages
Next Steps
Now that Adobe Commerce is integrated with Klavis AI:
- Explore all Adobe Commerce capabilities through Klavis AI
- Check out other MCP servers that work with Klavis AI
- Join the MCP community for tips and support
- Consider contributing to Adobe Commerce development
Need Help?
- Search for Adobe Commerce documentation
- Check the Klavis AI MCP guide
- Join the MCP community discussions