LinkedIn Copilot MCP
Related Servers
Alternatives to LinkedIn Copilot MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA local-first LinkedIn workspace that turns your own documents, CVs, repositories, and exports into a verifiable claim ledger and evidence-backed canonical profile, enabling evidence import, claim verification, profile patching, post drafting, content planning, analytics, and publication approvals through MCP tools — all stored locally in SQLite with an optional human-review dashboard.9 npmMIT
- AlicenseNot gradedqualityDmaintenanceLocal-first MCP server for research on AI-assisted browsing of a user-owned professional-network account (e.g., LinkedIn), providing read-focused tools such as profile, company, search, and feed reads.MIT
- AlicenseAqualityBmaintenanceLocal-first MCP server using LinkedIn's official OAuth and REST APIs to connect a member account, read profile, and publish text posts.467 npmMIT
- AlicenseAqualityDmaintenanceA local-first MCP server for auditing, drafting, and planning updates to your personal LinkedIn profile safely, without automation or scraping.101MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for AI-native LinkedIn prospecting. It enables lead research, audience building, conversation management, and controlled outreach actions such as messaging and publishing through an OAuth-protected remote endpoint.2MIT
- AlicenseNot gradedqualityCmaintenanceA personal-use remote MCP server that lets you post to LinkedIn, queue/schedule drafts, and pull your own post analytics from Claude.9 npmMIT
TDQS
Scored across 27 tools
Most tools map to distinct resources and actions, but crm_set_classification and crm_update_relationship both update source-backed classification at an expected revision, and linkedin_get_inbox_page / linkedin_get_recent_messages / copilot_sync all read or import provider message data. Descriptions add caveats but still leave meaningful overlap requiring careful selection.
Names consistently use snake_case with domain prefixes and mostly follow verb_noun style, e.g. crm_get_thread, dm_prepare_draft, copilot_pause_thread. Minor deviations such as copilot_sync lacking an object noun and set/update used for similar classification operations keep it from a perfect score.
At 27 tools the set is above the 25+ heavy threshold, and several CRM/classification and LinkedIn read/sync tools overlap. The domain is broad, but the surface feels large enough that consolidation would materially improve usability.
The surface covers connection status, inbox/recent messages, sync, settings, threads, entities, person context, classification, drafting, outbox, send, queueing, export, and deletion. Minor gaps exist such as no single-entity get or external CRM record search, but core workflows are well represented.