Skip to content
Back to blog

MCP Clients Explained: Claude, Cursor, and the Growing Ecosystem

An MCP server is only half the picture — here's a guide to the clients (Claude Desktop, Cursor, GitHub Copilot, and others) that connect to MCP servers, and how each one works.

An MCP server exposes tools, resources, and prompts. An MCP client is the AI application that connects to it, discovers what's available, and lets the model call those tools. The two sides are defined by the same protocol, which means a server built once works with any compliant client.

Here's what the client ecosystem looks like in 2026.

How clients connect

MCP clients connect to servers over one of two transports:

  • STDIO — the client launches the server as a child process and communicates over stdin/stdout. Used for local tools on the same machine.
  • Streamable HTTP — the client connects to a URL over HTTP. Used for remote servers and multi-user deployments.

Each client has its own configuration format for adding MCP servers, but the connection model is the same.

Claude Desktop

Connection options: local STDIO configuration, remote connectors, or a local HTTP bridge

Claude Desktop is Anthropic's native desktop client and has one of the earliest MCP integrations. You configure servers in its claude_desktop_config.json:

JSON

A command-based local configuration can bridge to an HTTP server with mcp-remote:

JSON

Claude also supports custom remote MCP connectors. Use that setup for hosted endpoints; it is separate from local command-based configuration.

Cursor

Transport support: Streamable HTTP and STDIO

Cursor added MCP support in 2025 and treats it as a first-class feature. HTTP servers connect directly — no bridge needed:

JSON

STDIO servers use the same command / args pattern as Claude Desktop. Cursor exposes connected tools inside the Composer and Chat interfaces, and the model can call them during normal coding sessions.

GitHub Copilot

In VS Code, configure MCP servers through mcp.json or the MCP: Add Server command. STDIO and HTTP connections are supported. Follow the VS Code MCP documentation; other Copilot surfaces have their own setup and capability limits.

Windsurf

Transport support: STDIO and HTTP

Windsurf (by Codeium) is an AI-first IDE that supports MCP server connections through its cascade feature. Configuration is similar to Cursor — servers are declared in a settings file and become available during AI-assisted coding sessions.

Other clients

The MCP ecosystem is growing quickly. Other clients with MCP support include:

  • Zed — the collaborative code editor has MCP integration in its assistant.
  • Continue.dev — the open-source AI coding assistant supports MCP for tool extension.
  • Custom agents — any application built with the MCP TypeScript or Python SDK can act as a client.

What this means for your server

MCP provides a shared protocol, but clients differ in supported transports, authorization flows, and optional capabilities. Test your tools with each target client instead of assuming identical behavior. Use the connection reference and a runnable template to establish a working baseline.

Next steps

One framework to rule them all