Can My Agent Uselookup · compare · cite

Aug 28, 2026 · Catalog foundation is up

Specification feature · interfaces

MCP client roleMCP 2026-07-28

Consume capabilities exposed by MCP servers.

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

MCP client role: 8 supported, 0 partial, 0 unsupported, 23 unreviewed across 31 cataloged products.

Markdown · JSON

Explore this familyMore in Model Context Protocol23 capabilities

Current evidence by product

Can my agent use MCP client role?

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

Known issues (0)Report an issue
  • Supported8
  • Partial0
  • Unsupported0
  • Unknown23
  • Not applicable0

Web

9 products
GrokGrok
Y2Supported
Observed 2026-08-28Current · 2 conditions
?Unknown
No source reviewedPreview record
Report this result

Desktop

13 products
ClineCline
Y6Supported
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

Consume capabilities exposed by MCP servers.

The Grok Bot claim is scoped to its hosted desktop product and inherited Cursor MCP policy. It does not prove support for MCP resources, prompts, sampling, elicitation, or every authentication flow; those remain separate rows.

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
  • policyconfigured server scope, enterprise managed configuration, tool permissions, and server health determine which MCP capabilities are available in a session
Evidence
Cursordesktop · current
Supported
Target
current Cursor MCP documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • policyconfigured server enablement, tool approval, enterprise allowlists, and server health determine which capabilities are available
Evidence
Gemini CLIcli · current
Supported
Target
Gemini CLI MCP documentation updated 2026-06-18 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • policyconfigured server enablement, workspace trust, tool confirmation, and server health determine which capabilities are available
Evidence
Grokweb · current
Supported
Target
2026-08-28 Grok Web connector documentation observation · hosted-observation
Environment
hosted-default
Observed
2026-08-28
  • transportcustom servers must be reachable over the public internet; local-only servers require a separate tunnel
  • authserver authentication and provider permissions can be required
Evidence
Grok Botdesktop · current
Supported
Target
2026-08-28 Grok Bot desktop documentation and compatible-client listing · hosted-observation
Environment
hosted-default
Observed
2026-08-28
  • policyteam MCP allowlists, denylists, member-install policy, and network allowlists can disable a server
  • authhosted MCP authentication is shared across Cursor and Grok Bot for the account
Evidence
Clinedesktop · current
Supported
Target
current Cline MCP documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • policyconfigured server enablement, tool approval, enterprise controls, and server health determine which capabilities are available
Evidence
Continuedesktop · current
Supported
Target
current Continue MCP documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • policyMCP servers are available in Agent mode and depend on the active Continue configuration and server health
Evidence
Zed Agentdesktop · current
Supported
Target
current Zed MCP documentation observed 2026-08-28 · dated-documentation
Environment
local-default
Observed
2026-08-28
  • host-roleclaim is scoped to Zed Agent using Zed-configured MCP servers directly, not external agents forwarded through ACP
Evidence
  1. 1. Evidence checked 2026-08-28: xAI documents Grok Bot connecting to tools through MCP servers and following Cursor team MCP policy; the Agent Plugins compatible-client registry independently lists Grok Bot's supported MCP transports.
  2. 2. Evidence checked 2026-08-28: xAI documents custom MCP connectors in Grok Web, including server URL and authentication setup, tool discovery, and making the server's tools available in conversations.
  3. 3. Evidence checked 2026-08-28: Anthropic documents Claude Code connecting to local and remote MCP servers, discovering their tools, prompts, and resources, and managing those servers through `claude mcp`.
  4. 4. Evidence checked 2026-08-28: Google documents Gemini CLI connecting to configured MCP servers as a client, discovering tools, prompts, and resources, and executing server-provided tools.
  5. 5. Evidence checked 2026-08-28: Cursor documents its editor and CLI connecting to MCP servers and consuming protocol capabilities exposed by those servers.
  6. 6. Evidence checked 2026-08-28: Cline documents its desktop extension connecting to configured local or remote MCP servers and using their exposed capabilities.
  7. 7. Evidence checked 2026-08-28: Continue documents MCP servers as an Agent-mode integration for connecting the editor extension to external tools, systems, databases, and context.
  8. 8. Evidence checked 2026-08-28: Zed documents that Zed Agent uses Zed-configured MCP servers directly and currently consumes their Tools and Prompts capabilities.