Connecting to Claude
Walk through the four phases of connecting an MCP server to Claude Desktop or Claude Code -- from installation to live tool usage. Click each phase tab below to walk through the process step by step.
Phase 1: Install Your MCP Server
In this phase, you get the MCP server code onto your machine. MCP servers are typically Node.js packages published to npm, or standalone scripts you run locally. Installation is straightforward:
Option A: Install from npm
Most community MCP servers are published as npm packages. Install globally or use npx:
Option B: Run your own server
If you built a custom server (like in Lesson 4), you can run it directly with Node or compile it first:
Phase 2: Configure in Claude
In this phase, you tell Claude where to find your server by editing a config file. This JSON file maps server names to the commands that launch them.
Claude Desktop Config Location
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Key Config Fields
command — The program to run (node, npx, python, etc.). This is what launches your server.
args — Extra information passed to the command, like which directory to access or which server package to use.
env — Secret values the server needs to work, like API keys or database connection strings. These stay on your machine.
Phase 3: Claude Discovers Tools
In this phase, Claude automatically connects to your server and asks "what can you do?" This handshake happens every time Claude starts. Here is what happens under the hood:
This lesson is for Pro members
Unlock all 520+ lessons across 52 courses with Academy Pro.
Already a member? Sign in to access your lessons.