By Fahad Murtaza · Published
MCP clients compared: Claude, Cursor, ChatGPT
MCP clients compared: Claude, Cursor, ChatGPT and how to choose
Most MCP writing is about servers. The client is the other half, and it decides more than people expect: how you sign in, which transports work, how many tools the model sees and whether a destructive call asks you first. Two clients can talk to the same server and give very different results.
This article explains what an MCP client is, the axes on which clients differ, and how four common ones compare when the server is a WordPress site running WP MCP. If you are new to the protocol, start with what an MCP server is.
What is an MCP client? It is the component inside an AI application that connects to MCP servers. It asks a server what tools it has, hands that list to the model, and sends the tool calls the model decides to make. The application around it, such as Claude Desktop or Cursor, is the host.
Hosts, clients and servers
The terms are easy to mix up, so here are the three roles:
- Host. The application you use. Claude Desktop, Claude Code, Cursor and ChatGPT are hosts.
- Client. A connection object inside the host. The host runs one client per server it talks to.
- Server. The program or service that exposes tools. A WordPress site with an MCP plugin is one.
In everyday speech people call the host the client, and that is fine. The distinction only matters when something breaks and you need to know which side to debug.
How clients differ
Transport
A client reaches a server in one of two main ways. stdio starts the server as a local process and talks over standard input and output. Streamable HTTP connects to a URL. A client that supports only stdio cannot talk to a remote server directly, which is why bridges such as mcp-remote exist. The remote MCP servers article covers the trade-offs.
WordPress needs the HTTP route in practice, because the site is a remote server. WP MCP also ships a stdio bridge, wp mcp-stdio serve --user=<login>, for a machine that has WP-CLI and the site’s files.
Sign-in
Clients authenticate in two different ways:
- A static header, such as
Authorization: Basic ..., set in a config file. WordPress application passwords work this way. - OAuth, where the client discovers the server’s authorization endpoints, opens a browser, and you approve access.
Some clients do both, some do only one. A client that can only use OAuth cannot send an application password, and a server that has OAuth switched off cannot serve it. The MCP OAuth explainer covers how the flow works.
Tool limits and token cost
Every tool definition the server lists is sent to the model, so a large list costs tokens on every request and can push out other context. Some clients also cap how many tools they accept. A server with hundreds of tools needs a way to present a smaller surface.
WP MCP registers up to 407 tools: 274 in the free plugin and 133 in Pro. The number a site shows depends on its active plugins. Compact mode is an optional setting that advertises five tools: list-tools, get-tool-schema, call-tool, get-connection-info and get-site-context. Every other tool is reached through call-tool. It changes only what is advertised. A call through call-tool still runs the target tool’s own permission check, snapshot and rate limit. The advertised list shrinks from hundreds of full definitions to five short ones.
Prompts, resources and elicitation
Beyond tools, the protocol has other features, and clients support them unevenly:
- Prompts are reusable instructions a client can show as slash commands.
- Resources are readable context a client can attach.
- Elicitation lets a server ask the person a question mid-call, for example to confirm a destructive action.
WP MCP serves its agent skills as prompts and a site summary as a resource, and uses elicitation for its confirm: true gate where the client advertises support. A client without those features still works, because the server falls back to the plain behavior.
Approval and auto-run
Most hosts ask before running a tool, and some let you switch that off. This is a human check on a call, not a check on its effect. A person who has approved forty harmless reads will approve a destructive write on the forty-first. That is why a server-side safety layer matters whatever the client does. See MCP security for WordPress.
Four clients and a WordPress site
This table uses what the WP MCP documentation records, and says plainly how well each path is tested.
| Client | How it signs in | Setup it needs | How well tested |
|---|---|---|---|
| Claude Code | Application password | One command or one .mcp.json entry. Works on a default install. |
Most tested, alongside Claude Desktop |
| Claude Desktop | Application password (desktop bundle or config file), or OAuth for the custom connector | Download the bundle and enter the password. The custom connector needs OAuth switched on first. | Most tested, alongside Claude Code |
| Cursor | Application password | One entry in .cursor/mcp.json. Works on a default install. |
Supported through the standard MCP config. Our own testing is mostly with the Claude clients. |
| ChatGPT | OAuth only, it cannot send an application password | A site administrator switches OAuth on in wp-config.php, then adds the site as a custom MCP server |
Works through OAuth once enabled. Not fully tested yet. |
A few points sit behind those rows.
Claude Code takes a remote URL and a header directly, so it is the shortest path. The Claude Code guide covers scopes and .mcp.json.
Claude Desktop is a chat app whose config file runs local servers only. A url entry is skipped, so WordPress goes through the desktop bundle, an mcp-remote entry, or a custom connector. The Claude Desktop guide walks through all three, and the custom connectors guide covers the OAuth route.
Cursor accepts remote entries in its config, so the WordPress endpoint and Basic header go straight in. The Cursor guide shows the file and the troubleshooting.
ChatGPT needs OAuth, which WP MCP ships switched off. It will not connect until the site owner turns it on, and we have not tested that path as fully as the Claude ones, so treat it as working but unproven.
Other MCP clients exist, including editors and agent frameworks. Any that can reach an HTTP MCP endpoint and send a header, or complete OAuth, can in principle connect to the same address. We list only the four above because those are the ones we can describe from the record.
How to choose
Pick by how you work, then by sign-in.
- You work in a terminal or an IDE. Claude Code or Cursor. Both take the URL and header directly and keep the credential in your own config.
- You want a chat app and no config files. Claude Desktop with the bundle. It needs nothing else installed.
- You want OAuth and no stored password. The custom connector in Claude, or ChatGPT. Both need OAuth switched on, and a public site.
- The site is private or on localhost. Use a client that connects from your machine: Claude Code, Cursor, or Claude Desktop with the bundle. A hosted client’s requests come from the provider’s side and cannot reach a private address.
- You manage many client sites. Prefer a dedicated WordPress user per site, a scoped identity, and a read-only token until you trust the workflow.
None of these choices replaces undo. The server-side layer is the same across clients: WP MCP snapshots each supported write before it happens, verifies it, and lets you roll back one operation or a whole session from the AI or from wp-admin. A few changes cannot be snapshotted, and the plugin lists them rather than claim an undo it cannot do.
Test the client against the server separately
When a client does not work, you want to know which half to fix. The two-minute method is to take the exact URL and header from the client config and run them through MCP Inspector. If the Inspector connects and lists tools, the site is fine and the fault is in the client config or the client itself. If the Inspector fails too, the fault is the endpoint, the credential or the network.
For what the server exposes once a client is connected, see the WordPress MCP server page, and pricing for what Pro adds.
New to all of this? Follow the MCP tutorial from first connection to first undo.
Common questions
What is an MCP client?
An MCP client is the part of an AI application that connects to MCP servers, lists their tools and sends the tool calls the model decides on. Claude Code, Claude Desktop, Cursor and ChatGPT each contain one. The application that holds the client is called the host.
What is the difference between an MCP client and an MCP server?
The server offers tools, resources and prompts, such as a WordPress site that can create a post. The client sits inside an AI application, connects to the server, and runs the calls the model chooses. One host can run several clients, one per server.
Which MCP clients work with WordPress?
Any client that can reach an HTTP MCP endpoint can work with a site running WP MCP. The Claude clients are the most tested, Cursor works through the standard config, and ChatGPT works only after OAuth is switched on and is not fully tested yet.
Do all MCP clients support the same features?
No. They differ on transports, sign-in, how many tools they accept, and whether they support prompts, resources and elicitation. A server should work in the basic case everywhere and use newer features only where the client advertises them.
Why do some MCP clients show fewer tools than the server has?
Some clients cap the number of tools they pass to the model, and every tool definition costs tokens. WP MCP has an optional compact mode that advertises five tools and reaches the rest through call-tool, which keeps the list small without removing any capability.
Which MCP client should I start with for WordPress?
Claude Code if you work in a terminal, and Claude Desktop if you want a chat app. Both work on a default install with an application password. Choose ChatGPT only if you are ready to switch OAuth on first.