AgentBay + Amp: Complete MCP Integration

AgentBay is a MCP server that An MCP server for providing serverless cloud infrastructure for AI agents..

When integrated with Amp, 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 Amp, 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 Amp
• All AgentBay capabilities will be available for your workflows
• Access to 5 different tools

Prerequisites

Before starting, ensure you have:

• Amp installed and configured
• Compatible operating system (macOS, Linux, Windows (WSL))

Installation

Step 1: Install AgentBay

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 AgentBay in Amp:

### Open Browser Session

Launch browser and navigate to specific website

**Ask Amp:** "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 Amp:** "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 Amp:** "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 Amp:** "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

1. Launch Amp
2. Verify AgentBay is available in the tools list
3. Test basic AgentBay functionality



## 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

#### 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

#### AgentBay not appearing in Amp

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

**Cause:** Configuration or installation issue

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



## Next Steps

Now that AgentBay is integrated with Amp:

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

## Need Help?

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