AgentBay + Amazon Q CLI: Complete MCP Integration
AgentBay is a MCP server that An MCP server for providing serverless cloud infrastructure for AI agents..
When integrated with Amazon Q CLI, you can:
- One-click environment session management with automatic scaling
- Web browser access and automation within cloud environments
- File management and manipulation in cloud environments
This guide provides step-by-step instructions to set up AgentBay in Amazon Q CLI, including configuration, examples, and troubleshooting.
What You'll Achieve
After completing this setup:
- AgentBay will be fully integrated and operational
- You can use AgentBay tools directly in Amazon Q CLI
- All AgentBay capabilities will be available for your workflows
- Access to 5 different tools
Prerequisites
Before starting, ensure you have:
- Amazon Q CLI installed and configured
- Compatible operating system (Windows, macOS, Linux)
Installation
Step 1: Install AgentBay
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 AgentBay to help me"
Configuration Details
Configure MCP servers through Q CLI commands:
# Configure MCP server integration
q config set mcp.servers.agentbay.command "agentbay"
q config set mcp.servers.agentbay.args ""
q config set mcp.servers.agentbay.env ""
# Verify configuration
q config list mcp.servers
Examples
Once configured, you can use AgentBay in Amazon Q CLI:
Open Browser Session
Launch browser and navigate to specific website
Ask Amazon Q CLI: "Open browser with wuying-agentbay and access wuying.aliyun.com"
Expected Result: Browser session started with navigation to specified URL and screen streaming enabled
Development Environment Setup
Create isolated development environment for coding project
Ask Amazon Q CLI: "Set up a Python development environment with required packages for data analysis"
Expected Result: Linux environment created with Python, pip, and data analysis libraries installed
File Processing Workflow
Upload, process, and download files using cloud resources
Ask Amazon Q CLI: "Upload my dataset.csv, run data processing script, and download the results"
Expected Result: File uploaded, processing completed in cloud environment, results available for download
Multi-Agent Deployment
Deploy multiple AI agents for parallel processing
Ask Amazon Q CLI: "Deploy 5 AI agents for parallel image processing tasks with load balancing"
Expected Result: Multiple agent instances deployed, work distributed, and results aggregated
Testing Your Setup
- Run q doctor to verify system health
- Start Q CLI chat session
- Ask Q to list available MCP tools
- Test specific AgentBay functionality
Test commands:
q doctor
q chat
q config list mcp.servers
Troubleshooting
Common Issues
API Key Authentication Failed
Symptoms: Access denied errors, Invalid API key messages, 401 Unauthorized
Cause: Invalid or expired API key
Solution:
- Verify API key is correct and active in AgentBay Console
- Check API key permissions and quotas
- Regenerate API key if expired or compromised
- Ensure API key is properly URL-encoded in SSE endpoint
Concurrent Instance Limit Exceeded
Symptoms: Resource allocation errors, Instance creation failures
Cause: Public beta limit of 10 concurrent instances reached
Solution:
- Wait for existing instances to complete or terminate them
- Optimize workflows to use fewer concurrent instances
- Consider upgrading to production plan for higher limits
- Monitor instance usage and implement resource pooling
Environment Session Lost
Symptoms: Session disconnection, State not persisted, Data loss
Cause: Network connectivity issues or session timeout
Solution:
- Use EXTERNALID parameter for persistent sessions
- Implement session restoration mechanisms
- Save work frequently to persistent storage
- Check network stability and connection quality
Screen Streaming Performance Issues
Symptoms: Lag in browser streaming, Poor video quality, Connection drops
Cause: Network bandwidth limitations or high latency
Solution:
- Check internet connection speed and stability
- Use lower quality settings for better performance
- Choose nearest edge location for better latency
- Optimize browser usage for streaming performance
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
AgentBay not appearing in Amazon Q CLI
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check AgentBay installation
- Restart Amazon Q CLI
- Check logs for error messages
Next Steps
Now that AgentBay is integrated with Amazon Q CLI:
- Explore all AgentBay 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 AgentBay development
Need Help?
- Search for AgentBay documentation
- Check the Amazon Q CLI MCP guide
- Join the MCP community discussions