Wire It into Claude Desktop
Edit the config so Claude loads your server.
Wire It into Claude Desktop is a free MCP Academy lesson on CoddyKit — lesson 2 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.
From Script to Real Host
Your server runs, but nobody is talking to it yet. Let’s connect it to a real host: Claude Desktop. 🖥️
It Reads a Config File
Claude Desktop discovers servers from one JSON file named claude_desktop_config.json. You list each server there, and it loads them on start.
Where the File Lives
On macOS the file sits under Application Support; on Windows it lives in your AppData roaming folder. Open it from the app’s settings.
~/Library/Application Support/Claude/claude_desktop_config.jsonThe mcpServers Key
Every server goes inside the top-level mcpServers object. Each key is the name you choose; the value describes how to launch it.
{
"mcpServers": {}
}Command and Args
For each server you give a command to run and an array of args. Together they are exactly how the host spawns your process.
{
"weather": {
"command": "python",
"args": ["/abs/path/server.py"]
}
}Use Absolute Paths
The host launches from its own working directory, so relative paths break. Always point args at an absolute path to your script.
uv Makes It Cleaner
If your project uses uv, set the command to uv and let it run your module in the right environment, no global install needed.
{
"command": "uv",
"args": ["run", "server.py"]
}Pass Environment Variables
Secrets like API keys go in an optional env object. The host injects them when it starts your server, so they stay out of code.
"env": { "API_KEY": "sk-..." }Restart to Apply
Claude reads the config only at launch. After any edit you must fully restart the app for it to pick up your new server.
The Hammer Icon
When it works, a small tools indicator appears in the chat. Clicking it shows the tools your server now offers Claude. 🔨
Name It Carefully
The key you choose under mcpServers becomes the server’s name. Keep it short and unique so multiple servers never clash in the host.
Quick Check
What change does Claude Desktop need before it will load a newly added server?
Recap
You added your server to claude_desktop_config.json with a command, args, and env, used absolute paths, and restarted. It’s live in Claude! ✅
Frequently asked questions
Is the “Wire It into Claude Desktop” lesson free?
Yes — the full text of “Wire It into Claude Desktop” 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 “Wire It into Claude Desktop”?
Edit the config so Claude loads your server. 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 2 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “Wire It into Claude Desktop” 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
- How stdio Transport Works
- Wire It into Claude Desktop
- Explore with MCP Inspector
- Debug a Server That Won't Start