LinkedIn Toolkit vs Qampi
A side-by-side look at the LinkedIn Toolkit and Qampi 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 declaredVerdict: choose LinkedIn Toolkit for social media work as a local process; choose Qampi for social media. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose LinkedIn Toolkit when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Q Qampi | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 43/100 · Fair | 33/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
LinkedIn Toolkit tools
No tool names declared yet. Check the project README from the listing page.
Qampi 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.
LinkedIn Toolkit
{
"mcpServers": {
"linkedin-toolkit": {
"command": "npx",
"args": [
"-y",
"linkedin-toolkit-mcp"
]
}
}
}
Qampi
No confirmed install command for Qampi yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
LinkedIn Toolkit is categorized under Social Media and uses a local stdio subprocess. Qampi belongs to Social Media and uses an install path we have not confirmed yet. Pick LinkedIn Toolkit for social media work and Qampi 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. Qampi has no confirmed install command yet — follow its own setup instructions.
LinkedIn Toolkit has no declared pricing — check the project's own site. Qampi 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-toolkit and qampi as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, LinkedIn Toolkit has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 11 GitHub stars. Qampi has 33/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.
