Skip to Content
Add MCP Servers to Claude Desktop

Set up MCP in Claude Desktop without guesswork. Pick a safe server, copy a working config snippet, understand the required files and env vars, and make your first tool call.

First Tool Call Help
Add MCP Servers to Claude Desktop

Add MCP Servers to Claude Desktop

If your goal is “get one MCP server working in Claude Desktop today without breaking local security,” this is the shortest path.

Server or guideBest forNot ideal whenAuth / setupPermission risk
Connect Claude to SQL Databases with MCPAnalytics, app databases, read-only data questionsYou need mail, calendar, or local terminal accessDB credentialsMedium
Connect Claude to Kubernetes with MCPCluster visibility and rollout troubleshootingYou only need local file or email workflowsKubeconfig / cloud authHigh
MCP GSuite ServerGmail and Calendar in one setupYou only need lightweight task managementOAuth2 + local auth filesHigh
MCP Shell ServerWhitelisted local shell commandsYou need broad host control or zero local-risk rolloutAllowed command listHigh
CLI MCP ServerRestricted command execution inside a chosen directoryYou need a polished SaaS integration firstAllowed directory + command/flag policyHigh

Quick selection (30 seconds)

  • Pick a read-oriented data server first if you want the safest first success.
  • Pick GSuite if your workflow lives in Gmail or Calendar.
  • Pick Shell or CLI only if you are comfortable reviewing every command scope and local permission boundary.
  • Avoid starting with a high-blast-radius server if the only goal is to prove Claude Desktop MCP works.

Copy-paste config (Claude Desktop)

This generic starter pattern is the lowest-friction way to add one server and verify Claude Desktop can see it.

{
  "mcpServers": {
    "my-first-server": {
      "command": "uvx",
      "args": [
        "mcp-shell-server"
      ],
      "env": {
        "ALLOW_COMMANDS": "pwd,ls,cat"
      }
    }
  }
}

If you prefer a local checkout instead of a published package, switch uvx to uv and add --directory /absolute/path/to/repo run <server-command>.

Setup checklist

ItemRequiredSensitiveNotes
claude_desktop_config.json accessYesNomacOS path: ~/Library/Application Support/Claude/claude_desktop_config.json
Correct command binaryYesNoCommon values are uv, uvx, node, or npx
Server-specific auth filesSometimesYesOAuth JSON, API keys, or credentials dir depending on the server
Least-privilege env varsYesSometimesStart with read-only or whitelisted scopes only
Claude restart after config updateYesNoClaude Desktop usually needs a restart to load changes

First tool-call prompts

  • “List the tools exposed by this MCP server and explain which one is safest to test first.”
  • “Run a low-risk read-only check so I can confirm the server is connected.”
  • “Tell me which credentials or local files this server can access before we do anything else.”

Fastest failure checks

  • If Claude does not show the server, check the JSON for trailing commas or the wrong command.
  • If the server starts but tools fail, verify auth files and env vars before debugging prompts.
  • If the workflow touches local files or shell commands, reduce permissions first and retest with a single safe command.

Risk and permission notes

  • Local execution servers: never start with unrestricted command access if a small whitelist is enough.
  • Workspace tools: keep OAuth scopes narrow and isolate auth files outside your repo.
  • Database and infra tools: begin with read-only roles, not production write credentials.
  • Approval discipline: if the server can execute commands or write data, review the first several actions manually.

FAQ

What is the safest first MCP server for Claude Desktop?

A read-only data or task server is usually the safest first step because you can validate connectivity without giving Claude host-level control.

Should I use uvx, npx, or a local checkout?

Use the published command when you want the shortest setup path. Use a local checkout when you need to inspect source, pin a branch, or supply local config files next to the repo.

Why does Claude Desktop still not see my server after editing the config?

The most common causes are invalid JSON, the wrong executable name, or forgetting to restart Claude Desktop after saving the file.

Sources and freshness

  • Sources: existing server detail pages linked above.
  • Updated: March 15, 2026.
Last updated on