Adobe Commerce + MCPHub (mcp.nvim): Complete MCP Integration
Adobe Commerce is a MCP server that Adobe Commerce MCP server.
When integrated with MCPHub (mcp.nvim), 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 MCPHub (mcp.nvim), 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 MCPHub (mcp.nvim)
- 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
- MCPHub (mcp.nvim) installed and configured
- Compatible operating system (Neovim 0.9+, 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 MCPHub (mcp.nvim)
- Open MCPHub (mcp.nvim) 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 MCPHub (mcp.nvim):
Explore GraphQL Schema
Introspect Adobe Commerce admin GraphQL schema
Ask MCPHub (mcp.nvim): "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 MCPHub (mcp.nvim): "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 MCPHub (mcp.nvim): "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 MCPHub (mcp.nvim): "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 MCPHub (mcp.nvim)
- 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
Plugin Not Loading or Command Not Found
Symptoms: :MCPHub command not recognized, Plugin not appearing in :PlugStatus, No errors but plugin inactive
Cause: Plugin not properly installed or configuration error
Solution:
- Verify plugin is added to plugin manager configuration
- Run plugin manager install command (:PackerInstall, :PlugInstall, or Lazy auto-install)
- Check for errors in :messages after sourcing config
- Ensure dependencies (plenary.nvim, nui.nvim) are installed
- Restart Neovim completely
MCP Server Won't Start
Symptoms: Server status shows "Error", Red indicator on server, Server immediately stops after starting
Cause: Invalid server configuration or missing dependencies
Solution:
- Verify npx is installed and in PATH: npx --version
- Check MCP server package exists: npx -y @modelcontextprotocol/server-filesystem --help
- Review server configuration in setup() - verify command and args
- Check server logs in MCPHub interface for detailed error messages
- Ensure required environment variables are set (e.g., GITHUB_TOKEN)
- Test server manually in terminal: npx -y @modelcontextprotocol/server-filesystem /path
UI Not Displaying Correctly
Symptoms: Blank window, Garbled text, Layout issues, Missing borders
Cause: Terminal or Neovim rendering issues
Solution:
- Verify Neovim version is 0.9 or higher: nvim --version
- Try different border style in ui.border config ("single", "double", "rounded")
- Check terminal supports Unicode and 256 colors
- Update nui.nvim dependency to latest version
- Test with different colorscheme to rule out theme conflicts
Integration with Avante/CodeCompanion Not Working
Symptoms: AI assistant not seeing MCP tools, Tool calls failing, Integration not recognized
Cause: Integration not enabled or incompatible versions
Solution:
- Verify integration is enabled in config: integrations.avante = true
- Ensure Avante.nvim/CodeCompanion.nvim is installed and loaded
- Check versions are compatible - update both plugins to latest
- Restart Neovim after enabling integration
- Check :checkhealth for integration-specific warnings
Marketplace Not Loading
Symptoms: :MCPHubMarketplace shows empty list, Network error in marketplace, Timeout loading servers
Cause: Network connectivity issues or marketplace service unavailable
Solution:
- Verify internet connectivity
- Check firewall allows HTTPS connections
- Try again later if marketplace service is temporarily down
- Review proxy settings if behind corporate firewall
- Check :messages for detailed network error messages
Project-Local Config Not Loading
Symptoms: .mcphub.json ignored, Project servers not appearing, Only global config loaded
Cause: Config file location or format issues
Solution:
- Verify .mcphub.json is in project root (same directory as .git)
- Check JSON syntax is valid using jsonlint or similar tool
- Ensure file name is exactly .mcphub.json (case-sensitive)
- Restart Neovim after creating/modifying project config
- Check file permissions are readable
Adobe Commerce not appearing in MCPHub (mcp.nvim)
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Adobe Commerce installation
- Restart MCPHub (mcp.nvim)
- Check logs for error messages
Next Steps
Now that Adobe Commerce is integrated with MCPHub (mcp.nvim):
- Explore all Adobe Commerce capabilities through MCPHub (mcp.nvim)
- Check out other MCP servers that work with MCPHub (mcp.nvim)
- Join the MCP community for tips and support
- Consider contributing to Adobe Commerce development
Need Help?
- Search for Adobe Commerce documentation
- Check the MCPHub (mcp.nvim) MCP guide
- Join the MCP community discussions