LinkedIn MCP for Cursor

Cursor speaks MCP natively and takes remote servers over HTTP, which means there is nothing to install: no npm package, no local process, no mcp-remote bridge. A remote entry in Cursor's config is a URL and a headers object, so the workspace key travels in an ordinary Authorization header exactly as the API expects it. That makes Cursor the least fiddly of the four clients here.

Authentication in one line

Takes an Authorization header, which is the clean path.

What Cursor gets

43 LinkedIn tools plus the workspace ones. Only the 15 propose_* tools, which queue an action for a person to approve, and connect_linkedin_account, add_do_not_contact, pause_campaign and install_product, which change only this workspace change anything — Cursor can research LinkedIn and propose who to contact and what to say; a person approves before anything is sent.

search_linkedin_people get_linkedin_profile get_linkedin_posts list_linkedin_connections get_account_seat get_my_profile get_profile_viewers get_ssi get_profile_sections check_reachability get_company get_post list_post_comments list_post_reactions get_profile_activity list_sent_invitations list_received_invitations list_followers list_following list_conversations get_conversation list_recent_messages search_linkedin_companies search_linkedin_posts search_linkedin_jobs search_linkedin_url find_company_people lookup_search_filter list_sender_accounts connect_linkedin_account propose_connection_request propose_message propose_profile_visit propose_inmail propose_reply propose_withdraw_invitation propose_accept_invitation propose_ignore_invitation propose_follow propose_unfollow propose_endorsement propose_post_reaction propose_comment propose_post propose_message_reaction get_approval list_approvals list_do_not_contact add_do_not_contact get_usage list_campaigns get_stats list_leads get_inbox list_tasks pause_campaign search_capabilities search_products get_product install_product list_installations list_projects get_project_context check_credits get_platform_usage

Setup

Generate a key

In TopClozer, Developer → Create a key (MCP). It is shown once and stored only as a hash, so copy it now.

Create the config

Put the block below in ~/.cursor/mcp.json to have the tools everywhere, or in .cursor/mcp.json in a project to scope them to it. Cursor also has a UI for this under Settings → Tools & MCP.

Reload

Cursor picks the file up on reload. The server should appear in Tools & MCP with its tool list expanded.

Ask for something

"Find VP Engineering people at fintech companies in Berlin and tell me which three are worth approaching." The agent will call search_linkedin_people and then read the profiles.

The config

Lives in ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one. Swap the key and you are done.

~/.cursor/mcp.json

{
  "mcpServers": {
    "topclozer": {
      "url": "https://topclozer.com/api/mcp",
      "headers": {
        "Authorization": "Bearer tcz_live_YOUR_KEY"
      }
    }
  }
}

Verify it works

Ask Cursor: “which TopClozer tools do you have?” — 65 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.

Cursor gotchas

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

A project config does not inherit the global one: If you keep .cursor/mcp.json in a repo, that file is what Cursor reads there. A server defined only in ~/.cursor/mcp.json will not appear.
The key is in a file in your home directory: Which is fine until the project config ends up in git. Put .cursor/mcp.json in .gitignore, or keep the server global and out of the repo entirely.
An empty tool list means auth, not transport: The handshake is answered before authentication, so a bad key connects cleanly and then fails on the first call. Check the header before you check the URL.

What it will not do

Send anything by itself. No invite, message, comment, follow or like goes out because an agent asked: it lands in Approvals, a person decides, and it then runs under the account's Smart Limits.
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

Do I need to install anything?

No. TopClozer is a remote HTTP server, so Cursor talks to it directly. You do not need npx, mcp-remote, Docker or a local process — that requirement belongs to the open-source LinkedIn servers that run a browser on your machine.

Can Cursor send LinkedIn messages through this?

Not by itself. Cursor can search, read profiles, posts and the inbox, and propose an invite, a message or a reply — each proposal waits in Approvals until a person approves it.

Which LinkedIn account does it use?

A sender account connected to your TopClozer workspace, not your personal profile. Call list_sender_accounts to see which identities are available and which one is used by default.

Other clients: ChatGPT · VS Code · Claude · the tool reference

LinkedIn MCP server for Cursor