Mac is generally the easiest platform for MCP server setup — Unix paths, Homebrew for package management, and no PowerShell quirks. But there's one trap that catches nearly everyone on Apple Silicon Macs: Claude Desktop doesn't see the same PATH as your terminal, so npx silently fails. Here's how to set everything up correctly from the start.

Step 1: Install Node.js via Homebrew (recommended)

If you don't have Homebrew, install it first:

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

Then install Node.js LTS:

brew install node

After installing, find out exactly where npx lives — you'll need this path for your config:

which npx

On Apple Silicon Macs, the output is usually /opt/homebrew/bin/npx. On Intel Macs, it's usually /usr/local/bin/npx. Write this path down.

Mac MCP server setup steps: install Node.js via Homebrew, find claude_desktop_config.json at ~/Library/Application Support/Claude, write the config with absolute paths, restart Claude Desktop with Cmd+Q, with common macOS gotchas about path format and npx location
Mac MCP setup steps with the correct config file path and key gotchas for Apple Silicon and nvm users.

Step 2: Open the Claude Desktop config file

The config file lives in a hidden Library folder. The fastest way to reach it:

  1. Open Finder
  2. Press Shift+Cmd+G (Go to Folder)
  3. Paste: ~/Library/Application Support/Claude/
  4. Press Enter

Open claude_desktop_config.json in VS Code or any text editor. If it doesn't exist, create it.

Step 3: Write the Mac-correct config

Here's the key difference from generic guides: use the full path to npx, not just npx.

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

Replace /opt/homebrew/bin/npx with whatever your which npx output was. Replace the path argument with the folder you want Claude to access.

If you're on an Intel Mac, use /usr/local/bin/npx instead. If you installed Node via the nodejs.org installer rather than Homebrew, it might be at /usr/local/bin/npx regardless of chip.

Step 4: Restart Claude Desktop

Right-click the Claude dock icon and select "Quit" (or Cmd+Q with Claude focused). Then reopen it. Test by asking "what tools do you have?" in a new chat.

Mac MCP server recommended starter config JSON showing Filesystem, GitHub, and Brave Search servers with correct absolute paths for macOS, plus tips for Node via Homebrew versus nvm, config file location, and Cmd+Q quit shortcut
Ready-to-use Mac starter config with three servers — plus Mac-specific tips for node path, config location, and quitting Claude.

Adding Python-based MCP servers on Mac

Some servers use Python instead of Node.js. The recommended approach is uv — a fast Python package manager. Install it:

curl -LsSf https://astral.sh/uv/install.sh | sh

Then find its path: which uvx — usually /Users/yourname/.local/bin/uvx. Use the full path in your config:

"git": {
  "command": "/Users/yourname/.local/bin/uvx",
  "args": ["mcp-server-git", "--repository", "/Users/yourname/projects/myapp"]
}

The recommended Mac starter config

Here's a complete config with the most useful servers, all using full paths for Apple Silicon:

{
  "mcpServers": {
    "filesystem": {
      "command": "/opt/homebrew/bin/npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/yourname/projects"]
    },
    "memory": {
      "command": "/opt/homebrew/bin/npx",
      "args": ["-y", "@modelcontextprotocol/server-memory"]
    },
    "brave-search": {
      "command": "/opt/homebrew/bin/npx",
      "args": ["-y", "@modelcontextprotocol/server-brave-search"],
      "env": {
        "BRAVE_API_KEY": "BSAxxxxxxxxxxxx"
      }
    }
  }
}

Honestly, this three-server combo — filesystem, memory, and Brave Search — is the one I'd start every new Mac setup with. It covers file access, persistent context, and live web search. Everything else is additive after that.

How do I open the Library folder permanently in Finder?

Hold Option and click the "Go" menu in Finder's menu bar — "Library" will appear in the dropdown. Click it. You can also drag the Library folder to your Finder sidebar for permanent access.

Frequently Asked Questions

On Mac, the config file is at ~/Library/Application Support/Claude/claude_desktop_config.json. The Library folder is hidden — use Shift+Cmd+G in Finder to navigate directly to it, or hold Option and click the Go menu.

Claude Desktop is a GUI app and doesn't inherit the same PATH as your terminal on macOS. On Apple Silicon Macs, Homebrew installs to /opt/homebrew/bin/ — not in the default GUI app PATH. Fix it by using the full path /opt/homebrew/bin/npx as the command in your config.

No. Homebrew is the easiest way to install Node.js on Mac, but you can also download the Node.js installer from nodejs.org. If you use the nodejs.org installer, npx is typically at /usr/local/bin/npx on both Intel and Apple Silicon.

Yes, but it complicates the path issue. nvm puts Node in your home directory under ~/.nvm/versions/node/vX.X.X/bin/npx. Use this full path in your config. Better yet, use brew install node for a stable, globally-accessible installation that doesn't change with nvm version switches.