AgentBay + Microsoft Copilot Studio: Complete MCP Integration
AgentBay is a MCP server that An MCP server for providing serverless cloud infrastructure for AI agents..
When integrated with Microsoft Copilot Studio, 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 Microsoft Copilot Studio, 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 Microsoft Copilot Studio
- All AgentBay capabilities will be available for your workflows
- Access to 5 different tools
Prerequisites
Before starting, ensure you have:
- Microsoft Copilot Studio installed and configured
- Compatible operating system (Web Browser, Microsoft 365)
Installation
Step 1: Install AgentBay
Configuration
Step 2: Configure Microsoft Copilot Studio
- Enable Generative Orchestration
Generative Orchestration must be enabled in your Copilot Studio environment to use MCP
Visit: https://learn.microsoft.com/en-us/microsoft-copilot-studio/agent-extend-action-mcp
Note: This is a prerequisite - MCP will not work without it
- Access Copilot Studio
Log in to Microsoft Copilot Studio with appropriate permissions to create and configure agents
Visit: https://copilotstudio.microsoft.com
Note: Requires organizational access or trial subscription
- Navigate to Connectors
In Copilot Studio, go to the Connectors section where you can add new integrations
Note: Location may vary based on interface updates
- Create MCP Connector
Click "Add Connector" and select "Model Context Protocol (MCP)" from the available connector types
Note: Use the YAML schema template provided by Copilot Studio
- Configure {server_name} Connection
Fill in the YAML schema with {server_name} server details including command, arguments, and environment variables
agentbay
Note: Copilot Studio dynamically reflects changes as tools and resources are updated on the MCP server
- Add Tools to Agent
Once connected, add the MCP server tools and resources to your specific agent through the Copilot Studio UI
Note: Currently supports Tools and Resources (Prompts not yet supported)
- Test Agent Capabilities
Test your agent to verify it can access and use the {server_name} tools correctly
Configuration Details
Connect MCP server to Microsoft Copilot Studio:
Step 1: Create YAML Connector Schema
In Copilot Studio, navigate to the connectors section and create a new MCP connector using the YAML schema template:
# MCP Connector Configuration for AgentBay
name: AgentBay-mcp-connector
description: An MCP server for providing serverless cloud infrastructure for AI agents.
mcp_server:
command: agentbay
args:
env:
Step 2: Add to Agent
Once connected, add the MCP server's tools and resources to your Copilot Studio agent through the UI.
Examples
Once configured, you can use AgentBay in Microsoft Copilot Studio:
Open Browser Session
Launch browser and navigate to specific website
Ask Microsoft Copilot Studio: "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 Microsoft Copilot Studio: "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 Microsoft Copilot Studio: "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 Microsoft Copilot Studio: "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
- Launch Microsoft Copilot Studio
- Verify AgentBay is available in the tools list
- 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
Generative Orchestration Not Available
Symptoms: MCP option not visible, Cannot add MCP connectors
Cause: Generative Orchestration is not enabled for your environment
Solution:
- Contact your Microsoft 365 administrator
- Enable Generative Orchestration in tenant settings
- Verify your subscription includes Copilot Studio with MCP support
- Check Microsoft Learn documentation for enablement steps
MCP Connector Connection Failed
Symptoms: Connector shows "Disconnected" status, Tools not available to agent
Cause: MCP server not accessible or configuration error
Solution:
- Verify the MCP server command is correct and accessible
- Check all required environment variables are set
- Test the MCP server independently outside Copilot Studio
- Review YAML schema for syntax errors
- Check network connectivity and firewall rules
Tools Not Appearing in Agent
Symptoms: Connector connected but tools missing, Agent cannot invoke MCP tools
Cause: Tools not added to agent or synchronization issue
Solution:
- Manually add tools to agent through Copilot Studio UI
- Refresh connector to sync latest tools from MCP server
- Verify tools are published on the MCP server
- Check agent configuration includes the MCP connector
MCP Server Tools Update Not Reflected
Symptoms: New tools not appearing, Old tools still visible after removal
Cause: Copilot Studio cache or sync delay
Solution:
- Disconnect and reconnect the MCP connector
- Wait a few minutes for dynamic sync to occur
- Manually refresh the connector in Copilot Studio
- Restart the MCP server if possible
AgentBay not appearing in Microsoft Copilot Studio
Symptoms: Server not listed, Tools not available
Cause: Configuration or installation issue
Solution:
- Verify configuration syntax
- Check AgentBay installation
- Restart Microsoft Copilot Studio
- Check logs for error messages
Next Steps
Now that AgentBay is integrated with Microsoft Copilot Studio:
- Explore all AgentBay capabilities through Microsoft Copilot Studio
- Check out other MCP servers that work with Microsoft Copilot Studio
- Join the MCP community for tips and support
- Consider contributing to AgentBay development
Need Help?
- Search for AgentBay documentation
- Check the Microsoft Copilot Studio MCP guide
- Join the MCP community discussions