Skip to content
Agentmart
Submit a tool

How to add an MCP server to Claude Desktop

This guide adds MCP servers to Claude Desktop, using Playwright MCP, Figma MCP Server and Firecrawl MCP Server from the catalog. Playwright MCP runs locally, Figma MCP Server is hosted and connects by URL, and Firecrawl MCP Server runs locally and can take an API key. Local servers go in a JSON file, while the hosted one is added inside the app. The commands and values come from each listing's install data, and the paths come from Claude Desktop's own documentation.

Updated Oct 26, 2026 · Built from catalog data; how we rank and grade

Checked against Claude Desktop's documentation on Oct 26, 2026. Commands and config blocks are generated from the same install data as each listing page.

Before you start

  • Claude Desktop installed and able to start.
  • Node.js with npx for local servers that run through npx (check with node --version), or the runtime the server's listing names.
  • An API key or account only for servers that need one; hosted servers that sign in with OAuth need an account with that service.
  1. 1. Choose a server and see what it needs

    Claude Desktop keeps servers at the user level only, and it splits them between a JSON file for local servers and the app for hosted ones.

    • Playwright MCP: runs locally, no key needed.
    • Figma MCP Server: hosted, connect by URL, no key needed.
    • Firecrawl MCP Server: runs locally, can take FIRECRAWL_API_KEY.
    • Where Claude Desktop can keep a server: user only. The JSON file is for local servers; remote servers are added in the app as custom connectors.
  2. 2. Add a local server (Playwright MCP)

    Claude Desktop reads local servers from claude_desktop_config.json. On macOS the file sits under ~/Library/Application Support/Claude/claude_desktop_config.json, and the caption shows the Windows path.

    Add this to claude_desktop_config.json (macOS path shown; Windows is %APPDATA%\Claude\claude_desktop_config.json)~/Library/Application Support/Claude/claude_desktop_config.json
    {
      "mcpServers": {
        "playwright-mcp": {
          "command": "npx",
          "args": [
            "-y",
            "@playwright/mcp@0.0.82"
          ]
        }
      }
    }
  3. 3. Add a remote server (Figma MCP Server)

    Hosted servers never touch the JSON file in Claude Desktop. You add Figma MCP Server through the app's connector settings.

    • Open Customize > Connectors and choose Add custom connector.
    • Enter a name and the server URL: https://mcp.figma.com/mcp
    • Review the sign-in settings Claude detects, then add the connector.
    • Switch the connector on for a conversation from the + menu in the chat box.
    • Remote servers are not added in claude_desktop_config.json; that file is for local servers.
  4. 4. Keep API keys out of the file (Firecrawl MCP Server)

    The JSON file stores the key as a literal value under env, so the example uses a placeholder that you replace with your own key.

    Add this to claude_desktop_config.json (macOS path shown; Windows is %APPDATA%\Claude\claude_desktop_config.json)~/Library/Application Support/Claude/claude_desktop_config.json
    {
      "mcpServers": {
        "firecrawl-mcp-server": {
          "command": "npx",
          "args": [
            "-y",
            "firecrawl-mcp@3.34.1"
          ],
          "env": {
            "FIRECRAWL_API_KEY": "YOUR_FIRECRAWL_API_KEY"
          }
        }
      }
    }
    • The env object passes literal values; the docs do not describe ${VAR} expansion, so the secret sits in the config file.
    • This puts the value in claude_desktop_config.json in plain text; keep that file out of version control.
    • FIRECRAWL_API_KEY (optional): Your API key for Firecrawl.
  5. 5. Restart or reload if the server does not appear

    For Claude Desktop the notes state that a restart is required, so do not skip this step after you edit the file.

    • Required. After saving the file, completely quit Claude Desktop and start it again.
    • Local servers run with your user account's permissions, so only give them access to folders you are comfortable with.

Check that it works

After the restart, Claude Desktop shows servers through a menu in the chat box, and its logs are there for troubleshooting.

  • After the restart, open the + menu in the chat box, hover Connectors and choose Manage connectors to see the server and its tools. Logs are in ~/Library/Logs/Claude on macOS and %APPDATA%\Claude\logs on Windows.

Troubleshooting

The server does not appear in Claude
Restart Claude Desktop completely, check the JSON syntax, make sure the paths in args are absolute and valid, read the mcp log, and run the server command by hand in a terminal. Source
Tool calls fail silently
Read mcp.log and mcp-server-NAME.log in the logs folder and confirm the server runs without errors. Source
On Windows the log shows ENOENT or ${APPDATA} in a path
Add APPDATA with its expanded value to the server's env block, and make sure npm is installed globally. Source

Security notes

  • A local server runs with your user account's permissions and can do whatever you can on that machine; read what it does before you add it (MCP's security guidance says the same).
  • A remote server receives what the agent sends it. Check who runs it and what the service does with your data.
  • The env object passes literal values; the docs do not describe ${VAR} expansion, so the secret sits in the config file.
  • Agent Market does not grade security yet, so a listing page shows no security grade today; read the server's source and permissions yourself (see How we grade security).

How we grade security · Trust policy

Servers and skills in this guide

To continue, browse the listings that name Claude Desktop as a supported host, or open a guide for a single tool.

  1. 1
    Playwright MCP

    microsoftOfficial

    Playwright Tools.

    ★ 38.6KLast active Oct 22, 2026Local (stdio)Claude Code, Codex, VS Code, Cursor +2

  2. 2
    Figma MCP Server

    mcp.figma.comOfficial

    The Figma MCP server brings Figma design context directly into your AI workflow.

    ★ 2.1KLast active Oct 20, 2026Remote (HTTP)Claude Code, VS Code, Cursor, Windsurf

  3. 3
    Firecrawl MCP Server

    firecrawlOfficial

    Firecrawl, the context API for AI agents: search, scrape, interact with the web, plus paper search.

    ★ 7.7KLast active Oct 23, 2026Local (stdio), Remote (HTTP)Claude Code, VS Code, Codex, Cursor +2

Sources

Cite this page

How to add an MCP server to Claude Desktop. Agent Mart. https://agentmart.dev/guides/add-mcp-server-claude-desktop (last updated 2026-10-26)