Qampi vs Linkedin
A side-by-side look at the Qampi and Linkedin MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Q
QampiSocial MediaLinkedIn outreach from your agent: find prospects, add leads, run campaigns, read results.33EmergingAuth: not declaredL
LinkedinSocial MediaLinkedIn campaigns, content, leads and inbox from your AI client. Scoped, revocable keys.41FairAuth: oauth 2.0Verdict: choose Qampi for social media work; choose Linkedin for social media. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
LChoose Linkedin when
- You need dedicated capabilities in the Social Media domain.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Q Qampi | L Linkedin |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 33/100 · Emerging | 41/100 · Fair |
| Install command | Not confirmed yet | Not confirmed yet |
| Transport | — | — |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | — |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Qampi | View Linkedin |
Tools & capabilities
Qampi tools
No tool names declared yet. Check the project README from the listing page.
Linkedin tools
No tool names declared yet. Check the project README from 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.
Qampi
No confirmed install command for Qampi yet — follow the setup steps linked from its listing page rather than a guessed package name.
No confirmed install command for Linkedin yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Qampi is categorized under Social Media and uses an install path we have not confirmed yet. Linkedin belongs to Social Media and uses an install path we have not confirmed yet. Pick Qampi for social media work and Linkedin for social media.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Qampi has no declared pricing — check the project's own site. Linkedin has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 qampi and linkedin-4 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Qampi has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars. Linkedin has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.