contentin

Current plans

Direct accepted alternatives

mcp_server_linkedin · job 73%Niche · job 73%omnflow · job 71%postly_social_publisher · job 78%proReach LinkedIn MCP Server · job 80%FeedSquad · job 73%LinkedIn · job 71%iridium · job 73%salestouch · job 75%veezee_veezee · job 76%gtm_api_linkedin_mcp · job 80%ladderflow · job 76%bulkpublish_mcp_server · job 71%LinkedIn MCP Server · job 80%Iridium · job 78%zooq · job 77%yadulink · job 72%cclarity_linkedin_mcp · job 77%linked_api_mcp · job 75%schedpilot · job 71%linkedin_mcp · job 76%LinkedDraft LinkedIn Content MCP Server · job 82%linkmcp · job 78%apex_leadshark · job 77%Linkedmash · job 79%antwork · job 79%vibemarketing · job 74%LinkedIn Publish + Schedule Posts (Much More Too!) · job 80%LinkedIn MPC with CRM · job 77%linkedin_ops · 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