Step 1 — Find the config file
Every MCP-capable Claude client reads a JSON config file at startup. Here's where to find it:
Mac: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
Linux: ~/.config/Claude/claude_desktop_config.json
If the file doesn't exist, create it with an empty JSON object: {}
Step 2 — Add your server config
On any MCP server page on ClaudeWave, click the Copy config button. Paste inside your existing config, merging the mcpServers object:
{"mcpServers":{"existing-server":{...},"new-server":{"command":"npx","args":["-y","@example/mcp-server"]}}}Placeholders like <api_token> must be replaced with real values. Environment variables are more secure than hardcoding secrets — some servers read from env.
Step 3 — Restart Claude Desktop
Fully quit the app (Cmd+Q on Mac). Reopen. The new MCP server should appear in the tools list (bottom-right of the chat input).
If it doesn't show up, check the logs: Claude Desktop → Settings → Developer → Open Logs. You'll see connection errors, missing commands, or permission issues.
Alternative — Claude Code CLI
If you use Claude Code (the terminal CLI), you can add MCP servers with: claude mcp add <name> <command>. The config is persisted to ~/.claude.json. Restart not required — next claude invocation picks it up.
Troubleshooting
'Command not found' — install the runtime. For npx: brew install node. For uvx: pip install uv. For Docker: install Docker Desktop.
'Permission denied' — your server may need filesystem access. On Mac, grant permission in System Settings → Privacy & Security → Files and Folders → Claude.
'No tools available' — the server started but returned zero tools. Check the server's README for required env vars (API keys, paths, etc).