transport_types
Which MCP transport protocols the provider supports. Common transports: stdio (local process), SSE (Server-Sent Events), HTTP/streamable-HTTP (stateless or streaming).
Type: object Content type: mcp
Provider Support
Section titled “Provider Support”| Provider | Supported | Mechanism |
|---|---|---|
| claude-code | ✓ | mcp_transport_types: stdio (local process), SSE (deprecated, still supported), HTTP/streamable-HTTP (recommended for remote) |
| cline | ✓ | sse_transport_support: Cline supports SSE transport alongside stdio; HTTP transport support follows MCP protocol adoption |
| copilot-cli | ✓ | Copilot CLI supports both local (stdio) and remote (HTTP/SSE) MCP server types, confirmed in concepts/context/mcp.md |
| crush | ✓ | Crush documents stdio, http, and sse transports in its JSON schema for MCP server configuration; default transport is stdio |
| cursor | ✓ | Cursor documents three MCP transports: stdio for local processes managed by Cursor, sse for Server-Sent Events (local or remote, multi-user), and streamable-http for HTTP-based servers (local or remote, multi-user) with OAuth authentication support. |
| factory-droid | ✓ | two transports documented: http (remote cloud endpoints, droid mcp add <name> <url> --type http) and stdio (local processes, droid mcp add <name> '<command>' [--env KEY=VALUE...]) |
| gemini-cli | ✓ | transport_types: Gemini CLI documents supported MCP transport protocols including stdio and HTTP |
| kiro | ✓ | Kiro supports stdio (local process via command + args) and remote (HTTPS endpoint or localhost HTTP via url + optional headers) server types |
| opencode | ✓ | OpenCode supports two transport types: local (type: local, launched via command array with stdio communication) and remote (type: remote, connected via URL supporting HTTP/SSE streamable-HTTP) |
| roo-code | ✓ | transport_types: stdio, sse, and streamable-http are supported and selected via the type field on each server entry |
| windsurf | ✓ | three_transport_types: Windsurf supports stdio, SSE, and HTTP/streamable-HTTP transports |
| zed | ✓ | Zed supports both stdio (local command + args + env) and HTTP/HTTPS (remote URL + headers) transports. Stdio servers use the command/args/env shape; remote servers use url + optional headers. Both use the same MCP protocol initialization. |
| amp | ✗ | Amp MCP transport types not documented beyond basic MCP support |
| codex | ✗ | Codex MCP transport types not documented beyond basic MCP support; likely stdio only |
| pi | ✗ | not documented |