beginner⏱️ 10-20 minutes📅 Updated June 2026

Step-by-step guide to integrate AgentBay MCP server with GitHub Copilot (VS Code). Includes serverless environment management and browser integration.

AgentBay + GitHub Copilot (VS Code): Complete MCP Integration

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

When integrated with GitHub Copilot (VS Code), 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 GitHub Copilot (VS Code), 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 GitHub Copilot (VS Code)
  • All AgentBay capabilities will be available for your workflows
  • Access to 5 different tools

Prerequisites

Before starting, ensure you have:

  • GitHub Copilot (VS Code) installed and configured
  • Compatible operating system (Windows, macOS, Linux)

Installation

Step 1: Install AgentBay

Configuration

Step 2: Configure GitHub Copilot (VS Code)

  1. Locate your configuration file:

    • Windows: .vscode\\mcp.json in your project directory
    • macOS: .vscode/mcp.json in your project directory
    • Linux: .vscode/mcp.json in your project directory
  2. Add server configuration:

{
  "mcpServers": {
    "agentbay": {
      "command": "agentbay",
      "args": [],
      "env": {
        
      }
    }
  }
}

  1. Restart GitHub Copilot (VS Code)

Completely quit and restart GitHub Copilot (VS Code) to load the new configuration.

Examples

Once configured, you can use AgentBay in GitHub Copilot (VS Code):

Open Browser Session

Launch browser and navigate to specific website

Ask GitHub Copilot (VS Code): "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 GitHub Copilot (VS Code): "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 GitHub Copilot (VS Code): "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 GitHub Copilot (VS Code): "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. Start a new conversation in GitHub Copilot (VS Code)
  2. Ask GitHub Copilot (VS Code) to list available tools
  3. Try using AgentBay functionality

Test prompts:

  • "What MCP tools are available?"
  • "Use AgentBay to help with my code"
  • "Show me what AgentBay can do"

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 Configuration Not Loaded

Symptoms: MCP tools not appearing, Copilot does not recognize MCP server

Cause: Configuration file not in correct location or invalid JSON

Solution:

  • Verify .vscode/mcp.json exists in project root directory
  • Check JSON syntax is valid (no trailing commas, proper quotes)
  • Reload VS Code window after making configuration changes
  • Check VS Code Developer Tools (Help > Toggle Developer Tools) for errors

MCP Server Not Starting

Symptoms: Tools listed but not responding, Server connection errors

Cause: Server command path incorrect or dependencies missing

Solution:

  • Test the MCP server command independently in terminal
  • Verify all server prerequisites are installed
  • Check that command path is correct (use absolute paths if needed)
  • Ensure required environment variables are set in mcp.json
  • Review VS Code Output panel for MCP server error messages

GitHub Copilot Subscription Required

Symptoms: Copilot features grayed out, Unable to access Copilot Chat

Cause: No active GitHub Copilot subscription

Solution:

  • Sign up for GitHub Copilot subscription (Individual, Business, or Enterprise)
  • Verify subscription is active in GitHub account settings
  • Re-authenticate GitHub Copilot in VS Code
  • Check that VS Code is using correct GitHub account

VS Code Version Too Old

Symptoms: MCP configuration ignored, No mcp.json recognition

Cause: VS Code version below 1.99 does not have native MCP support

Solution:

  • Update VS Code to version 1.99 or later
  • Check current version: Help > About
  • Download latest version from code.visualstudio.com
  • After updating, reload window and verify MCP support

{server_name} Tools Not Working

Symptoms: Server connected but tools fail, Error messages when invoking tools

Cause: Server-specific configuration or authentication issues

Solution:

  • Verify all required environment variables for {server_name} are set
  • Check {server_name} documentation for specific prerequisites
  • Test {server_name} with another MCP client to isolate issue
  • Review error messages in VS Code Output panel for specific failures

AgentBay not appearing in GitHub Copilot (VS Code)

Symptoms: Server not listed, Tools not available

Cause: Configuration or installation issue

Solution:

  • Verify configuration syntax
  • Check AgentBay installation
  • Restart GitHub Copilot (VS Code)
  • Check logs for error messages

Next Steps

Now that AgentBay is integrated with GitHub Copilot (VS Code):

  • Explore all AgentBay capabilities through GitHub Copilot (VS Code)
  • Check out other MCP servers that work with GitHub Copilot (VS Code)
  • Join the MCP community for tips and support
  • Consider contributing to AgentBay development

Need Help?

Related Resources

More Integrations

Explore other MCP servers that work with GitHub Copilot (VS Code)

Need Help?

Join the MCP community for support and discussions

AgentBay + GitHub Copilot (VS Code): MCP Setup Guide (2026)