Social Signal vs Linkedin MCP Server
A side-by-side look at the Social Signal and Linkedin MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Social Signal for social media work as a local process; choose Linkedin MCP Server for social media as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Social Signal when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You want tools like
social_topic_volume, social_account_activity.
Choose 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 59/100 · Good | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 4,008 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 2 | 20 |
| Full listing | View Social Signal | View Linkedin MCP Server |
Tools & capabilities
Social Signal tools 2
social_topic_volumeSOCIAL MEDIA VOLUME as a TIME SERIES: how many posts mention a topic, bucketed by day or hour, so you can see the POST VOLUME TREND and whether SOCIAL CHATTER ABOUT A TOPIC is rising or fading. Answers "how much is X being discussed", "BUZZ OVER TIME for X", "is attention on X growing this week". Returns a per-bucket count broken out by network, running totals, engagement sums where the source exposes them, and an explicit window_actually_covered block. A bucket is a number only where that network was truly measured; where reach ran out it is null, so a measured zero is always distinguishable from an unobserved gap. Coverage is Bluesky, Mastodon, Reddit and Hacker News; X/Twitter is excluded (paid API), so results are a directional proxy over a partial slice of social media rather than total social volume. Examples: topic "bitcoin", days 7, bucket "day" for a week-long attention curve; topic "openai", days 2, bucket "hour", networks ["bluesky","hackernews"] for an intraday spike check.social_account_activityPOSTING CADENCE for one social media account as a TIME SERIES: posts per day over a window, plus average engagement per post and the timestamp of the most recent post. Answers "how often does this account post", "has this account gone quiet", "what is their POST VOLUME TREND", "how active is @someone on social media". The network is inferred from the handle shape (a dotted handle is Bluesky, "@user@instance.tld" is Mastodon, "u/name" is Reddit); when the shape is ambiguous the response lists every network tried in networks_tried. Days with a null count were outside the reach of the feed and stay distinguishable from days with a measured zero. Coverage is Bluesky, Mastodon, Reddit and Hacker News; X/Twitter is excluded (paid API), so results are a directional proxy over a partial slice of social media rather than total social volume. Examples: handle "bsky.app", days 30 for a month of posting cadence; handle "@Mastodon@mastodon.social", days 90 for a long-run activity check.
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
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.
Social Signal
{
"mcpServers": {
"social-signal": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-social-signal"
]
}
}
}
Linkedin MCP Server
{
"mcpServers": {
"linkedin-mcp-server-3": {
"command": "uvx",
"args": [
"mcp-server-linkedin"
]
}
}
}
Frequently asked questions
Social Signal is categorized under Social Media and uses a local stdio subprocess. Linkedin MCP Server belongs to Social Media and uses a local stdio subprocess. Pick Social Signal for social media work and Linkedin MCP Server 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.
Social Signal has no declared pricing — check the project's own site. Linkedin MCP Server is listed as free. Auth: other. 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 social-signal and linkedin-mcp-server-3 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Social Signal has a quality signal of 59/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Linkedin MCP Server has 67/100 (Great) with 1 views, 0 installs and 4,008 GitHub stars.