MCPTutorialTechnical
MCP Installation Deep Dive: Claude Code vs Claude Desktop
A technical guide to installing MCP servers and skills across different Claude platforms. Troubleshooting included.
Steve Kaplan
December 26, 2025
12 min read
Understanding MCP Architecture
The Model Context Protocol (MCP) is an open standard that lets Claude connect to external tools and data sources. Before we install anything, let's understand how it works.
How MCP Works
[Claude] <---> [MCP Client] <---> [MCP Server] <---> [External Tool]
- Claude: The AI model you interact with
- MCP Client: Built into Claude Code/Desktop, handles the connection
- MCP Server: A small program that wraps your tool
- External Tool: Database, API, service, or any capability
MCP Server Types
- Local servers - Run on your machine (most common)
- Remote servers - Hosted externally (enterprise setups)
- Hybrid servers - Local process connecting to cloud services
Installing Skills in Claude Code
Claude Code is the CLI tool for developers. Installation is straightforward.
Step 1: Open Your Config
claude code --config
Or manually edit ~/.claude/settings.json
Step 2: Add the MCP Server
{
"mcpServers": {
"git-commit-writer": {
"command": "npx",
"args": ["-y", "@claudeskillshq/git-commit-writer"]
}
}
}
Step 3: Restart Claude Code
claude code
Step 4: Verify Installation
claude code --list-servers
You should see your new skill listed.
Installing Skills in Claude Desktop
Claude Desktop uses a similar config but in a different location.
macOS
~/Library/Application Support/Claude/claude_desktop_config.json
Windows
%APPDATA%\Claude\claude_desktop_config.json
Linux
~/.config/claude/claude_desktop_config.json
Config Format
{
"mcpServers": {
"skill-name": {
"command": "npx",
"args": ["-y", "@package/name"],
"env": {
"API_KEY": "your-key-here"
}
}
}
}
Troubleshooting Common Issues
"Server not found"
- Check the command path
- Ensure npx is in your PATH
- Try running the command manually first
"Connection refused"
- Server crashed or didn't start
- Check logs:
claude code --logs - Verify environment variables
"Timeout waiting for server"
- Server taking too long to initialize
- Add to config:
"timeout": 30000
"Permission denied"
- npm needs global install permissions
- Try:
npm config set prefix ~/.npm-global
Environment Variables
Many skills need API keys or configuration:
{
"mcpServers": {
"github-integration": {
"command": "npx",
"args": ["-y", "@claudeskillshq/github"],
"env": {
"GITHUB_TOKEN": "${GITHUB_TOKEN}"
}
}
}
}
The ${VAR} syntax pulls from your system environment.
Multiple Skills Setup
Install as many skills as you need:
{
"mcpServers": {
"git-commit-writer": { ... },
"code-reviewer": { ... },
"jira-integration": { ... }
}
}
Performance Tips
- Only install skills you actually use
- Skills with external API calls add latency
- Local-only skills are fastest
- Consider disabling unused skills