Claude Desktop, Cursor, VS Code, or Claude Code — pick your MCP client
They all speak MCP, but the install path and best use case differ. A quick decision guide.
MCP is client-agnostic, but the experience isn't. Here's the short version.
Claude Desktop
Best for general chat + tools on your machine. Install is a config file (or a deep link via the Unyly widget). Remote servers need the mcp-remote bridge. Great default for non-developers.
Claude Code (CLI)
Best for coding in the terminal. claude mcp add --transport http … wires remote servers in one line, and it handles OAuth flows for you. Native http transport, no bridge.
Cursor
Best for IDE-native coding with a nice one-click deep link (cursor://). Servers show up in the editor's tool list. Strong for dev stacks (GitHub, Postgres, filesystem).
VS Code
Best if you live in VS Code already — official MCP support, deep-link install, project-scoped config.
The meta-answer
Most power users run several. Install once per client, or connect the Unyly Gateway and every client shares the same pinned set. Browse MCPs.