Hosted remote toolsChatGPT web
ChatGPT web uses hosted MCP-backed tools supplied through plugins. It does not read local Codex configuration, so a server added to config.toml is not automatically available in a web conversation.
Client compatibility
ChatGPT MCP compatibility across web and desktop
The useful first question is not simply whether ChatGPT supports MCP. It is whether the connection will run in ChatGPT web or on a desktop Codex host. Those surfaces discover, configure, and govern tools differently.
Two connection paths
Choose the ChatGPT surface before the server
OpenAI documents a hosted plugin path for ChatGPT web and a local Codex-host path for desktop. A setup that works in one place is not evidence that it appears in the other.
Local Codex hostChatGPT desktop
ChatGPT desktop shares MCP configuration with Codex CLI and the IDE extension on the same host. It can use local stdio servers and remote Streamable HTTP servers through that configuration.
Current source check
Five provider comparisons across both surfaces
Documented labels require provider-owned evidence for the exact pairing. Requirements match is a transport and authentication inference; every condition remains part of the result.
| Surface | GitHub MCP Server | Linear MCP Server | Figma MCP Server | Notion MCP | Atlassian Rovo MCP Server |
|---|---|---|---|---|---|
| ChatGPT web | Conditional | Conditional | Unknown | Conditional | Conditional |
| ChatGPT desktop | Conditional | Requirements match | Unknown | Conditional | Conditional |
Availability gates
Technical compatibility is only one gate
For ChatGPT web, product availability and workspace policy can stop a connection before transport or OAuth is tested. For desktop, the local host still controls credentials, trust, and tool exposure.
Plan and workspace
Plugin availability can depend on the ChatGPT plan, workspace type, administrator settings, role, region, and the capabilities an app exposes.
OAuth continuity
Remote providers can require interactive authorization and durable refresh-token behavior. A successful login is not a permanent availability guarantee.
Write confirmation
A server exposing write tools does not bypass user confirmation or workspace policy. Tool visibility and action authorization remain separate decisions.
Evidence limits
What this compatibility answer never means
ResolveMesh compares public requirements as of the observation date. It does not connect your account or execute a provider tool.
Desktop configuration is web configuration
A local MCP entry belongs to the Codex host. ChatGPT web uses its separately managed plugin catalog.
Standards overlap is provider support
Matching HTTP and OAuth requirements is useful evidence, but only provider-owned documentation earns a documented label.
Tool exposure grants permission
The client, workspace, user, and provider still decide whether a specific read or write action can run.
Primary OpenAI sources
References
These product distinctions and availability conditions come from current OpenAI documentation. Verify them again before a production rollout because client behavior can change.
OpenAI: Model Context Protocol in Codex
Primary OpenAI reference distinguishing ChatGPT web plugin tools from desktop, CLI, and IDE configuration on the local Codex host.
Read the primary sourceOpenAI: Developer mode and MCP apps in ChatGPT
Primary OpenAI reference for custom MCP app setup, OAuth requirements, write confirmations, and workspace administration.
Read the primary sourceOpenAI: Apps in ChatGPT
Primary OpenAI reference for plugin availability across plans, workspaces, roles, regions, and app capabilities.
Read the primary source