GTM API: LinkedIn MCP Server vs HeyReagent LinkedIn MCP
A side-by-side look at the GTM API: LinkedIn MCP Server and HeyReagent LinkedIn MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GTM API: LinkedIn MCP Server for social media work as a local process; choose HeyReagent LinkedIn MCP for social media over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose GTM API: LinkedIn MCP Server when
- You need dedicated capabilities in the Social Media domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GTM_API_KEY.
Choose HeyReagent LinkedIn MCP when
- You need dedicated capabilities in the Social Media domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Social Media | Social Media |
| Quality signal | 48/100 · Fair | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Freemium | Freemium |
| Required env vars | GTM_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 92 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View GTM API: LinkedIn MCP Server | View HeyReagent LinkedIn MCP |
Tools & capabilities
GTM API: LinkedIn MCP Server tools
No tool names declared yet. Check the project README from the listing page.
HeyReagent LinkedIn MCP 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.
GTM API: LinkedIn MCP Server
{
"mcpServers": {
"gtm-api-linkedin-mcp-server": {
"command": "npx",
"args": [
"-y",
"@gtm-api/linkedin-mcp"
],
"env": {
"GTM_API_KEY": "YOUR_GTM_API_KEY_HERE"
}
}
}
}
HeyReagent LinkedIn MCP
{
"mcpServers": {
"heyreagent-linkedin-mcp": {
"url": "https://api.heyreagent.com/mcp"
}
}
}
Frequently asked questions
GTM API: LinkedIn MCP Server is categorized under Social Media and uses a local stdio subprocess. HeyReagent LinkedIn MCP belongs to Social Media and uses a remote HTTP/SSE transport. Pick GTM API: LinkedIn MCP Server for social media work and HeyReagent LinkedIn MCP 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.
GTM API: LinkedIn MCP Server is listed as freemium — a free tier with paid plans. HeyReagent LinkedIn MCP is listed as freemium — a free tier with paid plans. 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 gtm-api-linkedin-mcp-server and heyreagent-linkedin-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GTM API: LinkedIn MCP Server has a quality signal of 48/100 (Fair) with 3 views, 0 installs and 92 GitHub stars. HeyReagent LinkedIn MCP has 51/100 (Good) with 1 views, 0 installs and 1 GitHub stars.