Can My Agent Uselookup · compare · cite

Aug 28, 2026 · Catalog foundation is up

Specification feature · interfaces

MCP stdio transportMCP 2026-07-28

Connect to a local MCP server over standard input and output.

Terminology basis: MCP 2026-07-28. MCP 2026-07-28

MCP stdio transport: 7 supported, 0 partial, 0 unsupported, 24 unreviewed across 31 cataloged products.

Markdown · JSON

Explore this familyMore in Model Context Protocol23 capabilities

Current evidence by product

Can my agent use MCP stdio transport?

Read across for the answer. 7 of 31 current product columns have reviewed evidence; unreviewed does not mean unsupported.

Known issues (0)Report an issue
  • Supported7
  • Partial0
  • Unsupported0
  • Unknown24
  • Not applicable0

Web

9 products

Desktop

13 products
ClineCline
Y5Supported
Docs checked 2026-08-28Current · 1 condition
?Unknown
No source reviewedPreview record
Report this result

CLI

9 products

Unknown means no public evidence has been reviewed for that product and capability. It does not mean unsupported.

How statuses are assigned

Definition and scope

What this capability means

Connect to a local MCP server over standard input and output.

The Grok Bot cell is registry-listed. Server lifecycle, installation location, authorization, and security policy remain deployment-specific.

Traceable compatibility

Assertion ledger

Documentation evidence only. No runtime conformance test is implied.

Claude CLIcli · current
Supported
Target
current Claude Code MCP documentation · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportserver command, arguments, environment, and configuration scope are supplied by the operator or administrator
Evidence
Cursordesktop · current
Supported
Target
current Cursor MCP documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportCursor launches the configured local command; executable availability, environment, workspace trust, and enterprise policy can prevent connection
Evidence
Gemini CLIcli · current
Supported
Target
Gemini CLI MCP documentation updated 2026-06-18 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportstdio servers are started only for trusted folders and use the configured command, arguments, environment, and working directory
Evidence
Grok Botdesktop · current
Supported
Target
2026-08-28 Agent Plugins compatible-client listing · hosted-observation
Environment
hosted-default
Observed
2026-08-28
  • runtimetransport support is registry-listed and was not independently tested by Can My Agent Use
Evidence
Clinedesktop · current
Supported
Target
current Cline MCP documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportCline launches the configured command; executable availability, environment, working directory, and enterprise policy can prevent connection
Evidence
Continuedesktop · current
Supported
Target
Continue source commit 5522c6f44ca0 and current documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportContinue launches the configured local command; executable availability, environment, working directory, and server health can prevent connection
Evidence
Zed Agentdesktop · current
Supported
Target
Zed source commit e3adf43f37d7 and current documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • transportZed launches the configured local command; executable availability, environment, and server configuration determine connection success
Evidence
  1. 1. Evidence checked 2026-08-28: the Agent Plugins compatible-client registry explicitly lists MCP stdio for Grok Bot. This is registry evidence, not an independent transport test.
  2. 2. Evidence checked 2026-08-28: Anthropic documents adding local Claude Code MCP servers with the stdio transport and a command plus arguments.
  3. 3. Evidence checked 2026-08-28: Gemini CLI documents spawning local MCP subprocesses and communicating over stdin/stdout.
  4. 4. Evidence checked 2026-08-28: Cursor documents stdio as a supported local MCP transport managed by Cursor and provides its command, arguments, and environment configuration fields.
  5. 5. Evidence checked 2026-08-28: Cline documents local MCP servers using the stdio transport with command, arguments, environment, and optional working-directory configuration.
  6. 6. Evidence checked 2026-08-28: Continue documents local MCP server configurations using a command and arguments, and its pinned desktop client constructs a Stdio client transport.
  7. 7. Evidence checked 2026-08-28: Zed documents local custom MCP servers configured with a command, arguments, and environment, and its pinned client uses a dedicated stdio transport.