ChatGPT MCP Apps (Model Context Protocol)
Model Context Protocol (MCP) is an open standard for connecting AI assistants like ChatGPT to external tools, data sources, and apps. "ChatGPT MCP apps" usually refers to apps and connectors exposed to ChatGPT through an MCP server. Most of the apps inside ChatGPT are powered by MCP under the hood, even when users don't see the protocol name.
What MCP actually is
Model Context Protocol is an open protocol — originally introduced by Anthropic and now adopted broadly across the AI ecosystem — that defines a single, standard way for an AI assistant to talk to external tools and data. Instead of every app shipping a custom integration with every assistant, an app exposes its capabilities as an MCP server (a small program that speaks the MCP wire format), and any MCP-capable assistant — including ChatGPT — can connect, discover tools, call them, and read results. It's roughly the "LSP for AI tools" — one protocol, many clients, many servers.
How MCP relates to the ChatGPT apps directory
OpenAI's Apps SDK is built on top of MCP. The apps you see inside ChatGPT — Canva, Spotify, Notion, Booking.com, and the rest — are implemented as MCP servers that ChatGPT discovers and calls. From a user perspective, you still see an "app" you connect from inside chat. From a developer perspective, what you're shipping is an MCP server with a permissions manifest. So in nearly every case, "ChatGPT MCP apps" and "ChatGPT apps" refer to the same thing, just emphasizing different layers of the stack.
Why the distinction matters
Two reasons. First, portability: an MCP server you build for ChatGPT can — in principle — also work with Claude, Cursor, IDE assistants, and any other MCP-capable client. That changes the economics of building an app. Second, transparency: knowing an app speaks MCP tells a security-minded user exactly what permission model is in play (capability discovery, scoped tool calls, no arbitrary code execution on the assistant side), which is more auditable than vendor-specific plugin layers used to be.
Are all ChatGPT apps MCP apps?
In practice, yes for new apps shipped under the Apps SDK. A small number of older or pre-MCP integrations may still exist as legacy connectors that don't use the protocol. For the editorial rankings on this site, we don't distinguish — what matters is whether the app works well in chat, not which protocol it speaks underneath. The MCP framing is most useful if you're a developer building or evaluating an app, not if you're a user choosing one.
What MCP is not
MCP is not an OpenAI-only standard, not a marketplace, and not a billing layer. It does not run prompts or store user data on behalf of the AI assistant. It is purely the wire protocol the assistant uses to talk to your server. Anything beyond that — auth, billing, hosting, discovery — is the responsibility of the surface (ChatGPT, Claude, etc.) and the app developer.