Claude Desktop
Anthropic’s official desktop app with native MCP support.
VS Code + GitHub Copilot
Agent mode in VS Code with MCP server connections via
.vscode/mcp.json.Cursor
AI-first code editor with MCP server support.
Cline & Windsurf
Community editors and extensions with MCP integration.
Prerequisites
- A working MCP server (see Building Your First Server)
- The host application installed
- Basic familiarity with JSON configuration files
Claude Desktop
Claude Desktop uses a JSON config file to define which MCP servers are available.Configuration file location
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
Configuration format
Configuration fields
| Field | Description |
|---|---|
command | Executable to launch the server |
args | Array of command-line arguments |
env | Environment variables for the server process |
Open the config file
Navigate to the configuration file path for your OS. Create it if it doesn’t exist.
Restart Claude Desktop
Close and reopen Claude Desktop. Your server should appear in the tools list.
VS Code (GitHub Copilot Agent mode)
VS Code uses a workspace-level.vscode/mcp.json file. This was covered in detail in VS Code Integration.
Cursor
Cursor supports MCP servers through its settings.Cline
Cline is a VS Code extension with MCP support.Transport types
All hosts support both transport types:| Transport | Configuration | Use case |
|---|---|---|
stdio | "type": "stdio" with command + args | Local servers — host manages process lifecycle |
sse / http | "type": "sse" with url | Remote servers running independently |
SSE server example
Troubleshooting
Server not appearing in tools list
Server not appearing in tools list
- Check the config file for JSON syntax errors (use a JSON validator)
- Verify the
commandpath is correct and the executable is available in your PATH - Restart the host application after changes
- Check the host’s logs for startup errors
Server crashes on startup
Server crashes on startup
- Test the command manually in a terminal first:
python server.py - Ensure all dependencies are installed (
pip install -r requirements.txt) - Check that environment variables like
API_KEYare set correctly
Tools available but not working
Tools available but not working
- Use the MCP Inspector to test your server independently of the host
- Check the server’s error output in the host’s developer tools or logs
- Verify tool parameter schemas match what you’re sending
Key takeaways
- Each MCP host reads a JSON config file that maps server names to their startup
commandandargs. - For
stdioservers, the host manages the process — no port configuration needed. - For remote servers, use
ssetransport with aurlpointing to your server. - Always test your server with the MCP Inspector before configuring it in a host.