GTM API: LinkedIn MCP… vs Ship On Friday | AllMCPs
Side-by-Side Model Context Protocol Comparison
GTM API: LinkedIn MCP Server vs Ship On Friday
In-depth architectural comparison of the GTM API: LinkedIn MCP Server and Ship On Friday 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
Ship On Friday
Social Media · Local stdio
Quality: 43/100 (Fair) | 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 Ship On Friday 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.
Ship On Friday Tools (1)
ship_on_friday_check
Check whether you should ship on Friday. The answer is always no. Returns a rotating reason, risk level (always catastrophic), suggested day, and on-call sympathy score.
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, Ship On Friday belongs to Social Media using local stdio subprocess. Select GTM API: LinkedIn MCP Server when you need capabilities focused on social media and Ship On Friday when you require tools for social media.