MCPwell

Home › Clients › Claude Desktop

Claude Desktop MCP Setup

This page is the Claude Desktop half of the setup notes. Claude Code is a different client, with a different file and different commands, on Claude Code MCP setup. The combined page with both remains at Claude.

From the Claude Desktop docs

Claude Desktop's config file locations, as published in the Connect to local MCP servers guide: macOS ~/Library/Application Support/Claude/claude_desktop_config.json, Windows %APPDATA%\Claude\claude_desktop_config.json. The same guide's filesystem example is below. The paths are the guide's placeholders. This is not a server from our directory.

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/Users/username/Desktop",
        "/Users/username/Downloads"
      ]
    }
  }
}

What this page does not call verified

The endpoints below answered initialize and tools/list on 2026-10-17 with no credential. That is Verified on MCPwell. It is not a test inside this client. Config snippets further up that name a product are either copied from that client's docs or, on a fact sheet, generated from a registry entry. A registry snippet is not a statement that we opened the client and connected.

13 other checked URLs, including Figma, GitHub, Notion, and Stripe, returned HTTP 401. They are listed on the badge page and are not in the list above. Read the security checklist before you approve a local command or a sign-in.

FAQ

Does Verified on MCPwell mean this client connected?

No. It means initialize and tools/list returned a result for that public URL on the printed date. The check does not open Claude, Cursor, or VS Code.

Where do the JSON examples come from?

From the client document linked on the page. Server URLs on a fact sheet come from that server's registry entry, not from the client document.