LinkedIn API reference
The LinkedIn API is the full LinkedIn surface on one key — Classic, Recruiter,
Sales Navigator, pages, jobs, messaging and the Magic Route. Every
operation below is live on the /linkedin DSN.
At a glance #
This reference covers LinkedIn, one part of the Top-Rated Team API. The same key also reaches the messaging channels API: a shared inbox for WhatsApp, Telegram, email, SMS, LINE, TikTok, Instagram, Facebook Messenger and website chat, and your own X account. Keys and connected accounts live in the dashboard; add an account on the dashboard.
Use it from an AI #
Every operation below is also available as a tool to any AI assistant that speaks MCP, at one address:
https://top-rated.team/linkedin/mcp/<your API key>Paste it wherever your assistant asks for an MCP server address. There is nothing to install: the key in the address is an ordinary API key, the tools are built from the catalog below, and every call it makes goes through the same key check, plan check and account ownership check your own requests do. Revoking the key ends the connection. Create one on the dashboard — “Connect your AI”.
The address contains your key, so treat it like a password: anyone who has it can use your account through it. If it gets out, revoke that key and make another.
Connecting it, client by client
Every client below takes that one address and nothing else. These are the steps the dashboard gives you after it mints a key; they are the same whichever of the agents you point the address at.
There is no sign-in step. Your key is already inside that address, so when an assistant asks how to authenticate, pick the option that means none — it is usually called No sign in, No authentication or None. Do not set up an OAuth client and do not add a request header. That one question is where almost everybody gets stuck.
ChatGPT
Open Settings and look for Connectors — depending on when you are reading this it may be called Apps & Connectors or Plugins — then for the option to add a custom connector or MCP server. On some plans it sits behind a Developer mode toggle in the same area. Paste the address as the server URL, choose the no-authentication option, and accept the warning it shows about connecting a third-party server.
Written loosely on purpose: OpenAI has moved this setting more than once and it is not offered on every plan, so an exact click-path here would be wrong within a month. If you cannot find it at all, your account does not have it — use Claude, or call the API from your own code. Their current page is help.openai.com.
Claude
- Open Settings → Customize → Connectors.
- Click + Add, then Add custom connector.
- Give it a name you will recognise — Top-Rated Team does fine — paste the address above as the remote MCP server URL, and press Continue.
- On the authentication step choose No sign in, and leave Request headers empty. Press Add.
- Back in a conversation, press + at the bottom left, choose Connectors, and switch it on.
On a Team or Enterprise plan an owner adds it once under Organization settings → Connectors, and everyone else switches it on from their own Connectors list. Anthropic's own instructions are at support.claude.com, and they are the ones to believe if this page and that page ever disagree.
Cursor
Open Cursor's settings and find MCP — it has sat under Tools, under Integrations and under Features, depending on the version. Add a server, give it a name, and paste the address as its url; leave the headers and the authentication empty. Cursor keeps it in ~/.cursor/mcp.json, where you can write it yourself instead: a mcpServers entry whose only field is url.
A server put in a project's own .cursor/mcp.json has to be switched on once in that same settings screen before the agent will use it. One in the file in your home folder is on everywhere.
VS Code
VS Code reaches MCP servers through GitHub Copilot's agent mode, so Copilot has to be switched on first. The button below hands VS Code the address and it asks once before adding it. By hand it is MCP: Add Server in the command palette, then HTTP, then the address.
That button opens VS Code Stable. Insiders takes the same address under vscode-insiders: instead, and the command palette route works on both — as does code --add-mcp in a terminal.
Grok
Open grok.com/connectors, press New connector and choose Custom. Paste the address as the MCP server URL and pick the no-authentication option. On a Business or Enterprise account an administrator adds the connector for the organization first, and then each person switches it on for themselves.
This is xAI's assistant reading your account through MCP. It is a different thing from the X API, which posts and reads on X itself and has keys of its own — if that is what you are after, connect the X channel instead.
Gemini
Open gemini.google.com/apps — its Connected apps page — and choose Add a custom app. Paste the address above as the MCP server URL, press Next and allow it. It is added in the web app and is then there in the Gemini mobile app too.
Google offers custom apps on some Google accounts and not others — a personal account, English, and the web app rather than the phone, at the time of writing — so if there is no Add a custom app on that page, your account does not have it yet. Google's own page is support.google.com, and it is the one to believe if this page and that page ever disagree. Gemini asks you to confirm anything that writes.
Claude Code
In a terminal, run claude mcp add --transport http top-rated followed by the address above in quotes. Add -s user to have it in every project instead of only this one. It is then there in Claude Code wherever you run it — the terminal, the desktop app and the editors it plugs into — and /mcp lists what it can do. Nothing to sign in to: the key is already in the address.
Codex
In a terminal, run codex mcp add top-rated --url followed by the address above in quotes. By hand it is a [mcp_servers.top-rated] block with a url line in ~/.codex/config.toml. Do not put a command line in the same block: Codex refuses a server that is described both ways.
An older Codex read url only with experimental_use_rmcp_client = true at the top of that file. Update Codex first, and add that line only if the address is still ignored afterwards.
Anything else
Any assistant that speaks MCP over HTTP takes the same single address and nothing else. There is no package to install and no configuration file to edit. If it asks for a transport, it is a remote server over HTTP, not a command to run.
Check it worked. Ask the assistant “list my connected LinkedIn accounts”. If it answers with your accounts, everything is wired up. If it says it has no such tool, the address was pasted short of the key, or the connector is added but not switched on in that conversation.
Endpoint catalog #
Every operation on the LinkedIn API, grouped by area. Open a card for its parameters, request and response.