Can I see exactly how my Lindy made a specific decision?

Yes. Use the `get_run_logs` tool with a specific Run ID. Your agent will retrieve the literal LLM reasoning loops and step-by-step validations, giving you full transparency into the autonomous agent's logic.

How do I trigger an autonomous task through a conversation?

The `trigger_lindy` tool allows you to start an asynchronous task run. You just need to provide the Lindy ID and a JSON payload defining the inputs for the task. Your agent will fire the job and return a Run ID for status tracking.

Can my agent list which third-party apps my Lindies are connected to?

Absolutely. Use the `list_integrations` tool to retrieve all active third-party app connections. Your agent will report which channels (like Slack, Gmail, or HubSpot) are securely connected to your workspace.

Lindy (Autonomous AI Employees) MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Lindy (Autonomous AI Employees)
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 Lindy (Autonomous AI Employees) and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "lindy-autonomous-ai-employees": {
      "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 Lindy (Autonomous AI Employees) MCP Server

Connect your Lindy.ai account to any AI agent and take full control of your autonomous AI workforce and automated business processes through natural conversation.

GitHub Copilot Agent mode brings Lindy (Autonomous AI Employees) 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

Lindy Orchestration — List all custom autonomous assistants (Lindies) built in your workspace and retrieve their core configurations and prompt instructions directly from your agent
Task Execution — Trigger specific Lindies to start asynchronous task runs using dynamic JSON payloads to automate complex business workflows
Reasoning Audit — Dump literal LLM reasoning logs for specific run loops to understand how your autonomous agents are making decisions and identifying steps
Run Monitoring — Track the state of active executions and manage lifecycle controls, including the ability to cancel runs stuck in context loops securely
Integration Visibility — Enumerate secure connections to third-party apps like Slack, Gmail, and CRM systems to manage your AI's reach across your software stack
Workspace Management — Navigate organizational boundaries and team structures to understand how Lindies are distributed across your company

The Lindy (Autonomous AI Employees) 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 Lindy (Autonomous AI Employees) to VS Code Copilot via MCP

Follow these steps to integrate the Lindy (Autonomous AI Employees) 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 Lindy (Autonomous AI Employees)

Ask Copilot: "Using Lindy (Autonomous AI Employees), help me..." — 10 tools available

Why Use VS Code Copilot with the Lindy (Autonomous AI Employees) MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Lindy (Autonomous AI Employees) 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

Lindy (Autonomous AI Employees) + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Lindy (Autonomous AI Employees) 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

Lindy (Autonomous AI Employees) MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Lindy (Autonomous AI Employees) to VS Code Copilot via MCP:

cancel_run

Cancel a running execution dispatching hard stops interrupting trapped context loops

get_lindy

Get configuration mappings including standard tools and prompts for a specific Lindy

get_run

Get specific state for a Run blocking on Human input or External APIs

get_run_logs

Dump literal LLM reasoning logs isolating a specific run loop

list_integrations

List bounded third-party app connections securely connected (e.g Slack, Gmail)

list_lindies

List all custom autonomous AI Assistants (Lindies) built on the workspace

list_runs

List recent runs validating the full execution graph isolating active Lindy instances

list_triggers

List how autonomous AI agents are woken up (Cron, Webhook, API)

list_workspaces

List all explicit organizational boundaries structuring isolated Teams

trigger_lindy

Trigger a Lindy to start an asynchronous task run parsing a JSON payload

Example Prompts for Lindy (Autonomous AI Employees) in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Lindy (Autonomous AI Employees) immediately.

"List all active Lindies in my workspace"

"Show me the reasoning logs for the last run of 'Sales-Research-Lindy'"

"What triggers are currently configured for our autonomous agents?"

Troubleshooting Lindy (Autonomous AI Employees) MCP Server with VS Code Copilot

Common issues when connecting Lindy (Autonomous AI Employees) 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.

Lindy (Autonomous AI Employees) + VS Code Copilot FAQ

Common questions about integrating Lindy (Autonomous AI Employees) 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.