LinkedIn MCP for VS Code (GitHub Copilot)

VS Code supports MCP servers in Copilot's agent mode, and its config differs from every other client here in two ways worth knowing up front. The top-level key is servers rather than mcpServers, and a remote entry carries an explicit type: "http". VS Code also takes a firmer line than the others on secrets: its documentation tells you not to hardcode an Authorization header and to use an input variable instead, so the key is prompted for and stored by the editor rather than written into a file you might commit.

Authentication in one line

Prompts for the key and stores it itself, so the config file stays clean.

What VS Code gets

4 LinkedIn tools plus the workspace ones. All read-only — VS Code can research LinkedIn; it cannot contact anybody through it.

search_linkedin_people get_linkedin_profile get_linkedin_posts list_linkedin_connections list_sender_accounts get_usage list_campaigns get_stats list_leads get_inbox list_tasks pause_campaign

Setup

Generate a key

Developer → Create a key (MCP) in TopClozer. Copy it — it is shown once.

Add the server

Run MCP: Add Server from the command palette (⇧⌘P / Ctrl+Shift+P) and pick Workspace or Global, or write .vscode/mcp.json by hand using the block below.

Let it prompt for the key

With the inputs block below, VS Code asks for the key the first time the server starts and stores it itself. Nothing secret goes into the file, so the file is safe to commit.

Use agent mode

Open Copilot Chat, switch to agent mode, and the TopClozer tools appear in the tool picker.

The config

Lives in .vscode/mcp.json in a workspace, or globally via the command palette. Swap the key and you are done.

.vscode/mcp.json

{
  "inputs": [
    {
      "id": "topclozer-key",
      "type": "promptString",
      "description": "TopClozer MCP key",
      "password": true
    }
  ],
  "servers": {
    "topclozer": {
      "type": "http",
      "url": "https://topclozer.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${input:topclozer-key}"
      }
    }
  }
}

Verify it works

Ask VS Code: “which TopClozer tools do you have?” — 12 should come back. To check the endpoint independently of the client, an unauthenticated GET returns the server name, version and tool list:

curl

curl -s https://topclozer.com/api/mcp

If the tool list is empty but the connection succeeded, the problem is the key rather than the URL: the MCP handshake is answered before authentication, on purpose, so a client can complete initialize and then surface a clean 401 on the first real call instead of failing with an opaque connection error.

VS Code gotchas

Specific to this client. None of these are guesses — each one has cost somebody an evening.

It is `servers`, not `mcpServers`: Every other client on this site uses mcpServers. Copy a Cursor or Claude config into VS Code unchanged and it will simply not see the server, with no useful error.
`type: "http"` is required: VS Code does not infer the transport from the presence of a url the way some clients do.
Tools live in agent mode: MCP tools are not available in ordinary Copilot chat. Switch the mode, then check the tool picker.

What it will not do

Send anything. No invite, message, reply, follow or like. Every tool reads except pause_campaign, and outbound stays behind human approval in the product.
Work without a connected account. The LinkedIn tools run through a sender account in your workspace. Without one they return a readable error saying so — accounts for agents covers how teams get one.
Run unlimited. 30 LinkedIn calls per 5 minutes per workspace. An agent retrying in a loop is the request pattern that gets accounts restricted.

FAQ

Is this GitHub Copilot or VS Code?

Both: MCP servers are consumed by Copilot's agent mode, configured through VS Code. You need a Copilot subscription for agent mode itself; TopClozer adds no requirement beyond that.

Can I commit .vscode/mcp.json?

With the inputs block above, yes — the key never appears in it. That is the reason to use an input variable rather than pasting the header directly, and it is what VS Code's own documentation recommends.

Does it work in Cursor too?

Cursor is a VS Code fork but uses its own config format and location. Use the Cursor page, not this one.

Other clients: Cursor · ChatGPT · Claude · the tool reference

LinkedIn MCP server for VS Code