Linkedin MCP Server vs Social → Context

A side-by-side look at the Linkedin MCP Server and Social → Context MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Linkedin MCP Server logoLinkedin MCP ServerSocial Media · Local subprocess (stdio)Open-source MCP server for LinkedIn. Give Claude and any MCP-compatible AI agent access to profiles, companies, jobs, and messages.67GreatAuth: otherSocial → Context logoSocial → ContextSocial Media · Remote HTTP/SSETurn a TikTok/Instagram/YouTube link into text for your AI: metadata, transcript and image OCR.55GoodAuth: not declared

Verdict: choose Linkedin MCP Server for social media work as a local process; choose Social → Context for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Linkedin MCP Server logoChoose Linkedin MCP Server when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: other.
  • You want tools like get_person_profile, search_people, connect_with_person.
Explore Linkedin MCP Server

Social → Context logoChoose Social → Context when

  • You need dedicated capabilities in the Social Media domain.
  • You prefer a remote HTTP/SSE transport.
  • You want tools like socialdl_extract, socialdl_metadata, socialdl_download.
Explore Social → Context

Feature & specification comparison

Rows where the two servers differ are marked.

SpecLinkedin MCP Server logoLinkedin MCP ServerSocial → Context logoSocial → Context
CategorySocial MediaSocial Media
Quality signal67/100 · Great55/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Remote HTTP/SSE
AuthotherNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars3,9930
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools209

Tools & capabilities

Linkedin MCP Server tools 20

  • get_person_profileGet a specific person's LinkedIn profile.
  • search_peopleSearch for people on LinkedIn.
  • connect_with_personSend a LinkedIn connection request or accept an incoming one. The tool is annotated with destructiveHint so MCP clients will prompt for user confirmation before execution.
  • get_sidebar_profilesGet profile links from sidebar recommendation sections on a LinkedIn profile page. Extracts profiles from "More profiles for you", "Explore premium profiles", and "People you may know" sidebar sections. Follows "Show all" links to return the full list from each section. Sections that redirect to linkedin.com/premium are skipped.
  • get_my_profileGet the authenticated user's own LinkedIn profile. Navigates to /in/me/ and resolves the redirect to obtain the real username before reading the profile, so the url field in the result is the actual profile URL (e.g. linkedin.com/in/johndoe/) rather than /in/me/.
  • get_company_profileGet a specific company's LinkedIn profile.
  • get_company_postsGet recent posts from a company's LinkedIn feed.
  • search_companiesSearch for companies on LinkedIn.
  • get_company_employeesList employees at a company from the LinkedIn /people/ page, including the demographics aggregate that this view exposes: where employees live, where they studied, and a function breakdown (Engineering, Sales, Operations, etc.). The demographics are unique to this tool. For filtered search by network degree (1st/2nd/3rd) or location, prefer search_people with current_company set to the company URN id. That path also returns more result pages than the /people/ tab. The optional keywords filter narrows results by name, title, or skill. company_name must be the exact LinkedIn URL slug (the path segment after /company/), not the display name. LinkedIn assigns unique slugs and the display name often does not match. For example, the AI lab Anthropic lives at /company/anthropicresearch/, not /company/anthropic/. If you are unsure of the slug, call search_companies first and pick the slug from the returned references.
  • get_job_detailsGet job details for a specific job posting on LinkedIn.
  • get_job_apply_urlGet how a job posting takes applications, and the employer's application link. Reads the posting without clicking anything.
  • search_jobsSearch for jobs on LinkedIn. Returns job_ids that can be passed to get_job_details for full info.
  • +8 more on the listing page

Social → Context tools 9

  • socialdl_extractDownload a social-media link (TikTok, Instagram reel/post/carousel, YouTube, or any direct .mp4) and return it as usable text context: metadata (author, caption, duration), the audio/video transcript, and a vision description (OCR + summary) of each image in a carousel/post. YouTube uses its existing captions when available. Use this to give Claude the content of a video or post the user pasted.
  • socialdl_metadataLightweight lookup: resolve a social-media link to its metadata (author, caption, duration, counts) and media URLs WITHOUT transcribing or running vision. Cheaper than socialdl_extract — use when the caption/context alone is enough.
  • socialdl_downloadResolve a TikTok / Instagram / YouTube link (or direct .mp4/image URL) to its DIRECT download URLs from the source CDN — every video quality, audio track and image, with quality labels. Use when the user wants to DOWNLOAD/save the media instead of transcribing it. No transcription/vision.
  • show_versionShow the current MCP platform and adapter versions.
  • report_bugReport a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
  • connectReturns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
  • toolkit_infoReturns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
  • marketplaceThe official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.
  • authenticateMCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Linkedin MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "linkedin-mcp-server-3": {
      "command": "uvx",
      "args": [
        "mcp-server-linkedin"
      ]
    }
  }
}

Social → Context

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "social-context": {
      "url": "https://api.mcp.ai/p_socialdl"
    }
  }
}

Frequently asked questions

Linkedin MCP Server is categorized under Social Media and uses a local stdio subprocess. Social → Context belongs to Social Media and uses a remote HTTP/SSE transport. Pick Linkedin MCP Server for social media work and Social → Context for social media.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Linkedin MCP Server is listed as free. Auth: other. Social → Context has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add linkedin-mcp-server-3 and social-context as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Linkedin MCP Server has a quality signal of 67/100 (Great) with 1 views, 0 installs and 3,993 GitHub stars. Social → Context has 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars.