GTM API: LinkedIn MCP Server vs MCP Gtm Job Discovery
In-depth architectural comparison of the GTM API: LinkedIn MCP Server and MCP Gtm Job Discovery MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
GTM API: LinkedIn MCP Server
Social Media · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
MCP Gtm Job Discovery
Social Media · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose GTM API: LinkedIn MCP Server if you need specialized Social Media tools running via a local process. Choose MCP Gtm Job Discovery if your workspace requires Social Media integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose GTM API: LinkedIn MCP Server when:
You need dedicated capabilities in the Social Media domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
No explicit tool names declared in metadata yet. Check project README on main listing page.
MCP Gtm Job Discovery Tools (1)
monitor_job_postings
Give it a list of role keywords and it returns the companies currently advertising those roles, one flat row per posting, each enriched with firmographics and the company LinkedIn URL.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
GTM API: LinkedIn MCP Server is categorized under Social Media and uses a local stdio subprocess. In contrast, MCP Gtm Job Discovery belongs to Social Media using local stdio subprocess. Select GTM API: LinkedIn MCP Server when you need capabilities focused on social media and MCP Gtm Job Discovery when you require tools for social media.