How to Install MCP Servers on Desktop: The Complete 2026 Setup Guide

Table of Contents

1. What You'll Need
2. Step 1: Pick a Desktop MCP Client
3. Step 2: Find Your Config File
4. Step 3: Add an MCP Server to the Config
5. Step 4: Restart the Client
6. Step 5: Verify the Server Is Connected
7. Install Walkthroughs by Client
8. Recommended Starter Stack
9. Common Install Errors (and Fixes)
10. Frequently Asked Questions

What You'll Need

Before you start, make sure you have:

• A desktop MCP client. Claude Desktop, Claude Code, Cursor, Windsurf, Cline, or Zed all work. We cover the first five in this guide.
• Node.js 18 or later. Most MCP servers run via npx, which ships with Node.js. Install from nodejs.org if you don't have it. Some MCPs require Python with uvx instead — we'll flag those individually.
• A text editor. You'll edit one JSON file. Any editor works — Notepad, TextEdit, VS Code, vim. The Skiln Config Generator can build the file for you if you'd rather not touch JSON.
• Five spare minutes. That's the entire install for your first MCP. Each additional MCP afterward takes about 30 seconds.

You do not need to be a programmer. You do not need a paid plan. Every MCP server in our recommended starter stack is free.

Step 1: Pick a Desktop MCP Client

The client is the app you'll talk to. The MCP server is the tool the client plugs into. You need a client first.

For first-time MCP users, install Claude Desktop. Three reasons:

• The config file format is the simplest.
• The UI shows connected MCPs and their tools clearly in a hammer icon at the bottom of the chat.
• Anthropic's documentation is the most beginner-friendly.

Download Claude Desktop from claude.ai/download (macOS or Windows; Linux unofficial). Sign in with your Anthropic account. Free tier works fine for MCP testing.

If you live in the terminal, install Claude Code instead. It's the CLI version of the same protocol. If you live in an IDE, install Cursor or Windsurf. We cover all of these in the per-client walkthroughs below.

Step 2: Find Your Config File

Every MCP client stores its server configuration in a single JSON file. The path depends on your OS and client.

If the file doesn't exist yet, create it. Start with an empty JSON object:

{   "mcpServers": {} }

Step 3: Add an MCP Server to the Config

Each MCP server gets its own entry inside mcpServers. The entry tells the client how to launch the server: which command to run, what arguments to pass, and which environment variables to set.

Here's the smallest possible example — the Filesystem MCP, which gives Claude read/write access to a folder you choose:

{   "mcpServers": {     "filesystem": {       "command": "npx",       "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/yourname/Documents"]     }   } }

Three fields matter:

• command — the executable to run. Usually npx (for Node-based MCPs) or uvx (for Python ones).
• args — the arguments to pass. The first is typically the package name; later args are MCP-specific (here, the folder to expose).
• env (optional) — environment variables. Required when the MCP needs an API key. Example:

"github": {   "command": "npx",   "args": ["-y", "@modelcontextprotocol/server-github"],   "env": {     "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_yourtokenhere"   } }

Add as many MCP server entries as you want — separated by commas, all inside the mcpServers object.

Step 4: Restart the Client

MCP servers boot up alongside the client. The client reads the config file only at startup, so any changes require a full restart — not just closing the chat window.

• Claude Desktop: Cmd-Q (macOS) or right-click the system tray icon and Quit (Windows). Then relaunch.
• Claude Code: Type /quit or hit Ctrl-D, then run claude again.
• Cursor / Windsurf: Full quit (Cmd-Q / Alt-F4), then reopen.
• Cline: Reload the VS Code window (Cmd-Shift-P > Reload Window).

If you skip the restart, the MCP server is silently absent. This is the single most common install failure.

Step 5: Verify the Server Is Connected

Each client shows connected MCPs differently.

• Claude Desktop: Look for the hammer icon at the bottom of the chat input. Click it — connected servers list with their tool counts. If a server is missing or shows an error, the icon glows red.
• Claude Code: Type /mcp to list connected servers and their tools.
• Cursor: Settings > MCP. Connected servers show green; failed ones show red with a hover error.
• Windsurf: Settings > Cascade > MCP Servers. Same colour coding.
• Cline: MCP Servers panel in the Cline sidebar.

If the server is missing or red, check the client's log file for the error message. The most common errors are documented in the Common Install Errors section below.

Install Walkthroughs by Client

Claude Desktop

1. Open the config file at the path in the table above (create it if missing).
2. Add this minimal starter config:

{   "mcpServers": {     "filesystem": {       "command": "npx",       "args": ["-y", "@modelcontextprotocol/server-filesystem", "~/Documents"]     },     "sequential-thinking": {       "command": "npx",       "args": ["-y", "@modelcontextprotocol/server-sequential-thinking"]     }   } }

1. Save the file.
2. Cmd-Q or right-click-Quit the Claude app.
3. Relaunch. Click the hammer icon — you should see 2 servers connected with 5+ tools each.

Claude Code

Claude Code uses a slightly different config path and supports the same JSON format. The easiest way to add a server is the built-in CLI:

claude mcp add filesystem npx -y @modelcontextprotocol/server-filesystem ~/Documents

Or manually edit ~/.claude/claude_mcp_config.json with the same mcpServers JSON shape as Claude Desktop. Then restart with /quit and claude again. List with /mcp.

Cursor

Cursor's MCP config lives at ~/.cursor/mcp.json. Same JSON shape as Claude Desktop:

{   "mcpServers": {     "github": {       "command": "npx",       "args": ["-y", "@modelcontextprotocol/server-github"],       "env": {"GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..."}     }   } }

Restart Cursor fully. Settings > MCP shows connected servers. You can also manage servers via Cursor's settings UI without touching JSON.

Windsurf

Windsurf's config is at ~/.codeium/windsurf/mcp_config.json. Same JSON format. After editing, restart Windsurf and check Settings > Cascade > MCP Servers.

Windsurf has an in-app MCP marketplace as well — Settings > Cascade > MCP Marketplace lets you browse and install MCPs without touching the config file. The marketplace pulls from a curated subset of the Skiln directory.

Cline (VS Code Extension)

Cline is a VS Code extension, so the MCP config lives inside VS Code's settings.json:

{   "cline.mcpServers": {     "filesystem": {       "command": "npx",       "args": ["-y", "@modelcontextprotocol/server-filesystem", "${{workspaceFolder}}"]     }   } }

Cmd-Shift-P > Reload Window to apply. The Cline sidebar shows MCP status.

Recommended Starter Stack

If you're installing your first batch, start with these four MCPs. They cover 80% of common workflows and need zero external API keys:

Once you're comfortable, add one of: GitHub MCP (needs a PAT), Slack MCP (needs a bot token), Notion MCP (needs an integration token), or any of the 10 servers in our Best Desktop MCP Servers roundup.

Common Install Errors (and Fixes)

• "Could not load MCP server" — Almost always a JSON syntax error. Validate your config at jsonlint.com. Missing comma between server entries is the #1 cause.
• "npx: command not found" — Node.js isn't installed or isn't on your PATH. Install Node from nodejs.org and restart your terminal (and the client).
• Server connects but no tools appear — Some MCPs need to enumerate their tools on startup. Wait 5-10 seconds after restart. If still empty, the MCP probably failed to load its config; check the client logs.
• "Permission denied" on the Filesystem MCP — The path in args either doesn't exist or your user doesn't have permissions. Use ~/Documents or ~/Desktop to start.
• MCP works in Claude Desktop but not Claude Code — Different config file paths. Make sure you edited the right one. See the table above.
• API key MCPs return "401 Unauthorized" — Token expired or wrong scope. Regenerate the token with the scopes the MCP's README requires.

Frequently Asked Questions

Do I need to know how to code to install MCP servers?

No. The hardest thing you'll do is edit a JSON config file — you copy a snippet from the MCP's documentation and paste it into the right spot. No programming required. Tools like the Skiln Config Generator and the Smithery CLI can even do the edit for you.

Which MCP client should I install first?

If you're new to MCPs, install Claude Desktop. Its config file is the simplest, the UI shows connected MCPs clearly, and the documentation is the most beginner-friendly. Once you're comfortable, layer on Claude Code for terminal/CLI work or Cursor for IDE work.

Can I run MCP servers without npm or Node.js?

Most MCP servers are distributed as Node packages and run via npx, so Node.js (which includes npm) is the most common prerequisite. Some MCPs ship as Python packages (run via uvx) or as compiled binaries (run directly). The MCP's README will tell you which runtime it needs.

How many MCP servers can I install at once?

There's no hard limit. Claude Desktop, Cursor, and Windsurf all support unlimited concurrent servers. The practical ceiling is your machine's RAM — each MCP runs as a background process when the client is open. On a 16GB machine, 10-20 servers run comfortably; on 32GB+, you can have 50+ active without issues.

Do MCP servers need API keys?

It depends on what they connect to. MCPs that touch your local file system (Filesystem MCP) or run pure logic (Sequential Thinking MCP) need no keys. MCPs that hit external APIs (Stripe MCP, Slack MCP, OpenAI MCP) need the corresponding API key, which you supply via environment variables in the config.

Is it safe to install MCP servers from random GitHub repos?

MCP servers run on your machine with the same permissions as your AI client. That means file access, shell access, and network access. Only install MCPs from authors you trust, and prefer servers from official organisations (Anthropic, GitHub, Supabase, Stripe) or those with 100+ GitHub stars and recent commit activity. Read our MCP security guide for the full checklist.

What's the difference between an MCP and a Claude skill?

MCPs are external tools your AI client can call. Skills are bundles of prompt instructions, scripts, and references that shape how the AI behaves. MCPs add capabilities; skills add expertise. They complement each other and can be installed together. See our full comparison.

Where do I find more MCP servers after I've installed the basics?

Browse the Skiln directory at /browse to filter 75,000+ MCPs by category, client compatibility, or auth requirements. The Top 10 in our Best Desktop MCP Servers roundup is a good starting list once you've got the basics installed.

Last updated: June 04, 2026 · Skiln tracks MCP server releases daily across 10+ source registries.