Quibbly LinkedIn MCP

Current plans

Direct accepted alternatives

Iridium · job 72%GTM Otto MCP · job 80%LinkedDraft LinkedIn Content MCP Server · job 79%contentin · job 74%linkedin_mcp_2 · job 75%warm_leads · job 75%proReach LinkedIn MCP Server · job 71%Job Search Assistant · job 77%politereach · job 85%Linkedmash · job 72%Curtis · job 74%reachmcp · job 71%nudgelink · job 71%inboxapp · job 73%LinkedIn Agent MCP · job 73%LinkedIn MPC with CRM · job 76%your_echo_agent · job 79%HR Assist · job 74%capable · job 73%LinkedIn · job 70%LinkedIn OSINT CLI · job 73%Circuit · job 74%LinkedIn Manager MCP · job 75%famelab_linkedin · job 75%apex_leadshark · job 73%linkmcp · job 74%iridium · job 83%LinkedIn Post MCP · job 74%gigi · job 89%LinkedIn Ads MCP · job 79%gtm_api_linkedin_mcp · job 74%taplio_linkedin_mcp · job 83%linkedin_mcp_server · job 77%GTM Bud MCP Connector · job 71%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.

Inspect histories

Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.

This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series