mcpbeat Sign in

Linkedin MCP Server

answering

Linkedin is answering right now. Last checked 14 min ago. It exposes 12 tools.

LinkedIn: The LinkedIn Data API offers access to detailed information on individuals, companies.

Uptime history 58 days of history · worst day 93%
58 days agonow
100.0%
Uptime 24h
91 of 91 checks
12
Tools
read from the server
308 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 35

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 4 September 2026. No other catalogue keeps this.

4 Sep 12 tools appeared get_company, get_company_companyId_employees, get_company_companyId_jobs and 9 more
4 Sep 12 tool descriptions were rewritten get_company, get_company_companyId_employees, get_company_companyId_jobs and 9 more
4 Sep 11 tools disappeared get_v1_company_details, get_v1_person_details, get_v1_post_details and 8 more

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add linkedin --transport http https://mcp.jojapi.com/linkedin
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "linkedin": {
      "url": "https://mcp.jojapi.com/linkedin"
    }
  }
}
~/.codex/config.toml
[mcp_servers.linkedin]
url = "https://mcp.jojapi.com/linkedin"
.cursor/mcp.json
{
  "mcpServers": {
    "linkedin": {
      "url": "https://mcp.jojapi.com/linkedin"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "linkedin": {
      "url": "https://mcp.jojapi.com/linkedin"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

company
get_company
Provide either `slug` or `companyId`. If neither is given, the request fails with `400 VALIDATION_ERROR`. Take the `slug` from a `/company/search` result rather than guessing it from the company name — a company's slug often differs from its display name. Group: Companies. Billing per call: 1 Credits.
get_company_companyId_employees
Returns people who list this company as their employer. Results may include private or out-of-network profiles, which appear with the name `LinkedIn Member`. Full profiles cannot be retrieved for those records, so check the name before calling `/person-profile` with the returned `memberId`. Group: Companies. Billing per call: 1 Credits.
get_company_companyId_jobs
Returns an empty list if the company has no open postings. Use the `jobId` from a result with `/jobs/detail/{jobId}`. Group: Companies. Billing per call: 1 Credits.
get_company_posts
Returns the same post structure as `/person-profile/posts`. This endpoint is addressed by `slug` only. Group: Companies. Billing per call: 1 Credits.
get_company_search
Use the `slug` or `companyId` from a result to fetch full details from `/company`, the employee list, or the job list. Group: Companies. Billing per call: 1 Credits.
jobs
get_jobs_detail_jobId
Returns the full description for a posting. Several fields are only present on some postings; the company name is most reliably taken from the search result that provided the `jobId`. Group: Jobs. Billing per call: 1 Credits.
get_jobs_search
Use the `jobId` from a result with `/jobs/detail/{jobId}`. Group: Jobs. Billing per call: 1 Credits.
person
get_person_profile
Returns a full profile including experience, education, and skills. Obtain a `memberId` from `/people/search` or `/company/{companyId}/employees`. Note that profiles which are private or outside your network cannot be retrieved; these appear in listings with the name `LinkedIn Member`. Group: Person. Billing per call: 1 Credits.
get_person_profile_posts
Returns an empty list if the person has not posted. Group: Person. Billing per call: 1 Credits.
posts
get_posts_postId_comments
Returns an empty list when the post has no comments. Group: Posts. Billing per call: 1 Credits.
get_posts_postId_reactions
Returns an empty list when the post has no reactions. Group: Posts. Billing per call: 1 Credits.
people
get_people_search
All filters are optional and can be combined. Returns the same person structure as `/company/{companyId}/employees`. Returns an empty list when nothing matches. Group: Person. Billing per call: 1 Credits.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

get_v1_company_details
removed 4 Sep 2026
get_v1_person_details
removed 4 Sep 2026
get_v1_post_details
removed 4 Sep 2026
get_v1_pulse_details
removed 4 Sep 2026
get_v1_search_peoples
removed 4 Sep 2026
get_v2_autocomplete
removed 4 Sep 2026
get_v2_profile_contact_info
removed 4 Sep 2026
get_v2_profile_details
removed 4 Sep 2026
get_v2_profile_header_details
removed 4 Sep 2026
get_v2_search_all
removed 4 Sep 2026
get_v2_search_people
removed 4 Sep 2026

Endpoints

URLTransportStateLatencyChecked
https://mcp.jojapi.com/linkedin streamable-http answering 182 ms 14 min ago

Alternatives to Linkedin

same job, measured the same way
Reddit
by jojapi

Reddit: Reddit Data API offers streamlined access to Reddit’s public data, like posts, comments.

31 tools answering
EnvoAPI
by envoapi

People, company, job and LinkedIn post data, plus email finding and verification.

answering
DataForB2B
by dataforb2b

Search and enrich B2B people & companies — 70+ filters (funding, linkedin, industry, country, ...).

answering
Jobs Data
by benthepythondev00

Remote job boards, LinkedIn jobs, company ATS pages and Upwork jobs as tools. Runs on Apify.

answering
Jobs Search Multi
by dataleadspro

Search job postings across Indeed, LinkedIn, and more from one request - titles, companies

4 tools answering
Periodix Actions
by periodix

Search LinkedIn & Sales Navigator. Get structured people, companies, posts, jobs data. 4.9/5 on G2.

answering
CrustAPI Google + LinkedIn Data
by crustapi

Live Google + public LinkedIn data: search, maps, profiles, companies, jobs. Pay only for results.

43 installs/wk local only
Linkedin Data
by superagnt

LinkedIn data for AI agents: profiles, companies, jobs, posts, search. Sales research, recruiting.

answering

Linkedin — questions

Answers built from our own checks of this server.

What can Linkedin do?
It exposes 12 tools, read directly from the server on our last check. Among them: get_company, get_company_companyId_employees, get_company_companyId_jobs, get_company_posts, get_company_search, get_jobs_detail_jobId and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Linkedin mostly used for?
Its tools cluster around company, person and posts. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Linkedin working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 308 ms. The bar chart above shows every period we have measured.
Did Linkedin ever remove tools?
Yes. get_v1_company_details, get_v1_person_details, get_v1_post_details, get_v1_pulse_details and 7 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Linkedin?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Linkedin need an API key?
No. Linkedin completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Linkedin?
It answers our handshake in 308 ms on average, which is faster than 43% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.