Can I automatically trigger an RPA task via the AI agent?

Yes! Use the `trigger_task` tool with the target Robot ID and any required input parameters. Your agent will start the automation job and return the unique Job ID.

How do I check if a robot is currently online and ready?

Use the `list_robots` tool. It will retrieve all configured robots in your ShadowBot account along with their current status (e.g., Online, Busy, Offline).

Can I retrieve the logs for a completed automation job?

Yes! The `get_task_logs` tool allows you to fetch the execution details and any output data for a specific Job ID.

ShadowBot MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: ShadowBot
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

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.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install ShadowBot and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "shadowbot": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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 ShadowBot MCP Server

Connect your AI agents to ShadowBot (影刀RPA), the leading Robotic Process Automation (RPA) platform for high-performance browser and desktop automation. This MCP provides 10 tools to manage automation robots, orchestrate execution tasks, and monitor the health of your digital workforce programmatically.

GitHub Copilot Agent mode brings ShadowBot data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 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 inspect available automation robots and their current operational status
Task Execution — Trigger specific automation tasks and handle job lifecycle management from start to finish
Performance Monitoring — Retrieve granular execution logs and track robot throughput and success rates
Credential Handling — Monitor and manage robotic account assignments and access tokens for secure automation
Global Management — Access organizational project structures and list active automation workflows directly from your agent

The ShadowBot MCP Server exposes 10 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.

How to Connect ShadowBot to VS Code Copilot via MCP

Follow these steps to integrate the ShadowBot MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using ShadowBot

Ask Copilot: "Using ShadowBot, help me..." — 10 tools available

Why Use VS Code Copilot with the ShadowBot MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with ShadowBot 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

ShadowBot + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the ShadowBot 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

ShadowBot MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect ShadowBot to VS Code Copilot via MCP:

get_robot_details

Get detailed information for a specific robot

get_task_details

Retrieve the status and results of a ShadowBot task

list_apps

List all RPA applications in your ShadowBot account

list_department_members

List members in a specific department

list_departments

Retrieve the organizational department list

list_online_robots

List currently online robots

list_robots

List all robots associated with the account

list_task_logs

Retrieve logs for a specific task

start_task

Remote trigger a ShadowBot RPA application

stop_task

Stop a running ShadowBot task

Example Prompts for ShadowBot in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with ShadowBot immediately.

"List all automation robots in my ShadowBot account and show their status."

"Start task 'process_invoices' on robot ID 'bot_rpa_777'."

"Get the execution logs for Job ID 'job_12345'."

Troubleshooting ShadowBot MCP Server with VS Code Copilot

Common issues when connecting ShadowBot to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

ShadowBot + VS Code Copilot FAQ

Common questions about integrating ShadowBot MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .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.