Skip to main content
Installation

How Do I Install An MCP Server In Claude Desktop?

Config paths, example JSON, restart behavior, and the most common macOS path pitfall.

Short answer

Claude Desktop reads MCP server definitions from a local JSON config file. The current MCP quickstart documents the config paths on macOS and Windows and uses the same mcpServers structure that other clients use.

The most common failure is not the JSON itself. It is a bad executable path, especially on macOS setups where the GUI app does not inherit the same shell environment as your terminal.

Recommended path

  1. 01

    Open the Claude Desktop config file

    On macOS the file is ~/Library/Application Support/Claude/claude_desktop_config.json. On Windows it is %APPDATA%\Claude\claude_desktop_config.json.

  2. 02

    Add the MCP server definition

    Use the mcpServers object with a command and args, then save the file.

  3. 03

    Restart Claude Desktop and inspect the tool list

    If the tools do not appear, check the executable path first, not just the JSON syntax.

Minimal config example

{
  "mcpServers": {
    "aescut": {
      "command": "npx",
      "args": ["-y", "@aeptus/aescut", "--skip-install"]
    }
  }
}

Why npx fails for some users

The official MCP quickstart explicitly warns about environments that use NVM or other shell-specific Node setups. A desktop app can see a different PATH than your terminal, so npx works in Terminal but fails in Claude Desktop.

When that happens, use the absolute path to the executable, or install Node in a way the desktop app can resolve consistently.

When Claude Desktop is the right place to install

Claude Desktop is a good fit for personal, cross-project tools. If the MCP server should travel with one repository and one team, Claude Code or another project-scoped client is often a better fit because the configuration lives closer to the codebase.

Sources and further reading