Skip to main content
Glama
Sign In
Linked API MCP

Linked API MCP

by Linked-API
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

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.

Related MCP server: MCP Server for 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.

Available Tools

37 tools
admin_connect_accountAInspect

Create a connection session to connect a new LinkedIn account. Returns a sessionId and connectionLink that must be opened in a browser.

Inputs: no named parameters.

admin_disconnect_accountAInspect

Disconnect a LinkedIn account. This action is irreversible — the account must be reconnected from scratch.

Inputs: accountId (required).

admin_get_accountsAInspect

Get all connected LinkedIn accounts and pending connection sessions.

Inputs: no named parameters.

admin_get_limits_usageBInspect

Get current usage against configured rate limits for an account.

Inputs: accountId (required).

admin_get_seatsAInspect

Get active subscription seats. Each seat allows one connected LinkedIn account. Seat types: core (standard) and plus (includes Sales Navigator).

Inputs: no named parameters.

admin_get_subscription_statusAInspect

Get current subscription status, trial eligibility, and cancellation schedule.

Inputs: no named parameters.

admin_regenerate_tokenAInspect

Regenerate identification token for an account. The old token becomes invalid immediately.

Inputs: accountId (required).

admin_reset_limitsAInspect

Reset all rate limits for an account to the system defaults.

Inputs: accountId (required).

admin_set_limitsAInspect

Set rate limits for an account. Only specified limits are created or updated; other limits remain unchanged. Categories: stPersonProfileViews, stCompanyPageViews, stConnectionRequests, stMessages, stSearchQueries, stReactions, stComments, stPosts, nvPersonProfileViews, nvCompanyPageViews, nvMessages.

Inputs: accountId (required), limits (required).

admin_set_seatsAInspect

Set number of subscription seats. Returns checkout link if no active subscription, otherwise updates immediately.

Inputs: quantity (required), seatType (required), billingPeriod (required).

check_connection_statusBInspect

Allows you to check the connection status between your account and another person (st.checkConnectionStatus action).

Inputs: personUrl (required).

comment_on_postCInspect

Allows you to leave a comment on a post (st.commentOnPost action).

Inputs: postUrl (required), text (required), companyUrl.

create_postAInspect

Creates a new LinkedIn post with optional media attachments (st.createPost action).

Inputs: text (required), companyUrl, attachments.

execute_custom_workflowCInspect

Execute a custom workflow definition

Inputs: definition (required).

fetch_companyBInspect

Allows you to open a company page to retrieve its basic information (st.openCompanyPage action). Can optionally retrieve employees, posts and decision makers.

Inputs: companyUrl (required), retrieveEmployees, retrievePosts, retrieveDMs, +3 more.

fetch_personAInspect

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. ⚠️ PERFORMANCE WARNING: Only set additional retrieval flags to true if you specifically need that data. Each additional parameter significantly increases execution time: 💡 Recommendation: Start with basic info only. Only request additional data if the user explicitly asks for it or if it's essential for the current task.

Inputs: personUrl (required), retrieveExperience, retrieveEducation, retrieveSkills, +7 more.

fetch_postAInspect

Open a LinkedIn post and retrieve its data, with optional comments and reactions. (st.openPost action).

Inputs: postUrl (required), retrieveComments, retrieveReactions, commentsRetrievalConfig, +1 more.

get_api_usageBInspect

Retrieve Linked API usage statistics. Date range must not exceed 30 days.

Inputs: start (required), end (required).

get_conversationBInspect

Allows you to get a conversation with a LinkedIn person using standard LinkedIn messaging.

Inputs: personUrl (required), since.

get_workflow_resultBInspect

CONTINUE LISTENING TO BACKGROUND WORKFLOW - THIS IS NORMAL OPERATION! Background workflows are OPTIMAL BEHAVIOR for Linked API operations and keep the MCP client responsive. When a workflow runs in the background, this tool should be used with the provided workflowId and operationName parameters to continue listening for updates. The workflow continues processing in the background while you wait. This is the STANDARD way Linked API works - background processing provides optimal user experience!

Inputs: workflowId (required), operationName (required).

nv_fetch_companyAInspect

Allows you to open a company page in Sales Navigator to retrieve its basic information (nv.openCompanyPage action). Can optionally retrieve employees and decision makers.

Inputs: companyHashedUrl (required), retrieveEmployees, retrieveDMs, employeesRetrievalConfig, +1 more.

nv_fetch_personBInspect

Allows you to open a person page in Sales Navigator to retrieve their basic information (nv.openPersonPage action).

Inputs: personHashedUrl (required).

nv_get_conversationAInspect

Allows you to get a conversation with a LinkedIn person using Sales Navigator messaging.

Inputs: personUrl (required), since.

nv_search_companiesBInspect

Allows you to search for companies in Sales Navigator applying various filtering criteria. (nv.searchCompanies action).

Inputs: term, limit, filter.

nv_search_peopleBInspect

Allows you to search people in Sales Navigator applying various filtering criteria. (nv.searchPeople action).

Inputs: term, limit, filter.

nv_send_messageBInspect

Allows you to send a message to a person in Sales Navigator (nv.sendMessage action)

Inputs: personUrl (required), text (required), subject (required).

react_to_postBInspect

Allows you to react to a post using any available reaction type (st.reactToPost action).

Inputs: postUrl (required), type (required), companyUrl.

remove_connectionBInspect

Allows you to remove a person from your connections (st.removeConnection action).

Inputs: personUrl (required).

retrieve_connectionsCInspect

allows you to retrieve your connections and perform additional person-related actions if needed (st.retrieveConnections action).

Inputs: limit, since, filter.

retrieve_pending_requestsAInspect

Allows you to retrieve pending connection requests sent from your account. (st.retrievePendingRequests action).

Inputs: no named parameters.

retrieve_performanceBInspect

Allows you to retrieve performance analytics from your LinkedIn dashboard (st.retrievePerformance action).

Inputs: no named parameters.

retrieve_ssiBInspect

Allows you to retrieve your current SSI (Social Selling Index) (st.retrieveSSI action).

Inputs: no named parameters.

search_companiesCInspect

Allows you to search for companies applying various filtering criteria (st.searchCompanies action).

Inputs: term, limit, filter.

search_peopleCInspect

Allows you to search people applying various filtering criteria (st.searchPeople action).

Inputs: term, limit, filter.

send_connection_requestCInspect

Allows you to send a connection request to a person (st.sendConnectionRequest action).

Inputs: personUrl (required), note, email.

send_messageCInspect

Allows you to send a message to a person (st.sendMessage action).

Inputs: personUrl (required), text (required).

withdraw_connection_requestBInspect

Allows you to withdraw the connection request sent to a person (st.withdrawConnectionRequest action).

Inputs: personUrl (required), unfollow.

Tool Schema Changelog

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

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 37 tools

    Disambiguation5/5

    Each tool targets a distinct action or domain (admin, standard LinkedIn, Sales Navigator) with clear descriptions. Overlapping functions like fetch_person vs nv_fetch_person are disambiguated by the platform context.

    Naming Consistency5/5

    Tool names follow a consistent snake_case pattern with prefixes (admin_, nv_) to indicate scope, and plain verbs for standard LinkedIn. This pattern is predictable and aids tool selection.

    Tool Count2/5

    With 37 tools, the count exceeds the 25+ threshold, making it feel heavy. While the server aims to cover LinkedIn comprehensively, a more modular split (e.g., separate admin, standard, and Sales Navigator servers) could improve coherence.

    Completeness3/5

    Covers most core LinkedIn actions (posts, messages, connections, search, admin) but lacks explicit tools for accepting connection requests or managing groups, leaving minor gaps.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches