The Host: Claude Desktop & IDEs
The AI app the user actually opens and talks to.
The Host: Claude Desktop & IDEs is a free MCP Academy lesson on CoddyKit — lesson 1 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the MCP Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Meet the Host
The host is the AI app a person actually opens and talks to. Think Claude Desktop or an AI-powered code editor. It is the front door to everything MCP.
The Host Owns the Model
A host is the only part of MCP that holds a connection to the language model. Servers never talk to the model directly, only the host does.
Claude Desktop as a Host
Claude Desktop is the classic MCP host. You chat in it, and behind the scenes it can reach out to any servers you have connected.
IDEs Are Hosts Too
Coding tools like an AI-enabled IDE are also hosts. They embed a model and let it use MCP servers to read files or run tasks for you.
The Host Decides What Connects
You, through the host, choose which servers are trusted. The host reads a config file listing the servers it should launch and connect to.
A Host Config Entry
In Claude Desktop, each server lives under mcpServers in a JSON config. One key per server, with the command that starts it.
{
"mcpServers": {
"weather": { "command": "python", "args": ["server.py"] }
}
}The Host Holds the Permissions
Because the host sees the user, it enforces consent. Before a tool runs, the host can pause and ask you to approve the action.
One Host, Many Servers
A single host can wire up many servers at once. The host blends all their tools together into one capable assistant for you.
The Host Is Not the Server
Do not confuse them. The host is the user-facing app with the model; a server is a separate program that simply offers capabilities.
Hosts Launch Local Servers
For local setups, the host usually starts each server as a child process. It runs the command you configured and keeps it alive while you work.
Why the Host Matters
The host is where context, model, and user meet. Understanding it first makes the client and server roles far easier to follow.
Quick Check
Identify which MCP role holds the model connection.
Recap
You met the host: the AI app like Claude Desktop or an IDE that holds the model, reads server config, and asks for your consent. Nicely done!
Frequently asked questions
Is the “The Host: Claude Desktop & IDEs” lesson free?
Yes — the full text of “The Host: Claude Desktop & IDEs” is free to read here on the web, and the MCP Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the MCP Academy course, upgrade to CoddyKit PRO.
What will I learn in “The Host: Claude Desktop & IDEs”?
The AI app the user actually opens and talks to. You practise MCP Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start MCP Academy?
No prior experience is required. MCP Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 1 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “The Host: Claude Desktop & IDEs” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this MCP Academy lesson?
Yes. Every MCP Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- The Host: Claude Desktop & IDEs
- The Client: One Link Per Server
- The Server: Where Tools Live
- Tracing a Request End to End