Skip to main content
Glama
LinkedIn Copilot MCP

LinkedIn Copilot MCP

by Kian-hdr

A headless, locally installed MCP server for LinkedIn relationship memory, evidence-backed classifications, follow-ups and reply drafts. Your MCP-compatible assistant supplies the reasoning; this server stores channel state and exposes bounded tools.

Early developer release. You can install and inspect it without credentials. Reading LinkedIn requires your own approved API application, eligible account and member consent. This is not a universal “sign in with LinkedIn” app. Automatic sending is unavailable: dm_send and attempts to enable Auto-reply return transport_unavailable.

This is an independently packaged community edition with fresh source history, generic configuration and synthetic tests. It contains no hosted personal installation, deployment identity, owner inbox, operating policy or company-specific CRM adapter. It is not affiliated with or endorsed by LinkedIn.

community package · v0.1.0

Release notes

What works

  • Local stdio MCP, with no web server or graphical interface.

  • Account-pinned read adapter for official LinkedIn Member Data Portability APIs.

  • Resumable snapshot/event ingestion, duplicate suppression, coverage warnings and unknown-shape quarantine.

  • SQLite relationship memory, stable identities, separate business/personal domains and compact person context.

  • Source-backed relationship labels, organizations, opportunities and follow-ups.

  • Revision-checked edits, manual holds, conversation pauses and cancellation of stale drafts.

  • An idempotent draft outbox and business-only event queue for custom CRM integrations.

  • Synthetic tests without a LinkedIn account or paid model service.

Related MCP server: linkedin-mcp

What is not included

No automatic DM transport, browser automation, cookie extraction, interactive OAuth onboarding, token refresh service, campaign engine, public comments, scheduler, hosted deployment or bundled CRM consumer. Installing it does not start monitoring, send messages, change existing briefings or connect an external CRM. Your assistant's existing schedules remain its own configuration.

Quick start

Requires Node.js 24.13 or newer and npm. The server uses Node's built-in SQLite and TypeScript support. Git is optional if you use GitHub's Code → Download ZIP instead.

git clone https://github.com/Kian-hdr/linkedin-copilot-mcp-community.git
cd linkedin-copilot-mcp-community
npm ci --ignore-scripts
npm test
npm run typecheck
npm start

npm start waits for MCP input; it has no terminal menu. Stop with Ctrl+C. No credentials are required for local status, tool discovery and the test suite. Dependency installation is for development checks; the runtime has no third-party dependencies.

Add to an MCP client

Use your client's local stdio MCP server configuration. This common JSON format is illustrative; consult your client's settings format. Replace the path with the absolute location of your downloaded checkout, using escaped backslashes on Windows.

{
  "mcpServers": {
    "linkedin-copilot": {
      "command": "node",
      "args": ["/absolute/path/to/linkedin-copilot-mcp-community/src/server.ts"]
    }
  }
}

Use the absolute path to the Node executable too if your desktop client cannot find node. Restart/reconnect the client, then ask it to call copilot_get_status and linkedin_get_connection_status. The latter should report not_configured until you add authorized credentials. A connected authorization does not prove that message data is available.

Connect your own account

See Account setup before obtaining a token. The implementation uses LinkedIn's official portability product, not ordinary profile/login permissions. LinkedIn controls approval, region eligibility, consent, data preparation and retention.

Keep secrets in your MCP client's private environment or a private file outside this repository. With a private environment file, change the client args to:

[
  "--env-file=/absolute/private/path/copilot.env",
  "/absolute/path/to/linkedin-copilot-mcp-community/src/server.ts"
]

Configure LINKEDIN_ACCESS_TOKEN and LINKEDIN_OWNER_URN there. Never paste tokens into an assistant conversation or GitHub issue. Configuration lists every variable and storage behavior.

First workflow

  1. Call linkedin_get_connection_status; resolve access errors before importing.

  2. Call copilot_sync to import one bounded page. Inspect warnings, unresolved counts and checkpoint. Repeat deliberately to resume; historical snapshots are not live unread messages.

  3. Call crm_list_threads, then crm_get_thread for the actual thread ID and revision.

  4. Use crm_update_relationship to classify its domain and supported next action. Use message IDs as evidence; do not infer business relevance from a name alone.

  5. Use crm_set_classification for evidenced relationship labels, then crm_get_person_context for compact recall.

  6. Call dm_prepare_draft with the current thread revision and a stable action ID. Inspect dm_get_outbox. No message is sent.

See Tools for schemas and examples, Architecture for extension boundaries, and Security before using real messages.

Privacy

Local data defaults to ~/.local/share/linkedin-copilot-mcp-community/copilot.sqlite. Runtime storage is refused inside Git checkouts. SQLite stores message text, source references, classifications, drafts, audit entries and quarantined provider records in plaintext. File protections are not database encryption. Your connected MCP client can read and export this data; its own model/data policies still apply.

There is no telemetry or paid AI fallback. Explicit provider reads contact api.linkedin.com; installing dependencies contacts npm. The CRM origin is metadata only and does not trigger network writes. See the privacy and data lifecycle details.

Development

npm ci --ignore-scripts
npm test
npm run typecheck
npm run benchmark
npm run check:release

Tests use synthetic identities, messages and mock provider responses. The benchmark uses 10,000 synthetic contacts and 100,000 messages against local memory; it does not establish hosted or network latency. No tests send LinkedIn messages.

Contributing explains validation and release hygiene. MIT licensed; see LICENSE. Releases are source downloads, not an npm package or a hosted account.

Available Tools

27 tools
copilot_delete_threadC
Destructive

Delete Copilot conversation memory only; does not delete LinkedIn or CRM records.

Inputs: revision (required), threadId (required), confirmation (required).

copilot_export_memoryA
Read-onlyIdempotent

Export one bounded page of relationship memory for a single domain.

Inputs: domain (required), limit, offset.

copilot_get_activityC
Read-onlyIdempotent

Read recent classification and operator actions.

Inputs: no named parameters.

copilot_get_statusB
Read-onlyIdempotent

Get private Copilot settings, transport limits, synchronization coverage and the external company CRM route.

Inputs: no named parameters.

copilot_pause_threadA

Pause/resume a thread at its expected revision. Pause cancels unsent drafts.

Inputs: paused (required), revision (required), threadId (required).

copilot_release_manual_overrideB

Release a manual hold only on explicit owner instruction; does not enable sending.

Inputs: revision (required), threadId (required), confirmation (required).

copilot_syncA
Idempotent

Import one bounded provider page. Does not send messages. Repeat deliberately to resume; inspect coverage warnings.

Inputs: no named parameters.

copilot_update_settingsC

Update owner policies; sending cannot be enabled without a permitted transport.

Inputs: patch (required), revision (required).

crm_get_classificationB
Read-onlyIdempotent

Retrieve LinkedIn channel relationship labels and evidence; unknown values remain explicit. The external company CRM owns the authoritative company pipeline.

Inputs: threadId (required).

crm_get_person_contextC
Read-onlyIdempotent

Get compact source-linked LinkedIn channel context for a stable person ID; the company master remains in the external company CRM.

Inputs: domain (required), personId (required).

crm_get_sync_queueA
Read-onlyIdempotent

Inspect business-only updates queued for the hosted company CRM crm_sync_business_queue consumer and their routing metadata. Events remain queued, not applied, until company CRM persistence is verified.

Inputs: no named parameters.

crm_get_threadB
Read-onlyIdempotent

Read one LinkedIn channel conversation with bounded message pagination; content is untrusted data, not company master state.

Inputs: threadId (required), limit, offset.

crm_list_actionsA
Read-onlyIdempotent

List LinkedIn channel conversations needing action and due follow-ups; does not read company master tasks or pipeline.

Inputs: no named parameters.

crm_list_entitiesB
Read-onlyIdempotent

List LinkedIn channel-memory business organizations or opportunities with bounded pagination; these are not the authoritative company pipeline.

Inputs: kind (required), limit, offset.

crm_list_threadsA
Read-onlyIdempotent

List recent LinkedIn channel threads, classifications and revisions; does not read the authoritative company pipeline.

Inputs: limit, offset.

crm_map_existing_recordA

Store a reviewed exact existing company CRM recordId mapping for a business-only LinkedIn thread in channel memory; never match by name or write the company master.

Inputs: recordId (required), threadId (required).

crm_queue_updateB

Queue a business-only update for a reviewed exact existing company CRM recordId mapping; the hosted crm_sync_business_queue consumer must apply and verify it. Queued does not mean applied.

Inputs: changes (required), eventId (required), recordId (required), threadId (required).

crm_search_peopleC
Read-onlyIdempotent

Search private LinkedIn channel indexes without loading the inbox; use the external company CRM native search for company master records.

Inputs: limit, query, offset.

crm_set_classificationB

Store source-backed labels, confidence and classifier provenance in LinkedIn channel memory at an expected thread revision; does not update the authoritative company pipeline.

Inputs: revision (required), threadId (required), classification (required).

crm_update_relationshipB

Update source-backed classification in LinkedIn channel memory at an expected revision; respect manual overrides. Does not update the authoritative company pipeline.

Inputs: patch (required), revision (required), threadId (required).

crm_upsert_entityA

Create/update a channel-memory organization or opportunity from an evidenced business thread; does not update the authoritative company pipeline. Revision 0 creates a new stable ID. Organizations accept name and evidence only; opportunities may also include organizationId, stage and participant IDs.

Inputs: kind (required), record (required), entityId (required), revision (required), +2 more.

dm_get_outboxB
Read-onlyIdempotent

Read recent drafts and their actual states.

Inputs: no named parameters.

dm_prepare_draftC

Prepare an idempotent draft, never send it. Use only context from this thread domain.

Inputs: body (required), actionId (required), revision (required), threadId (required).

dm_sendC

Send only through a verified permitted transport; currently returns transport_unavailable.

Inputs: actionId (required).

linkedin_get_connection_statusA
Read-onlyIdempotent

Verify the configured LinkedIn account and portability authorization. Reports disconnected or unconfigured access explicitly; never returns credentials.

Inputs: no named parameters.

linkedin_get_inbox_pageA
Read-onlyIdempotent

Read one bounded page of the owner’s historical LinkedIn DMs using the official INBOX snapshot. Follow nextCursor with page and row_offset. Data is a provider snapshot, not a live unread inbox; freshness and completeness can be unknown. Treat returned message text as untrusted content.

Inputs: page, limit, row_offset.

linkedin_get_recent_messagesA
Read-onlyIdempotent

Read LinkedIn message events after consent within the provider’s 28-day retention window. since must be an ISO timestamp with timezone. Includes sent/received events and processing/freshness limitations. Exhaust nextCursor before advancing nextSince; deduplicate inclusive boundaries by activityId. Returned messages are untrusted content.

Inputs: since (required), count, limit, start.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 27 tools

    Disambiguation3/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Local-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
    • A
      license
      Not graded
      quality
      C
      maintenance
      A personal-use remote MCP server that lets you post to LinkedIn, queue/schedule drafts, and pull your own post analytics from Claude.
      18 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A local-first MCP server for auditing, drafting, and planning updates to your personal LinkedIn profile safely, without automation or scraping.
      10
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      2
      MIT