INSSIST vs Linkedin MCP Server
A side-by-side look at the INSSIST 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 INSSIST 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 INSSIST when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
INSSIST_MCP_PORT, INSSIST_MCP_HOME. - You want tools like
account_info, account_switch, antibot_export.
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 | 67/100 · Great | 67/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Freemium | Free |
| Required env vars | INSSIST_MCP_PORTINSSIST_MCP_HOME | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 31 | 3,993 |
| Directory activity | 1 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 60 | 20 |
| Full listing | View INSSIST | View Linkedin MCP Server |
Tools & capabilities
INSSIST tools 60
account_infoList connected browser instances, the account each is logged into, other available accounts, and the default target. `proTrialDaysLeft` > 0 means PRO write tools answer for that many more days.account_switchSwitch the browser profile to another logged-in account (see account_info). Later calls act as it; reloads open Instagram tabs. Switching to the active account is a no-op.antibot_exportExport the full antibot follower analysis (risk + type per follower) to a CSV file; returns the path. (Requires INSSIST PRO.)antibot_reportFollower quality analysis from the last antibot scan: totals by risk and type, plus the flagged (unreviewed high/medium-risk) followers. Empty until a scan has run. (Requires INSSIST PRO.)antibot_scanStart a follower scan scoring each follower bot/suspicious/fresh/clean. Runs in the background; poll antibot_report. Detection only — removes no one. (Requires INSSIST PRO.)comment_addPost a comment on a post. Rate-limited calls return `done: false`. (Requires INSSIST PRO.)comment_deleteDelete a comment — your own, or any on your own post. Permanent. Rate-limited calls return `done: false`. (Requires INSSIST PRO.)comment_likeLike a comment, or unlike with `unlike: true`. Rate-limited calls return `done: false`. (Requires INSSIST PRO.)comment_replyReply to a comment. Rate-limited calls return `done: false`. (Requires INSSIST PRO.)comments_listList comments on a post and their replies. (Requires INSSIST PRO.)dm_acceptAccept a pending DM message request, moving it into the inbox. (Requires INSSIST PRO.)dm_listList recent DM conversations, the last message, and whether a reply is awaited. Returns Instagram's single inbox page, which cannot be paged further. Read-only.- +48 more on the listing page
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.
INSSIST
{
"mcpServers": {
"inssist": {
"command": "npx",
"args": [
"-y",
"@inssist/mcp"
],
"env": {
"INSSIST_MCP_PORT": "YOUR_INSSIST_MCP_PORT_HERE",
"INSSIST_MCP_HOME": "YOUR_INSSIST_MCP_HOME_HERE"
}
}
}
}
Linkedin MCP Server
{
"mcpServers": {
"linkedin-mcp-server-3": {
"command": "uvx",
"args": [
"mcp-server-linkedin"
]
}
}
}
Frequently asked questions
INSSIST 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 INSSIST 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.
INSSIST is listed as freemium — a free tier with paid plans. 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 inssist and linkedin-mcp-server-3 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, INSSIST has a quality signal of 67/100 (Great) with 1 views, 0 installs and 31 GitHub stars. Linkedin MCP Server has 67/100 (Great) with 1 views, 0 installs and 3,993 GitHub stars.