LeadSync MCP Server

What the code does

We read the source, 3 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  const r = spawnSync(inv.file, inv.args, { encoding: 'utf8', shell: inv.shell, windowsHide: true })

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add mcp -- npx -y @leadsync/mcp

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@leadsync/mcp"
      ]
    }
  }
}

[mcp_servers.mcp]
command = "npx"
args = ["-y", "@leadsync/mcp"]

{
  "mcpServers": {
    "mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@leadsync/mcp"
      ]
    }
  }
}

{
  "servers": {
    "mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@leadsync/mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: LEADSYNC_API_KEY (LeadSync API key (Account, Settings, API keys). Optional if you ran npx @leadsync/skills login, which saves it to ~/.leadsync/.env).