LinkedIn Toolkit MCP Server

What the code does

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

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

        writeFileSync(resolve(options.csv), toCsv(profiles, PROFILE_COLUMNS), 'utf8');

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.

    exec(code, namespace)  # noqa: S102 — the source is generated from the contract

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 linkedin-toolkit -- npx -y linkedin-toolkit-mcp

{
  "mcpServers": {
    "linkedin-toolkit": {
      "command": "npx",
      "args": [
        "-y",
        "linkedin-toolkit-mcp"
      ]
    }
  }
}

[mcp_servers.linkedin-toolkit]
command = "npx"
args = ["-y", "linkedin-toolkit-mcp"]

{
  "mcpServers": {
    "linkedin-toolkit": {
      "command": "npx",
      "args": [
        "-y",
        "linkedin-toolkit-mcp"
      ]
    }
  }
}

{
  "servers": {
    "linkedin-toolkit": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "linkedin-toolkit-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: LINKEDIN_TOOLKIT_HOME (Directory for the local SQLite mirror and config. Defaults to ~/.linkedin-toolkit).