Atomic capability · interfaces

MCP toolsMCP

Invoke operations exposed by a Model Context Protocol server.

MCP tools: 7 supported, 3 partial, 0 unsupported, 21 unreviewed across 31 cataloged products.

Markdown · JSON

Current evidence by product

Can my agent use MCP tools?

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

  • Supported7
  • Partial3
  • Unsupported0
  • Unknown21
  • Not applicable0

Web

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

Desktop

13 products
ClaudeClaude
P3Partial
Docs checked 2026-08-28Current · 2 conditions
?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

MCP tools are operations advertised by a Model Context Protocol server and made available for a model or agent to invoke.

This row asks whether the named harness can connect to an MCP server and call its tools. It does not claim support for every MCP transport, authentication flow, protocol primitive, or third-party server. Plan, rollout, and transport restrictions are marked partial when the public documentation states them.

Only the current track is sourced in this first wave. Preview and unreviewed harness cells remain unknown.

Traceable compatibility

Assertion ledger

Documentation evidence only. No runtime conformance test is implied.

ChatGPTweb · current
Partial
Target
2026-08-28 hosted documentation observation · hosted-observation
Environment
hosted-default
Observed
2026-08-28
  • previewdeveloper mode and full MCP are beta
  • planavailability varies by ChatGPT plan
  • policyworkspace role and administrator controls apply
Evidence
Claudeweb · current
Partial
Target
2026-08-28 hosted documentation observation · hosted-observation
Environment
hosted-default
Observed
2026-08-28
  • previewcustom connectors are beta
  • planpaid plan required
Evidence
Claudedesktop · current
Partial
Target
current Claude Desktop documentation · dated-documentation
Environment
local-default
Observed
2026-08-28
  • policyextension installation and administrator controls apply
  • transportlocal extensions and remote connectors use different setup paths
Evidence
Claude CLIcli · current
Supported
Target
current Claude Code CLI documentation · dated-documentation
Environment
local-default
Observed
2026-08-28

No additional condition is recorded for this statement.

Evidence
Cursordesktop · current
Supported
Target
current Cursor documentation · dated-documentation
Environment
local-default
Observed
2026-08-28

No additional condition is recorded for this statement.

Evidence
Codex CLIcli · current
Supported
Target
current Codex CLI documentation · dated-documentation
Environment
local-default
Observed
2026-08-28

No additional condition is recorded for this statement.

Evidence
Gemini CLIcli · current
Supported
Target
current Gemini CLI documentation · dated-documentation
Environment
local-default
Observed
2026-08-28

No additional condition is recorded for this statement.

Evidence
Copilot Chatdesktop · current
Supported
Target
current VS Code documentation · dated-documentation
Environment
local-default
Observed
2026-08-28

No additional condition is recorded for this statement.

Evidence
OpenWork Desktopdesktop · current
Supported
Target
current OpenWork MCP documentation · dated-documentation
Environment
local-default
Observed
2026-08-28
  • authdocumented OAuth setup currently expects dynamic client registration
Evidence
Grok Botdesktop · current
Supported
Target
2026-08-28 Grok Bot desktop documentation observation · hosted-observation
Environment
hosted-default
Observed
2026-08-28
  • policyteam MCP allowlists, denylists, member-install policy, and network allowlists can disable a server
  • authsign-in tokens for hosted MCP servers remain with the backend that runs tool calls on the computer's behalf
Evidence
  1. 1. Evidence checked 2026-08-28: ChatGPT developer mode can scan and invoke tools from custom remote MCP apps on ChatGPT web, but full MCP is a beta rollout limited by plan and workspace controls.
  2. 2. Evidence checked 2026-08-28: Claude web supports tools from custom remote MCP connectors on paid plans, and Anthropic labels the feature beta.
  3. 3. Evidence checked 2026-08-28: Claude Desktop supports local MCP servers through desktop extensions and remote MCP connectors, with beta and administrator controls documented.
  4. 4. Evidence checked 2026-08-28: the Claude Code CLI reference exposes `claude mcp` for configuring MCP servers and documents MCP tools in its permission surface.
  5. 5. Evidence checked 2026-08-28: Cursor documents local and remote MCP transports and automatic use of discovered MCP tools by Agent.
  6. 6. Evidence checked 2026-08-28: OpenAI documents MCP as a Codex CLI tool for connecting the local agent to external systems.
  7. 7. Evidence checked 2026-08-28: Gemini CLI documents configured MCP server discovery and invocation of the tools those servers expose.
  8. 8. Evidence checked 2026-08-28: VS Code documents MCP tools as a supported agent tool type and supports local or remote MCP servers in Copilot agent mode.
  9. 9. Evidence checked 2026-08-28: OpenWork Desktop documents workspace or global custom MCP servers, including an OAuth setup path, for use in agent sessions.
  10. 10. Evidence checked 2026-08-28: xAI documents that Grok Bot connects to tools through plugins and MCP servers, while hosted MCP tool calls are run on the Bot computer's behalf; team MCP policy can disable servers or member-added configurations.