In your editor: a census of 145 listings

No IDE plug-in for the agent itself; what works in an editor is Ada's MCP server, which Cursor and VS Code can connect to in order to manage and analyse your agent.

Source retrieved 2026-10-08

Editor use is documented as three patterns you build yourself, through a CLI task, a webview hosting the React chat, or a language server; the vendor states no first-party extension exists yet.

Source retrieved 2026-10-08

There is no Agno IDE extension; instead the CLI registers your running AgentOS as an MCP server inside Cursor, Claude Code and Codex, which is a connection rather than an editor surface.

Source retrieved 2026-10-07

Cursor, VS Code, Cline and Windsurf are listed as supported harnesses, so the capability set is reachable from inside the editor's own agent.

Source retrieved 2026-10-03

There is no editor plugin; instead a file watcher picks up AI comments you type in whatever IDE you use, so the agent itself still runs as a separate terminal process.

Source retrieved 2026-09-30

Cursor is a supported MCP client, so an IDE can query Amplemarket data, but this is data access through a third-party editor rather than an Amplemarket extension that sells or sequences from the IDE.

Source retrieved 2026-09-10

The CLI itself is a keyboard TUI with no editor surface; the same agent harness runs in Antigravity 2.0 and IDE extensions, and conversations export between them.

Source retrieved 2026-09-10

It reaches editor-side agents such as Cursor, Claude Code and Codex through the same remote MCP server, but there is no native IDE extension of Argorant's own.

Source retrieved 2026-09-26

Extensions for VS Code, JetBrains IDEs and Vim/Neovim, plus ACP clients such as Zed.

Source retrieved 2026-09-02

An MCP server puts agent building inside Claude Code, Cursor, VS Code and Codex; the agent itself still runs on calls.

Source retrieved 2026-09-11

Bolt ships its own in-browser editor in Code view, but there is no extension for VS Code, JetBrains or any external editor.

Source retrieved 2026-09-11

No first-party editor extension: the ADK is code you author in your own editor, and Botpress ships skills and MCP config for Claude Code, Cursor, VS Code and Codex. Studio itself is a browser IDE.

Source retrieved 2026-09-02

No editor extension; the CLI and MCP server are what run inside Cursor, Claude Code and other MCP clients.

Source retrieved 2026-09-02

No native IDE extension; the documented editor surface is the Cartesia MCP server used from Cursor or Claude Code.

Source retrieved 2026-09-02

First-party extensions for VS Code (and Cursor) and JetBrains IDEs, with inline diffs and plan review.

Source retrieved 2026-09-02

It runs as an editor extension in VS Code and forks of it and as a JetBrains plugin, and ACP-capable editors such as Zed, Neovim and Emacs can drive the CLI instead.

Source retrieved 2026-09-12

A VS Code extension reviews uncommitted changes locally and works in Cursor, Windsurf and other VS Code-compatible editors, with chat, docstrings and test generation excluded.

Source retrieved 2026-09-15

A separate Codex IDE extension shares the same login and MCP configuration as the CLI.

Source retrieved 2026-09-02

There is no CrewAI editor extension; instead the vendor publishes a skill pack that teaches Claude Code, Cursor and Codex to scaffold CrewAI projects inside your editor.

Source retrieved 2026-09-13

Cursor Desktop is itself the editor; the same agent also drives JetBrains IDEs and Xcode over the Agent Client Protocol.

Source retrieved 2026-09-02

Runs inside JetBrains IDEs from the AI Chat panel over the Agent Client Protocol, including Remote Development.

Source retrieved 2026-09-02

The product is itself the IDE: a VS Code-derived editor for macOS, Windows and Linux that imports VS Code and Cursor settings. Extensions cannot be installed from any marketplace.

Source retrieved 2026-09-03

No IDE extension; instead a published Dify app can be attached to Cursor or Claude Desktop as an MCP server.

Source retrieved 2026-09-02

There is no native IDE plugin documented; instead Dust exposes the workspace as a remote MCP server that IDEs and assistants can call, plus a browser and Raycast extension.

Source retrieved 2026-10-01

Elicit ships no IDE or editor extension of its own; reaching it from an editor means connecting its hosted MCP server from any MCP-compatible client, which needs Pro or above.

Source retrieved 2026-09-14

Cursor is explicitly supported as an MCP client, so the product reaches the editor as an agent tool, but there is no native IDE extension or plugin of its own.

Source retrieved 2026-10-03

VS Code/Cursor/Windsurf extension shares files and diagnostics; JetBrains and Zed run Droid over ACP.

Source retrieved 2026-09-02

There is no Firecrawl editor plugin, but its official MCP server puts the tools inside IDE-resident agents such as Cursor and Windsurf.

Source retrieved 2026-09-24

There is no native editor extension; an IDE reaches GC AI only by pointing Cursor's MCP configuration at the public-beta MCP endpoint, which an org admin must first enable.

Source retrieved 2026-09-14

First-party extensions for VS Code and JetBrains IDEs, plus Android Studio, Cloud Workstations and Cloud Shell Editor.

Source retrieved 2026-09-02

Agent mode ships in five IDE families on every plan, with completions and chat also in Xcode, Neovim, Eclipse, Zed and SQL Server Management Studio.

Source retrieved 2026-09-02

A remote MCP server puts Glean inside Cursor, VS Code, Windsurf, JetBrains AI Assistant and Claude Desktop.

Source retrieved 2026-09-02

There is no ADK editor extension; instead Agents CLI installs ADK skills into existing AI coding environments, and a docs MCP server can be added to the same tools.

Source retrieved 2026-09-15

A VS Code extension gives goose an in-editor chat with selection and @-file context, and goose also runs as an ACP agent that editors such as Zed launch; the VS Code extension is documented as experimental.

Source retrieved 2026-09-16

The MCP server registers over stdio in Cursor and Claude Desktop, and a Claude Skill extends the agent into Claude Code.

Source retrieved 2026-09-16

There is no Gumloop IDE extension; instead its remote MCP server is documented for Cursor, VS Code and Windsurf, so the editor drives Gumloop agents rather than Gumloop living in the editor.

Source retrieved 2026-09-30

Cursor and Cline are supported harnesses, though Cursor's built-in terminal escapes Guard unless it runs inside an agent session.

Source retrieved 2026-09-29

It runs inside JetBrains IDEs and Android Studio, either from the shared AI Chat tool window or as a standalone plugin with its own tool window.

Source retrieved 2026-09-18

VS Code and every VS Code-based editor, plus all JetBrains IDEs.

Source retrieved 2026-09-02

LangSmith Studio is the vendor's own agent IDE for visualising and debugging graphs, but no plugin for VS Code, JetBrains or Cursor is documented; dcode is a terminal, not an editor.

Source retrieved 2026-09-18

No editor extension is documented. The vendor's own development surface is LangSmith Studio, a browser IDE that attaches to a locally running Agent Server; your own editor is where you write the graph.

Source retrieved 2026-09-02

No purpose-built editor extension; Cursor reaches the product as a supported MCP client, and Cursor specifically needs a Bearer API key because it does not yet support the OAuth flow.

Source retrieved 2026-09-18

The letta-acp adapter runs Letta as a custom agent in Zed, JetBrains IDEs and Obsidian.

Source retrieved 2026-09-02

Reached inside IDE agents through the hosted MCP server and coding-agent skills, not as a first-party IDE extension.

Source retrieved 2026-09-02

There is a VS Code instance inside Manus's own cloud computer that you can take over mid-task, and GitHub sync lets you work in your own editor, but the pages read document no plug-in for your IDE.

Source retrieved 2026-09-19

No IDE extension of its own; Mastra ships an MCP docs server and a skill that coding agents inside editors consume.

There is no MindStudio editor extension; the builder is a browser app. The agent skills plugin instead exposes MindStudio actions to IDE-resident coding agents such as Claude Code, Cursor and Windsurf.

Source retrieved 2026-09-02

No n8n editor extension: the editor is a browser canvas. Cursor, VS Code and Windsurf reach the instance through its MCP server, so workflow building happens from the IDE via an agent.

Source retrieved 2026-09-02

Only through the MCP connector: AI editors such as Cursor, Windsurf and Zed can query your hunt, but there is no NeverApply IDE extension and applying still needs separate approval.

Source retrieved 2026-09-29

There is no editor extension, but the hosted MCP server plugs the agent tools into Cursor, VS Code and Windsurf, so an IDE drives the platform rather than hosting it.

Source retrieved 2026-09-09

An Agent Client Protocol bridge over stdio lets an IDE drive a Gateway session; the docs give Zed setup steps for it.

Source retrieved 2026-09-02

A VS Code family extension installs itself on first run and adds selection sharing plus file-reference shortcuts.

Source retrieved 2026-09-21

Zed, JetBrains and a community VS Code extension connect over ACP, but the vendor itself labels the IDE integration experimental.

Source retrieved 2026-09-21

There is no Perplexity IDE extension; it enters the editor as an MCP tool that Claude Code, Cursor or VS Code calls.

Source retrieved 2026-09-02

There is no Pickaxe editor extension; instead the hosted MCP server exposes the workspace as tools inside Claude Code, Codex, Cursor or VS Code, which needs a workspace API key that Gold bills per request.

Source retrieved 2026-09-09

The ADK edits agent resources as local files in any editor, and Builder MCP plugs the same workflow into Cursor, Claude Code, Claude Desktop and Codex.

Source retrieved 2026-09-02

An agent can appear inside editors such as Zed through the ACP adapter, but that adapter is shipped under the harness experimental path and may be removed in any release without deprecation.

Source retrieved 2026-09-21

There is no in-editor coding assistant; instead the MCP server can be added to Cursor, VS Code, Windsurf or Zed to build and run your Relevance agents from the editor.

Source retrieved 2026-09-22

Agent lives in Replit's own browser-based Project Editor; no plugin for a local editor such as VS Code is documented.

Source retrieved 2026-09-22

There is no editor plugin for building calls, but the hosted MCP server lets IDE-based assistants such as Cursor create, publish and inspect Retell agents from inside the editor.

Source retrieved 2026-09-23

Agentforce Vibes ships as a VS Code extension and is preinstalled in the Salesforce-hosted Agentforce Vibes IDE.

Source retrieved 2026-09-03

No native editor plugin; the IDE surface is the hosted MCP server consumed by Cursor, GitHub Copilot, Cline and Zed, which read SEO data while their own agent edits code.

Source retrieved 2026-10-03

Agent SDK journeys are written in your own editor and software lifecycle, but Sierra ships no editor extension and the agent itself runs in customer channels.

Source retrieved 2026-09-03

No IDE extension; instead deployed workflows are callable from Cursor, VS Code, Claude Code and Codex as MCP tools.

Source retrieved 2026-09-03

Cursor is a first-class surface with a documented .cursor/mcp.json snippet, and Claude Desktop connects the same way; the review lands in the editor conversation.

Source retrieved 2026-10-03

No editor extension; the only IDE-adjacent surface is its MCP server, which MCP-compatible clients including Cursor connect to directly.

Source retrieved 2026-09-03

There is no StackAI editor plugin; the account is reachable from Cursor or Claude via the hosted MCP endpoint, which is an assistant integration rather than an IDE surface.

Source retrieved 2026-09-09

No Synthflow editor extension; Claude, Claude Code and Cowork can drive the workspace over MCP from where a developer already works.

There is no Tale IDE extension; instead opencode and Claude Code are pointed at Tale as a model provider and MCP tool server from your own editor.

Source retrieved 2026-10-03

The agent itself never runs in an editor, but Telnyx ships an MCP server that lets IDE assistants such as Cursor or Windsurf create and manage Telnyx AI assistants from the editor.

Source retrieved 2026-09-09

Hosted MCP server installs into Cursor, Windsurf, Claude Code, Codex and OpenCode.

Source retrieved 2026-09-03

The canvas lives in an IDE, but it is UiPath's own browser IDE Studio Web, not your editor: the Studio product page assigns AI agents to Studio Web and names Studio Desktop for RPA and coded workflows, and there is no VS Code or JetBrains extension for the low-code canvas.

Source retrieved 2026-09-03

Documented MCP setup covers Cursor, VS Code and GitHub Copilot in VS Code, so the research tools run inside the editor you already use.

Source retrieved 2026-09-26

Unify reaches Cursor through an official MCP plugin rather than a native editor extension, so the coding surface is assistant-mediated.

Source retrieved 2026-09-27

No agent runtime in the editor; `vapi mcp setup` teaches Cursor, Windsurf and VSCode the Vapi API so you can build from the IDE.

Source retrieved 2026-09-03

Vecbase installs itself into IDE-based hosts such as Cursor and VS Code Copilot as an MCP server, but only from an installer the vendor says is macOS Apple Silicon only.

Source retrieved 2026-09-27

Reachable inside Cursor and Claude Desktop through the MCP server; Warmly ships no editor extension of its own.

Source retrieved 2026-09-03

It reaches editors only as an MCP tool inside a client such as Cursor or Claude Code; the vendor documents no native IDE extension of its own.

Source retrieved 2026-09-27

Zed is itself the editor: the agent lives in a panel beside the buffers, and edits stream into the same window you are working in.

Source retrieved 2026-09-29

Marketplace plugins put the agent inside VS Code, JetBrains IDEs and Android Studio, where diffs are reviewed and accepted without leaving the editor.

Source retrieved 2026-09-09