Cloud BOT MCP Server for VS Code CopilotGive VS Code Copilot instant access to 7 tools to Cancel Job, Execute Bot, Get Bot Details, and more
GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.
Ask AI about this App Connector for VS Code Copilot
The Cloud BOT app connector for VS Code Copilot is a standout in the Productivity category — giving your AI agent 7 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Cloud BOT and 3,400+ MCP Servers from a single visual interface.




{
"mcpServers": {
"cloud-bot": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Cloud BOT MCP Server
Connect your Cloud BOT account to any AI agent and take full control of your cloud-based Robotic Process Automation (RPA) and browser-based workflows through natural conversation.
GitHub Copilot Agent mode brings Cloud BOT data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 7 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.
What you can do
- Robot Orchestration — List and manage all browser automation robots in your account programmatically, retrieving detailed configuration and input parameter metadata
- Automated Job Execution — Programmatically trigger bot executions with custom JSON parameters to coordinate high-fidelity web scraping and data entry tasks
- Workflow Monitoring — Track the real-time status of your automation jobs and retrieve detailed logs and results to maintain perfectly coordinated RPA operations
- File Architecture — Access and manage files within the Cloud BOT storage used or generated by your robots to maintain high-fidelity data cycles
- Lifecycle Management — Programmatically cancel or suspend running jobs and verify API connectivity directly through your agent for instant operational reporting
The Cloud BOT MCP Server exposes 7 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
All 7 Cloud BOT tools available for VS Code Copilot
When VS Code Copilot connects to Cloud BOT through Vinkius, your AI agent gets direct access to every tool listed below — spanning rpa, web-scraping, no-code, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.
Cancel a running job
You can pass optional input parameters as a JSON string. Trigger a bot execution
Get details for a specific bot
Check the status of a job
List all available RPA bots
List files in Cloud BOT storage
List recent execution jobs
Connect Cloud BOT to VS Code Copilot via MCP
Follow these steps to wire Cloud BOT into VS Code Copilot. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.
Create MCP config
.vscode/mcp.json file in your project rootAdd the server config
Enable Agent mode
Start using Cloud BOT
Why Use VS Code Copilot with the Cloud BOT MCP Server
GitHub Copilot for Visual Studio Code provides unique advantages when paired with Cloud BOT through the Model Context Protocol.
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services
Cloud BOT + VS Code Copilot Use Cases
Practical scenarios where VS Code Copilot combined with the Cloud BOT MCP Server delivers measurable value.
Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step
DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review
Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses
Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples
Example Prompts for Cloud BOT in VS Code Copilot
Ready-to-use prompts you can give your VS Code Copilot agent to start working with Cloud BOT immediately.
"List all available browser robots in my Cloud BOT account."
"Execute the 'Price Scraper' bot (ID: 'bot_123') with URL 'vinkius.com'."
"Show the status and logs for automation job 'job_456'."
Troubleshooting Cloud BOT MCP Server with VS Code Copilot
Common issues when connecting Cloud BOT to VS Code Copilot through the Vinkius, and how to resolve them.
MCP tools not available
Cloud BOT + VS Code Copilot FAQ
Common questions about integrating Cloud BOT MCP Server with VS Code Copilot.
Which VS Code version supports MCP?
How do I switch to Agent mode?
Can I restrict which MCP tools Copilot can access?
Does MCP work in VS Code Remote or Codespaces?
.vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.