Which of the following are established MCP client implementations?
An MCP client lives inside a host app and connects to servers. Claude Code, Cursor, Continue, and Cline qualify; an inference library and a model playground do not.
Picture MCP servers as appliances and an MCP client as the wall socket inside a building. The building is the host app you actually use, like a code editor or a terminal assistant. To plug an appliance in, the building needs a socket wired to the same standard. Claude Code, Cursor, Continue, and Cline all wired in that socket, so they can plug into any compliant server. Hugging Face Transformers is more like a toolbox for building the appliance's motor; it never had a wall socket, because that is not its job. OpenAI Playground is a showroom for trying out one brand of motor, with no socket either. The question asks which of these buildings actually have the socket installed.
Detailed answer & concept explanation~7 min readEverything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example. Click to expand.
Everything you need to truly understand this topic: intuition, mechanics, step by step explanation, code, formulas, and worked example.
Everything important, quickly.
3 min: define the host, client, and server roles, name the four correct clients, then explain why an inference library and a single-vendor playground fail the client test.
| Option | Category | MCP client? |
|---|---|---|
| Claude Code | Terminal coding agent | Yes |
| Cursor | AI-native IDE | Yes |
| Continue | VS Code extension | Yes |
| Cline | Autonomous coding agent | Yes |
| Hugging Face Transformers | Model inference library | No |
| OpenAI Playground | Vendor model console | No |
Real products, models, and research that use this idea.
- Claude Code reads an MCP config, spawns each server as a subprocess, and discovers its tools at session start.
- Cursor adds MCP servers through a JSON config and settings UI, mirroring Claude Desktop's claude_desktop_config.json format.
- Continue, the open-source VS Code extension at continuedev/continue, documents MCP server configuration for any compliant server.
- VS Code with GitHub Copilot and ChatGPT connectors both shipped MCP client support in 2025, showing cross-vendor adoption.
What an interviewer would ask next. Try answering before peeking at the approach.
QHow would you verify that a new AI tool is a genuine MCP client rather than just tool-calling?
QWhy did developer tooling adopt MCP before consumer apps?
Don't say thisRed flags and common mistakes that signal junior thinking. Click to expand.
Red flags and common mistakes that signal junior thinking. Click to expand.
Counting any AI developer tool as an MCP client. A library that only runs model inference, or a playground that just calls one vendor's API, has no MCP client built in.
The night-before-the-interview bullets. Scan these on the way to the call.
Primary sources. Skim if you want the original framing.
Same topic, related formats. Practice these next.