Prototyp · Vorschau: alle Server aus der offiziellen Registry, alle 30 Minuten synchronisiert. Bewertungen und Benutzerkonten folgen in einem späteren Schritt.
PopNx MCPMCP-Server für alle, die KI nutzen · in einfachen Worten erklärt

Linked API

von Linked-APIVersion 2.3.21i★ –iComputer oder Cloud
Name in der Registryio.github.Linked-API/linkedapi-mcp

Installieren

Überblick

Beschreibung vom Entwickler (englisches Original)

Manage LinkedIn messages, connections, posts, and profile data through Linked API.

Die drei Säulen von PopNx MCP

Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

  • Verbindung: Computer oder Cloud
  • Transport: stdio, Streamable HTTP
  • Kategorie: Marketing & Social Media
  • Das musst du eintragen: LINKED_API_TOKEN, IDENTIFICATION_TOKEN, linked-api-token, identification-token

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Bevor du installierst

  • Basischecks: 3 von 3 bestanden
  • Läuft auf dem Server des Entwicklers: Was du fragst, läuft über dessen Server.
  • Kann 60 Dinge (Tools) send_message, sync_inbox, get_inbox, sync_conversation …
  • Das trägst du selbst ein: LINKED_API_TOKEN, IDENTIFICATION_TOKEN, linked-api-token, identification-token

Als geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.

Du brauchst

  • Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet
  • npmNode.js installiert (für den Befehl npx)

Welche App nutzt du?

Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.

Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.

Oder führ ihn auf deinem Computer aus

Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein

{
  "mcpServers": {
    "linkedapi": {
      "command": "npx",
      "args": [
        "-y",
        "@linkedapi/mcp"
      ],
      "env": {
        "LINKED_API_TOKEN": "your-value",
        "IDENTIFICATION_TOKEN": "your-value"
      }
    }
  }
}

Führe das in deinem Terminal aus

claude mcp add --transport http linkedapi https://mcp.linkedapi.io/mcp --header 'linked-api-token: your-value' --header 'identification-token: your-value'

Oder führ ihn auf deinem Computer aus

claude mcp add linkedapi --env LINKED_API_TOKEN=your-value --env IDENTIFICATION_TOKEN=your-value -- npx -y @linkedapi/mcp

Trag die leeren Werte ein, bevor du ihn startest.

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "mcpServers": {
    "linkedapi": {
      "url": "https://mcp.linkedapi.io/mcp",
      "headers": {
        "linked-api-token": "your-value",
        "identification-token": "your-value"
      }
    }
  }
}

Oder führ ihn auf deinem Computer aus

In Cursor öffnen

Oder kopier die Einstellungen selbst

In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen

{
  "mcpServers": {
    "linkedapi": {
      "command": "npx",
      "args": [
        "-y",
        "@linkedapi/mcp"
      ],
      "env": {
        "LINKED_API_TOKEN": "your-value",
        "IDENTIFICATION_TOKEN": "your-value"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "servers": {
    "linkedapi": {
      "type": "http",
      "url": "https://mcp.linkedapi.io/mcp",
      "headers": {
        "linked-api-token": "your-value",
        "identification-token": "your-value"
      }
    }
  }
}

Oder führ ihn auf deinem Computer aus

In VS Code öffnen

Oder kopier die Einstellungen selbst

In .vscode/mcp.json in deinem Projekt einfügen

{
  "servers": {
    "linkedapi": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@linkedapi/mcp"
      ],
      "env": {
        "LINKED_API_TOKEN": "your-value",
        "IDENTIFICATION_TOKEN": "your-value"
      }
    }
  }
}

Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.

Diese Adresse braucht einen Schlüssel in einem Header der Anfrage, und das Menü zum Hinzufügen von Connectors kann ihn nicht setzen. Nutze stattdessen Claude Code, Cursor oder VS Code.

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Werte, die du selbst einträgst

  • LINKED_API_TOKEN geheim erforderlich env
    Linked API access token from https://app.linkedapi.io.
  • IDENTIFICATION_TOKEN geheim erforderlich env
    Identification token for the LinkedIn account from https://app.linkedapi.io.
  • linked-api-token geheim erforderlich HTTP header
    Linked API access token from https://app.linkedapi.io.
  • identification-token geheim erforderlich HTTP header
    Identification token for the LinkedIn account from https://app.linkedapi.io.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 7. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen Text.

  • send_message

    Allows you to send a message to a person (st.sendMessage action). Provide either personUrl or threadId (threadId replies into an existing conversation thread and takes precedence). Optionally pass manageConversation to archive, star, or mute the conversation right after the messa

  • sync_inbox

    Recommended first step before reading messages. Enable whole-inbox monitoring so every incoming conversation can be polled with get_inbox (st.syncInbox action). Run once per account, before sending messages whose replies you want to read; only messages that arrive after it is ena

  • get_inbox

    Default way to read LinkedIn messages (standard and Sales Navigator), newest first. Without personUrl returns new messages across all conversations since inbox monitoring was enabled; requires sync_inbox (or nv_sync_inbox) once per account. With personUrl returns the whole known

  • sync_conversation

    Loads this person's earlier message history (st.syncConversation action). Call once per person; repeating it within 24 hours returns quickly. Do not call it to check for new messages – use get_inbox. After it completes, read the history with get_inbox and personUrl. Linked API ac

  • get_conversation

    Legacy. Prefer get_inbox with personUrl. Retrieve a conversation with a LinkedIn person via standard LinkedIn messaging. Returns the conversation immediately if it has already been synced. If the conversation has not been synced yet, this tool starts a syncConversation workflow a

  • sync_network

    Enable background network monitoring so connection events can be polled with get_network (st.syncNetwork action). Run once per account; only changes that happen after it is enabled are captured. Linked API actions are queued into a cloud-browser workflow and may take several minu

  • get_network

    Get connection events from the monitored network, newest first. Requires network monitoring to be enabled once with sync_network. Event types: "connectionAccepted" (a connection request you sent was accepted), "connectionAdded" (a new connection appeared in your network), "connec

  • manage_conversation

    Archive, star, or mute a conversation thread by threadId (st.manageConversation action). Provide the threadId as returned by get_inbox and the operation to perform. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immedi

  • check_connection_status

    Allows you to check the connection status between your account and another person (st.checkConnectionStatus action). Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status:

  • retrieve_connections

    allows you to retrieve your connections and perform additional person-related actions if needed (st.retrieveConnections action). Every person in the result carries urn — their permanent LinkedIn member URN (urn:li:member: ), or null when LinkedIn does not expose it. Linked API ac

  • send_connection_request

    Allows you to send a connection request to a person (st.sendConnectionRequest action). If this workflow is still running, do not retry this tool; retrying can queue duplicate connection request attempts for the same person. Linked API actions are queued into a cloud-browser workf

  • withdraw_connection_request

    Allows you to withdraw the connection request sent to a person (st.withdrawConnectionRequest action). If this workflow is still running, do not retry this tool; retrying can queue duplicate withdrawal attempts for the same person. Linked API actions are queued into a cloud-browse

  • retrieve_pending_requests

    Allows you to retrieve pending connection requests sent from your account. (st.retrievePendingRequests action). Every person in the result carries urn — their permanent LinkedIn member URN (urn:li:member: ), or null when LinkedIn does not expose it. Linked API actions are queued

  • retrieve_invitations

    Retrieves incoming connection, company-follow, and newsletter-subscription invitations received by your account (st.retrieveInvitations action). Every invitation carries urn — the permanent LinkedIn member URN (urn:li:member: ) of the person who sent it, or null when LinkedIn doe

  • accept_invitation

    Accepts an incoming connection, company-follow, or newsletter-subscription invitation (st.acceptInvitation action). Set invitationType and provide only its matching URL. If this workflow is still running, do not retry this tool; retrying can queue duplicate accept attempts. Linke

  • ignore_invitation

    Ignores an incoming connection, company-follow, or newsletter-subscription invitation (st.ignoreInvitation action). Set invitationType and provide only its matching URL. If this workflow is still running, do not retry this tool; retrying can queue duplicate ignore attempts. Linke

  • remove_connection

    Allows you to remove a person from your connections (st.removeConnection action). If this workflow is still running, do not retry this tool; retrying can queue duplicate removal attempts for the same person. Linked API actions are queued into a cloud-browser workflow and may take

  • search_companies

    Allows you to search for companies applying various filtering criteria (st.searchCompanies action). Every company in the result carries urn — its permanent LinkedIn organization URN (urn:li:organization: ), or null when LinkedIn does not expose it. Linked API actions are queued i

  • search_people

    Allows you to search people applying various filtering criteria (st.searchPeople action). Either term or customSearchUrl must be provided. Every person in the result carries urn — their permanent LinkedIn member URN (urn:li:member: ), or null when LinkedIn does not expose it. Eve

  • search_jobs

    Allows you to search jobs applying various filtering criteria (st.searchJobs action). LinkedIn serves either a classic or an AI-powered jobs search, and the two do not offer the same refinements: send filter for the classic one or preferences for the AI-powered one, never both. E

  • search_posts

    Allows you to search posts applying various filtering criteria (st.searchPosts action). Either term or customSearchUrl must be provided, and when customSearchUrl is specified, filter is ignored entirely and only the facets already encoded in the URL are applied. LinkedIn widens a

  • fetch_company

    Allows you to open a company page to retrieve its basic information (st.openCompanyPage action). Can optionally retrieve employees, posts and decision makers. The basic information carries urn — the permanent LinkedIn organization URN of the company (urn:li:organization: ); retri

  • fetch_person

    Allows you to open a person page to retrieve their basic information and perform additional person-related actions if needed. (st.openPersonPage action). Allows additional optional retrieval of experience, education, skills, languages, posts, comments and reactions. The basic inf

  • endorse_person_skill

    Endorses one skill by name on a 1st-degree connection's profile. Skill names are in the profile owner's language, regardless of your LinkedIn language. An already-endorsed skill counts as success and is never removed. Every success, including an existing endorsement, counts towar

  • endorse_person_skills

    Endorses selected skills of a 1st-degree connection, returning each selected skill's name, success and error if it failed. Skill names are in the profile owner's language. Patterns use RE2, are case-insensitive and match anywhere; anchor with ^…$ to match a whole name. Omit skill

  • fetch_post

    Open a LinkedIn post and retrieve its data, with optional comments and reactions. (st.openPost action). The author and reposter carry urn — a member URN (urn:li:member: ) for a person actor and an organization URN (urn:li:organization: ) for a company actor — and each retrieved r

  • fetch_job

    Open a LinkedIn job and retrieve its details such as company, location, salary, and description (st.openJob action). The result carries urn — the permanent LinkedIn job posting URN (urn:li:jobPosting: ) — which is null when LinkedIn does not expose the identifier. Linked API acti

  • react_to_post

    Allows you to react to a post using any available reaction type (st.reactToPost action). If this workflow is still running, do not retry this tool; retrying can queue duplicate reaction attempts. Linked API actions are queued into a cloud-browser workflow and may take several min

  • comment_on_post

    Allows you to leave a comment on a post (st.commentOnPost action); returns the comment's URN and URL. If this workflow is still running, do not retry this tool; retrying can post duplicate comments. Linked API actions are queued into a cloud-browser workflow and may take several

  • react_to_comment

    React to a comment by commentUrl (like, love, support, celebrate, insightful, funny). If this workflow is still running, do not retry this tool; retrying can queue duplicate reaction attempts. Linked API actions are queued into a cloud-browser workflow and may take several minute

  • reply_to_comment

    Reply to a comment by commentUrl; returns the reply's URN and URL. If this workflow is still running, do not retry this tool; retrying can post duplicate replies. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediat

  • create_post

    Creates a new LinkedIn post with optional mentions and media attachments (st.createPost action). Returns the URL and URN of the new post. If this workflow is still running, do not retry this tool; retrying can create duplicate posts. Linked API actions are queued into a cloud-bro

  • create_repost

    Reposts a LinkedIn post, either as is or with your own commentary (st.createRepost action). Returns the URL and URN of the repost itself, which is a post of your own account, not of the post that was reshared. Reposting the same post twice from the same account fails with already

  • retrieve_feed

    Retrieves posts from the current account's personalized LinkedIn home feed (st.retrieveFeed action). Each post's author and reposter carry urn — a member URN (urn:li:member: ) for a person actor and an organization URN (urn:li:organization: ) for a company actor, or null when Lin

  • retrieve_profile_viewers

    Retrieves the people who recently viewed the current account's LinkedIn profile (st.retrieveProfileViewers action). Each entry is either identified — carrying name, publicUrl and urn (a member URN urn:li:member: , null when LinkedIn does not expose it) — or anonymous, carrying on

  • retrieve_ssi

    Allows you to retrieve your current SSI (Social Selling Index) (st.retrieveSSI action). Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|'running', pendingR

  • retrieve_performance

    Allows you to retrieve performance analytics from your LinkedIn dashboard (st.retrievePerformance action). Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns immediately after starting the workflow with {status: 'pending'|

  • nv_send_message

    Allows you to send a message to a person in Sales Navigator (nv.sendMessage action). Provide either personUrl or threadId (threadId replies into an existing conversation thread and takes precedence). If this workflow is still running, do not retry this tool; retrying can send dup

  • nv_sync_inbox

    Recommended first step before reading Sales Navigator messages. Enable whole-inbox monitoring in Sales Navigator so every incoming conversation can be polled with get_inbox (nv.syncInbox action). Run once per account, before sending messages whose replies you want to read; only m

  • nv_sync_conversation

    Loads this person's earlier Sales Navigator message history (nv.syncConversation action). Call once per person. Do not call it to check for new messages – use get_inbox. After it completes, read the history with get_inbox and personUrl. Linked API actions are queued into a cloud-

  • nv_get_conversation

    Legacy. Prefer get_inbox with personUrl. Retrieve a conversation with a LinkedIn person via Sales Navigator messaging. Returns the conversation immediately if it has already been synced. If the conversation has not been synced yet, this tool starts an nvSyncConversation workflow

  • nv_manage_conversation

    Archive or unarchive a Sales Navigator conversation thread by threadId (nv.manageConversation action). Provide the threadId as returned by get_inbox and the operation to perform. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server

  • nv_retrieve_alerts

    Retrieve Sales Navigator lead and account alerts (root-only nv.retrieveAlerts). Returns a workflow acknowledgement; use get_workflow_result with operationName nvRetrieveAlerts. Final data is an array of alerts: id (notification URN), type (open upstream machine code), publishedAt

  • nv_retrieve_lists

    Plus-only root action nv.retrieveLists. Retrieve every owned Sales Navigator list of the requested type. Results contain id (string), name, type (lead/account), source (open upstream string), entityCount (number or null), and url. Returns a workflow acknowledgement; use get_workf

  • nv_delete_list

    Plus-only root action nv.deleteList. Delete one owned list by string listId, keeping members saved and in their other lists. Unknown, shared or already-deleted IDs return listNotFound; system lists without a Delete action return listNotDeletable. Success has no result data. Engli

  • nv_create_list

    Plus-only root action nv.createList. Create an owned lead or account list. Name is trimmed (1–75 characters). Optional description has surrounding spaces trimmed, allows up to 350 characters after trimming, and is omitted when blank. Same-type names equal after trimming, case-sen

  • nv_delete_saved_search

    Delete an owned saved search by its string ID. An absent search returns savedSearchNotFound. English interface only. Plus required. Returns a workflow acknowledgement; use get_workflow_result with operationName nvDeleteSavedSearch. Linked API actions are queued into a cloud-brows

  • nv_create_saved_search

    Save a Sales Navigator search URL matching the requested type. Returns its id, name, type and URL. English interface only. Plus required. Returns a workflow acknowledgement; use get_workflow_result with operationName nvCreateSavedSearch. Linked API actions are queued into a cloud

  • nv_retrieve_saved_searches

    Retrieve owned saved searches of the requested type. Plus required. Returns a workflow acknowledgement; use get_workflow_result with operationName nvRetrieveSavedSearches. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns

  • nv_rename_list

    Rename an owned custom list. Trimmed name: 1–75 characters, no line breaks. Same name succeeds; duplicates return listAlreadyExists and system lists return listNotRenamable. Returns the renamed list with its id, name, type and url. English interface only. Plus required. Returns a

  • nv_remove_account_from_list

    Remove an account from exactly one owned custom list, keeping it saved even after its last list. Repeating an absent membership succeeds. English interface only. Plus required. Returns a workflow acknowledgement; use get_workflow_result with operationName nvRemoveAccountFromList.

  • nv_remove_lead_from_list

    Remove a lead from exactly one owned custom list, keeping it saved and in its other lists. Repeating an absent membership succeeds. English interface only. Plus required. Returns a workflow acknowledgement; use get_workflow_result with operationName nvRemoveLeadFromList. Linked A

  • nv_retrieve_list_accounts

    Retrieve list accounts from an owned Sales Navigator list. Plus required. Returns a workflow acknowledgement; use get_workflow_result with operationName nvRetrieveListAccounts. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server re

  • nv_retrieve_list_leads

    Retrieve list leads from an owned Sales Navigator list. Plus required. Returns a workflow acknowledgement; use get_workflow_result with operationName nvRetrieveListLeads. Linked API actions are queued into a cloud-browser workflow and may take several minutes. The server returns

  • nv_unsave_account

    Plus-only root action nv.unsaveAccount. Unsave the account only; its saved leads stay saved. Repeating succeeds without changes. Sales Navigator can take up to a few minutes to reflect a change. A call that conflicts with a change you just made through Linked API may fail with un

  • nv_save_account

    Plus-only root action nv.saveAccount. Ensure an account is saved; with listId, also ensure membership in that one list, leaving other lists untouched. Without listId, leave lists unchanged. Repeating succeeds without changes. Optional string ID, never a number. Eligible: owned cu

  • nv_unsave_lead

    Plus-only root action nv.unsaveLead. Use Sales Navigator's native unsave: the lead is no longer saved and leaves every custom list the user owns. Repeating succeeds without changes. Sales Navigator can take up to a few minutes to reflect a change. A call that conflicts with a cha

  • nv_save_lead

    Plus-only root action nv.saveLead. Ensure a lead is saved; with listId, also ensure membership in that one list, leaving other lists untouched. Without listId, leave lists unchanged. Repeating succeeds without changes. Saving a lead may also save its current company in Sales Navi

  • nv_search_companies

    Allows you to search for companies in Sales Navigator applying various filtering criteria. (nv.searchCompanies action). Every company in the result carries urn — its permanent LinkedIn organization URN (urn:li:organization: ), or null when LinkedIn does not expose it. Linked API

  • nv_search_people

    Allows you to search people in Sales Navigator applying various filtering criteria. (nv.searchPeople action). Either term or customSearchUrl must be provided. Every person in the result carries urn — their permanent LinkedIn member URN (urn:li:member: ), or null when LinkedIn doe

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 7. Nov. 2026

  • ✓ Bestanden

    Entwickler passt zum Repo

    Der Registry-Name wurde mit dem GitHub-Konto Linked-API bestätigt, dem das Repo gehört

  • … Noch nicht geprüft

    Wird noch gepflegt

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • … Noch nicht geprüft

    Hat eine Lizenz

    Dieses Repo haben wir noch nicht von GitHub gelesen

  • ✓ Bestanden

    Endpunkt antwortet

    Antwort in 47 ms (HTTP 200)

  • – Nicht zutreffend

    Anmeldung mit OAuth

    Keine Anmeldung nötig

  • ✓ Bestanden

    Keine versteckten Anweisungen in Tool-Beschreibungen

    Wir haben 60 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Marketing & Social Mediai

  • Mehr Sterne als 0 % der anderen 2985 Server in dieser Kategorie
  • Neuer in der Registry veröffentlicht als 80 % der anderen 2985 Server in dieser Kategorie
  • Basischecks gleich gut wie oder besser als bei 100 % der anderen 2985 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Häufige Fragen

Ist Linked API sicher?

Er hat 3 von 3 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.

Welche Schlüssel oder Codes braucht er?

Das musst du eintragen: LINKED_API_TOKEN, IDENTIFICATION_TOKEN, linked-api-token, identification-token

Läuft er auf meinem Computer oder in der Cloud?

Beides geht: Installiere ihn auf deinem Computer oder verbinde dich mit der Cloud-Version.

Wird er noch gepflegt?

Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (2.3.21) kam vor 9 Tagen in die Registry.

Welche Apps können ihn nutzen?

Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Er verbindet sich per URL, also funktionieren auch Apps, die Remote-MCP-Server akzeptieren, zum Beispiel ChatGPT im Entwicklermodus.

Was kann ich stattdessen nutzen?

In derselben Kategorie: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

Google Analytics MCP

von surendranb

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

Läuft auf deinem Computer★ 244MITAktualisiert vor 10 Tagen
Installieren

README vom Entwickler

README öffnen

Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.

Linked API MCP server connects your LinkedIn account to AI assistants like Claude, Cursor, and VS Code. Ask them to search for leads, send messages, analyze profiles, and much more – they'll handle it through our cloud browser, safely and automatically.

Use cases

  • Sales automation assistant. Ask your AI to find leads, check their profiles, and draft personalized outreach. It can search for "software engineers at companies with 50-200 employees in San Francisco", analyze their backgrounds, and suggest connection messages that actually make sense.
  • Recruitment assistant. Let your assistant search for candidates with specific skills, review their experience, and send initial outreach. It handles the time-consuming parts while you focus on actually talking to people.
  • Conversation assistant. Your AI can read your existing LinkedIn conversations and help you respond naturally. It understands the context of your chats, suggests relevant replies, and can even send follow-up messages.
  • Market research assistant. Need competitor analysis? Your assistant can gather data about companies, their employees, and recent activities. Get insights about industry trends without spending hours on LinkedIn.

Get started

To start using Linked API MCP, spend 2 minutes reading these essential guides:

  1. Installation – set up MCP in Claude, Cursor, VS Code, or Windsurf.
  2. Available tools – explore all the LinkedIn tools your assistant can call.
  3. Usage examples – see real-world examples to get you started quickly.

Long-running actions

Linked API actions run through a cloud browser and are queued like normal automation. Many actions take several minutes, especially searches and profile fetches with optional data.

If a tool returns status, workflowId, operationName, and message, the action is still running. Do not retry the original tool because that can queue duplicate work. Call get_workflow_result with the exact workflowId and operationName until the final result is returned. By default get_workflow_result long-polls until the workflow completes or the current MCP client's request budget elapses; pass waitSeconds: 0 for an immediate single-shot snapshot.

License

This project is licensed under the MIT – see the LICENSE file for details.

PopNx fragen