Claude Desktop MCP Setup – Step‑by‑Step Configuration (2026)
You've heard that MCP unlocks Claude's real power, but now you're staring at a blank claude_desktop_config.json file with no idea what to put in it. This guide takes you from zero to a fully configured Claude Desktop MCP setup in 10 minutes – with exact config templates for Windows and macOS, and a free premium starter kit (normally $49) that bundles the 5 best MCP servers pre‑configured.
For a concrete example, follow the GitHub MCP Server setup. For server comparisons, see Best MCP Servers for Claude.
What MCP does in Claude Desktop (2026)
MCP (Model Context Protocol) is how Claude Desktop connects to external tools like GitHub, local files, databases, and APIs. By 2026, MCP is the default way to give Claude real‑world agency beyond the chat window.
Without MCP, Claude's knowledge is limited to the conversation. With MCP servers, Claude can read live data, edit files, run commands, and complete complex workflows accurately.
What you need before starting
Claude Desktop installed
Latest Claude Desktop app (2026) installed and signed in. The free tier works perfectly for MCP.
Node.js LTS (v22+)
Most MCP servers run via npx, so Node.js must be installed and available in your terminal.
MCP server config block
Every MCP server provides a JSON snippet. Our free premium kit bundles the top 5 together.
Step 1: Install Node.js for npx MCP servers
Most MCP servers are npm packages launched with npx. Node.js LTS (v22 or newer) is required for the smoothest Claude Desktop MCP experience in 2026.
Quick Node.js check
Run these commands in your terminal:
node -v npm -v npx -v
If any fail, install the latest LTS from nodejs.org before proceeding.
Step 2: Open claude_desktop_config.json
Claude Desktop reads MCP servers from claude_desktop_config.json. This file defines which servers start when Claude launches.
File locations (2026)
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
You can also open it from Claude Desktop's developer menu (Settings → Developer → Edit Config).
Step 3: Add your first MCP server
Start with GitHub MCP Server – it gives Claude access to repos, PRs, and issues.
Basic claude_desktop_config.json
{
"mcpServers": {
"github": {
"command": "npx",
"args": ["-y", "@github/github-mcp-server"],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "YOUR_TOKEN"
}
}
}
}Replace YOUR_TOKEN with your GitHub personal access token.
Step 4: Restart Claude Desktop
Save the config file, then completely quit Claude Desktop (Cmd+Q / Alt+F4) and reopen it. The new MCP server will load only after a full restart.
Step 5: Test the MCP server
Once restarted, look for the hammer icon (tools) in Claude's input bar. Try a test prompt:
- List my GitHub repositories
- Show me the latest PRs
- Search for authentication middleware
Adding multiple MCP servers
A powerful yet simple stack for 2026:
Common MCP errors & fixes
Invalid JSON
Check commas and braces in claude_desktop_config.json.
Node.js not found
Ensure Node.js is in your PATH (restart terminal/Claude after install).
Missing env variables
Many servers need tokens – verify env block.
Wrong file path
Confirm you're editing the correct config file (use Claude's developer menu).
Not restarted
Full quit and reopen Claude after changes.
Security tips for 2026
Least privilege
Grant only necessary scopes to each MCP server.
Be careful with local access
File system / shell MCP servers can be powerful – understand the risk.
Rotate tokens
Regularly refresh API keys and remove unused credentials.
Related Guides
Download the Ultimate Claude Desktop MCP Starter Kit
Get a ready‑to‑use claude_desktop_config.json with the 5 best MCP servers pre‑configured: GitHub, Context7, Desktop Commander, Semgrep, and Filesystem. Plus a troubleshooting checklist. Normally sold for $49 — free today.
- ▹ GitHub, Context7, Desktop Commander, Semgrep, Filesystem
- ▹ Correct environment variables & args
- ▹ Error‑fix checklist (JSON, Node, tokens, paths)
Instant .json download. No email required.
Frequently asked questions (2026)
What is Claude Desktop MCP setup in 2026?▾
In 2026, Claude Desktop MCP setup is the standard way to connect Claude to external tools via Model Context Protocol servers. You configure a local claude_desktop_config.json file to launch MCP servers that give Claude access to GitHub, local files, databases, APIs, and more – all from the chat interface.
Do I still need Node.js for npx MCP servers in 2026?▾
Yes. The vast majority of MCP servers remain npm packages launched via npx. Node.js LTS (v22 or later) is recommended and must be present in your system PATH for Claude Desktop to start them.
Where is the Claude Desktop MCP config file in 2026?▾
On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows: %APPDATA%\Claude\claude_desktop_config.json. The location has remained consistent through 2026 updates.
Why is my MCP server not appearing in Claude Desktop (2026)?▾
Common 2026 causes include: invalid JSON in claude_desktop_config.json, missing Node.js for npx servers, incorrect environment variables, or not fully restarting Claude Desktop. Also check that your MCP server package is still maintained and uses an up-to-date npx command.
Can I add more than one MCP server in 2026?▾
Absolutely. Claude Desktop supports multiple MCP servers inside the mcpServers object. Most developers run 3–5 servers for a complete workflow. Our free premium starter kit gives you the top 5 pre-configured.
Which MCP server should I install first in 2026?▾
GitHub MCP Server remains the #1 first install for developers. Followed by Context7 for live docs, and Desktop Commander for local file/shell access. Semgrep is excellent for security-focused teams. All five are included in our free downloadable starter kit (normally $49).
Browse ready‑to‑use MCP servers
Explore the full MCPIndex directory for copy‑ready configs, setup steps, and category pages.