One Host, Many Servers
Run a fleet of servers behind a single client app.
One Host, Many Servers 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.
One App, Many Powers
So far you have run a single server. But a real host like Claude Desktop can connect to many servers at once, each adding its own set of skills. 🔌
Why Not One Giant Server?
You could cram everything into one server, but small focused servers are easier to build, test, and reuse. One does files, another does GitHub, another does search.
The Host Coordinates
The host is the conductor. It launches each server, opens a client for it, and gathers all their tools into one menu the model can choose from.
One Client per Server
Remember the one-link rule: the host spins up a separate client for every server. Three servers means three independent client connections.
Config Lists Them All
You register each server in the host's config under mcpServers. Add an entry and the host knows one more place to find tools.
"mcpServers": {
"files": {...},
"github": {...}
}Tools Merge Into One Pool
At startup the host asks each server for its tools and merges them into a single pool. The model sees one combined list, not three separate ones.
Servers Stay Isolated
Each server runs in its own process. If the search server crashes, the files and GitHub servers keep working, so one fault does not sink the whole app.
The Model Sees Capabilities
The model never thinks in servers. It just sees a flat list of capabilities and picks the best tool for the task, wherever it lives.
Routing Calls Back
When the model calls a tool, the host knows which server owns it and routes the request to that server's client. The reply travels back the same path.
Mix and Match Freely
Because servers are independent, you can add, remove, or upgrade one without touching the others. Your toolset grows like installing plugins. 🧩
The Big Picture
A fleet of small servers behind one host gives the model rich, combined powers while keeping each piece simple and replaceable. ✨
Quick Check
How does a host manage three separate MCP servers?
Recap: One Host, Many Servers
A host runs many small servers, each with its own client, and pools all their tools. Isolation keeps faults contained and lets you swap pieces freely. 🎉
Frequently asked questions
Is the “One Host, Many Servers” lesson free?
Yes — the full text of “One Host, Many Servers” 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 “One Host, Many Servers”?
Run a fleet of servers behind a single client app. 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 “One Host, Many Servers” 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
- One Host, Many Servers
- Avoid Tool Name Collisions
- Server Registries & Discovery
- Compose Tools Across Servers