Lindy (Autonomous AI Employees) MCP for AI. Manage your autonomous agent fleet via chat.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
Lindy (Autonomous AI Employees) MCP gives you a direct line to your Lindy.ai workspace from your favorite AI client. You can trigger autonomous agents, inspect their internal reasoning logs, monitor active task runs, and manage your entire fleet of Lindies without ever leaving your chat interface.
It turns your agent into a command center for your autonomous workforce.
What your AI can do
Cancel run
Interrupts a running execution and stops tasks stuck in context loops.
Get run
Gets the current state of a run that is blocked by an API or human input.
Get lindy
Retrieves the prompts and tool configurations for a specific Lindy.
Start new asynchronous runs for your Lindies using specific JSON payloads.
Pull literal LLM reasoning logs to see how your agents are making decisions.
Force a hard stop on running tasks that are caught in context loops.
See how your Lindies are distributed across different team boundaries.
Track the real-time state of executions that are waiting on APIs or humans.
See every third-party connection like Slack or Gmail linked to your AI.
Ask an AI about this
Waiting for input…
Lindy (Autonomous AI Employees) MCP - 10 Tools
Manage your autonomous agent fleet, audit reasoning logs, and trigger tasks using 10 specialized tools.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Lindy (Autonomous AI Employees) on VinkiusCancel Run
Interrupts a running execution and stops tasks stuck in context loops.
Get Run
Gets the current state of a run that is blocked by an API or human input.
Get Lindy
Retrieves the prompts and tool configurations for a specific Lindy.
List Integrations
Lists all third-party app connections like Slack and Gmail.
List Runs
Lists recent runs and validates the execution graph for active instances.
List Lindies
Lists all custom autonomous assistants built in your workspace.
Get Run Logs
Dumps the literal LLM reasoning logs for a specific run loop.
Trigger Lindy
Starts an asynchronous task run by parsing a JSON payload.
List Triggers
Shows how your agents are woken up by webhooks, cron jobs, or APIs.
List Workspaces
Lists the organizational boundaries and team structures in your account.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Lindy (Autonomous AI Employees), then connect any of our 5,100+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,100+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Lindy. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This connection provides 10 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
The dashboard fatigue of managing dozens of AI agents.
Most teams today are drowning in 'AI sprawl.' You have one agent for sales, one for support, and another for research. To check on them, you have to log into a dashboard, find the right workspace, locate a specific run, and then try to interpret why it's stuck or what it's actually doing with your Slack data.
This MCP puts the control plane back into your hands. Instead of tab-hopping, you just ask your agent. You can see the status of every run, pull the reasoning logs to see the internal logic, and kill stuck tasks with a single command. You get a bird's-eye view of your entire autonomous workforce in one conversation.
Lindy (Autonomous AI Employees) MCP puts your agents on autopilot.
You can stop manually checking statuses, hunting for run IDs, and digging through web interfaces. This tool handles the heavy lifting of fetching workspace boundaries, listing integrations, and pulling deep reasoning logs.
You stop managing a dashboard and start managing a workforce. It's that simple.
What your AI can actually do with this
Managing a fleet of autonomous agents usually means jumping between browser tabs, hunting for specific run IDs, and squinting at logs to figure out why a task stalled. This MCP changes that by bringing your entire Lindy.ai workspace into your primary AI client. Instead of hunting for data, you just ask your agent what's happening.
You can check the status of a specific run, see exactly what your agents are doing with your Slack or Gmail connections, and even pull the raw reasoning logs to see the internal logic of a loop. If an agent gets stuck in a context circle, you can kill the execution immediately via chat.
It moves the control plane from a complex dashboard into a natural conversation. Because Vinkius lets you connect to the entire catalog of 4,000+ MCPs from one client, you can manage your Lindy workforce alongside your other business tools without switching apps. You get a high-level overview of your organizational boundaries and a granular way to trigger complex workflows using simple JSON payloads.
It's about having one place to see, audit, and command every autonomous employee you've built.
019d75c7-5441-702a-974b-896b9f156f5f Here's how it actually works
The bottom line is you get a chat-based command center for your autonomous agents.
Subscribe to the MCP and enter your Lindy API Token.
Connect your preferred AI client to the Vinkius catalog.
Ask your agent to list your Lindies or trigger a specific task run.
Who is this actually for?
This is for the operations lead who is tired of checking fifty different status lights, the developer debugging a runaway agent loop, and the founder who needs to know exactly what their AI is doing with company data.
Checks the status of daily automated workflows and kills stuck tasks without leaving the chat.
Debugs agent logic by pulling reasoning logs directly into the IDE or chat interface.
Audits the reach of AI integrations across Slack, Gmail, and CRMs to ensure security.
What Changes When You Connect
Stop manual dashboard hopping by using list_runs to see every active agent status in one chat window.
Debug agent behavior instantly with get_run_logs to see the exact reasoning steps the AI took.
Kill runaway tasks immediately with cancel_run to prevent stuck loops from wasting your API credits.
Audit your security posture by using list_integrations to see every Slack and Gmail connection.
Launch complex workflows faster by using trigger_lindy to send JSON payloads directly from your chat.
Map out your entire AI infrastructure using list_workspaces to see how agents are distributed across teams.
See it in action
Debugging a stuck support agent
A support agent gets stuck in a loop. The developer uses get_run_logs to see the reasoning, identifies the error, and uses cancel_run to stop the loop.
Auditing company integrations
A founder wants to know which apps the AI can access. They ask the agent to list_integrations to see all active Slack and Gmail connections.
Launching a research task
An ops manager needs a specific research task done. They use trigger_lindy to pass a JSON payload to the Sales-Research-Lindy.
Checking team boundaries
A manager wants to see which assistants are assigned to which departments. They use list_workspaces to see the organizational structure.
The honest tradeoffs
Manually hunting for logs in a web UI
Logging into the Lindy dashboard and clicking through five pages to find a specific run ID.
Use get_run_logs to pull the reasoning logs directly into your chat or IDE.
Letting a stuck agent run forever
Watching an agent loop indefinitely until it hits a rate limit or consumes your budget.
Use cancel_run to send a hard stop to any execution that is caught in a context loop.
Guessing your Lindy configurations
Trying to remember what prompts or tools a specific assistant is using.
Use get_lindy to see the exact configuration mappings and prompts for any assistant.
When It Fits, When It Doesn't
Use this MCP if you already use Lindy.ai and want to manage your agents from a chat interface like Claude or Cursor. It's built for people who need to see the 'why' behind an agent's action (via get_run_logs) or who need to manage a high volume of tasks without clicking through a dashboard. Don't use this if you aren't already using Lindy.ai, as it won't give you agent capabilities out of the box. If you just need a simple chatbot and don't need autonomous task execution or reasoning logs, this is likely overkill.
Questions you might have
How do I stop a Lindy run that is stuck? +
You can use the cancel_run tool to send a hard stop to any execution that is caught in a context loop.
Can I see the internal reasoning of my Lindy agents? +
Yes, the get_run_logs tool allows you to dump the literal LLM reasoning logs for a specific run loop.
Does the Lindy MCP work with my Slack integrations? +
You can use list_integrations to see all bounded third-party app connections, including Slack and Gmail.
How do I start a new task for a Lindy? +
Use the trigger_lindy tool to start an asynchronous task run by passing in a JSON payload.
Can I see all my Lindies at once? +
The list_lindies tool will enumerate every custom autonomous assistant built in your workspace.
How do I authenticate the Lindy MCP with my account? +
You'll need a Lindy API Token. Grab that from your Lindy dashboard and paste it into your MCP client's configuration to connect your workspace.
Can I see what triggers my Lindy agents? +
Yes, you can use the list_triggers tool. It shows how your agents get woken up, including Cron jobs, Webhooks, and manual API triggers.
How do I see how Lindies are organized across my company? +
You can use list_workspaces to see your organizational boundaries. This helps you understand how your autonomous assistants are distributed across different teams.
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.
We've already built the connector for Lindy (Autonomous AI Employees). Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.