Subscribe

MCP Clients

Which MCP clients support which features?

Tools, resources, prompts, elicitation, OAuth, transports and protocol versions across the clients people actually use.

Clients
17
Features
10
Verified cells
93/170
Sources
13
YesPartialNoUnknownHover a cell for notes. Click it to open the source.

Features

What each column means and who supports it

MCP updates

All →
  1. MCP clients: 17 tracked across 10 capabilities

    93 of 170 cells are verified against vendor docs and 77 are still marked unknown. The most widely confirmed capability is Remote (HTTP/SSE) (16 of 17).

  2. Claude.ai connectors move to the 2026-07-28 protocol

    Connectors moved to a new embedded client that negotiates 2026-07-28 and advertises MCP Apps, but no longer advertises elicitation.

    Source

  3. Claude Code defaults to MCP 2026-07-28 everywhere

    Confirmed on 2026-07-28 by default for HTTP, stdio (v2.1.292+) and claude.ai connectors (v2.1.295+). Opt out with MCP_PROTOCOL_NEGOTIATION=legacy.

    Source

  4. Goose 1.50 speaks the latest MCP protocol natively

    Goose CLI 1.50.0 negotiates 2026-07-28 natively; form elicitation works over remote HTTP.

    Source

  5. ChatGPT Desktop gets working form and URL elicitation

    Desktop 26.901: form and URL elicitation both verified working over remote HTTP.

    Source

Also in the hub

Weekly, free

What changed in AI integrations

One short email when MCP clients, plugin ecosystems, IDE integrations, AI plan prices or security advisories change. Every item is sourced.

You'll finish signing up on beehiiv.