Linkedin vs ReplyAtlas
A side-by-side look at the Linkedin and ReplyAtlas MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
L
LinkedinSocial MediaLinkedIn campaigns, content, leads and inbox from your AI client. Scoped, revocable keys.41FairAuth: oauth 2.0Verdict: choose Linkedin for social media work; choose ReplyAtlas 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?
LChoose Linkedin when
- You need dedicated capabilities in the Social Media domain.
- Its auth model fits you: OAuth 2.0.
Choose ReplyAtlas when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
REPLYATLAS_API_KEY, REPLYATLAS_BASE_URL.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | L Linkedin | |
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 41/100 · Fair | 36/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | REPLYATLAS_API_KEYREPLYATLAS_BASE_URL |
| Verified owner |
Tools & capabilities
Linkedin tools
No tool names declared yet. Check the project README from the listing page.
ReplyAtlas 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.
No confirmed install command for Linkedin yet — follow the setup steps linked from its listing page rather than a guessed package name.
ReplyAtlas
{
"mcpServers": {
"replyatlas": {
"command": "npx",
"args": [
"-y",
"replyatlas-mcp"
],
"env": {
"REPLYATLAS_API_KEY": "YOUR_REPLYATLAS_API_KEY_HERE",
"REPLYATLAS_BASE_URL": "YOUR_REPLYATLAS_BASE_URL_HERE"
}
}
}
}
Frequently asked questions
Linkedin is categorized under Social Media and uses an install path we have not confirmed yet. ReplyAtlas belongs to Social Media and uses a local stdio subprocess. Pick Linkedin for social media work and ReplyAtlas 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 has no confirmed install command yet — follow its own setup instructions.
Linkedin has no declared pricing — check the project's own site. Auth: oauth 2.0. ReplyAtlas 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-4 and replyatlas as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Linkedin has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. ReplyAtlas has 36/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
