Use Smithery MCP Server with Amazon Q CLI
Smithery is a MCP server that Gateway to 5000+ ready-made MCP servers with one-click deployment..
When integrated with Amazon Q CLI, you can:
- Access Smithery functionality through Amazon Q CLI
This guide provides step-by-step instructions to set up Smithery in Amazon Q CLI, including configuration, examples, and troubleshooting.
What You'll Achieve
After completing this setup:
- Smithery will be fully integrated and operational
- You can use Smithery tools directly in Amazon Q CLI
- All Smithery capabilities will be available for your workflows
Prerequisites
Before starting, ensure you have:
- Amazon Q CLI installed and configured
- Compatible operating system (Windows, macOS, Linux)
Installation
Step 1: Install Smithery
Configuration
Step 2: Configure Amazon Q CLI
- 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
- Authenticate
Set up authentication with AWS Builder ID or IAM Identity Center
q auth
Note: Follow interactive authentication flow
- Verify Installation
Test Q CLI installation and configuration
q doctor
- Install MCP Server
Install the MCP server you want to integrate
Note: Ensure server is accessible from command line
- Configure MCP Integration
Add MCP server configuration to Q CLI
Note: Use q config commands to set server parameters
- Test Integration
Verify MCP server works with Q CLI
q chat "Use Smithery to help me"
Configuration Details
Configure MCP servers through Q CLI commands:
# Configure MCP server integration
q config set mcp.servers.smithery.command "smithery"
q config set mcp.servers.smithery.args ""
q config set mcp.servers.smithery.env ""
# Verify configuration
q config list mcp.servers
Examples
Once configured, you can use Smithery in Amazon Q CLI:
Testing Your Setup
- Run q doctor to verify system health
- Start Q CLI chat session
- Ask Q to list available MCP tools
- Test specific Smithery functionality
Test commands:
q doctor
q chat
q config list mcp.servers
Troubleshooting
Common Issues
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
Smithery not appearing in Amazon Q CLI
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check Smithery installation
- Restart Amazon Q CLI
- Check logs for error messages
Next Steps
Now that Smithery is integrated with Amazon Q CLI:
- Explore all Smithery 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 Smithery development
Need Help?
- Search for Smithery documentation
- Check the Amazon Q CLI MCP guide
- Join the MCP community discussions