title: "Swimlane Turbine adds two-way MCP support and Hero AI" slug: "swimlane-turbine-adds-two-way-mcp-support-and-hero-ai" published: "2026-10-28" beat: "Launches" tags: ["Launches", "Tools"] creator: "Agentry Newsroom" editor: "Susanne Sperling, Editor — Human in the Loop" tools: ["Claude (Anthropic)", "Perplexity Sonar"] creativeWorkStatus: "verified" dateReviewed: "2026-10-28" aiActArticle50: "compliant" humanView: "https://agentry.news/launches/swimlane-turbine-adds-two-way-mcp-support-and-hero-ai" agentView: "https://agentry.news/agent/swimlane-turbine-adds-two-way-mcp-support-and-hero-ai"
Swimlane released bidirectional Model Context Protocol support for its Turbine security automation platform on October 28, 2026, enabling external AI agents like Claude and ChatGPT to invoke governed
Drafted by an AI agent. Verified by Susanne Sperling, Editor — Human in the Loop. AI policy.
Swimlane announced expanded capabilities for its Turbine security automation platform on October 28, 2026, in a release from Denver, Colorado, adding two-way Model Context Protocol (MCP) support and rolling out the Hero AI Application Builder Agent as generally available features Swimlane.
The update enables Turbine to function both as an MCP host and an MCP server, creating a two-way bridge between the platform and external AI agents. When operating as a host, Turbine's Hero AI can now connect to third-party MCP servers and use their tools during security investigations and playbook execution, all governed by centralized authentication and access controls Swimlane documentation.
As an MCP server, Turbine can expose selected, governed Turbine components—including multi-step playbooks—to external AI clients. The announcement identifies Claude, ChatGPT, Cursor, Gemini CLI, and Microsoft Copilot as examples of external agents that can now invoke those components Swimlane documentation. External clients invoking Turbine playbooks remain subject to the platform's existing role-based access controls, ensuring security teams maintain oversight of what external agents can execute within their infrastructure.
The release introduces the Hero AI Application Builder Agent, which accepts natural-language prompts to generate applications tailored to security and other use cases Swimlane documentation. This capability reduces the manual work required to construct detection logic and incident response workflows, allowing security teams to describe desired behavior in plain English rather than writing configuration code.
The announcement arrives as security operations centers face growing pressure to automate detection and response at scale. Two-way MCP support allows Turbine deployments to operate as part of a larger AI agent ecosystem, enabling hero AI to pull data and services from other platforms while allowing those platforms' agents to trigger Turbine-managed playbooks. The move positions Turbine as infrastructure for agent-to-agent orchestration within enterprise security stacks, rather than as an isolated automation tool.
Administrators can publish selected tenant components through Turbine MCP servers and register external MCP servers for Hero AI to use Swimlane documentation, configuring which agents have access to which Turbine resources and capabilities.