Skip to main content
Glama
AndresMinakata

LinkedIn MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TIMEOUTNoTimeout for a single page operation in milliseconds (default: 5000).5000
CHROME_PATHNoPath to a Chrome/Chromium executable.
PROXY_BYPASSNoComma-separated list of hosts to bypass proxy, e.g. localhost,127.0.0.1,::1.
PROXY_SERVERNoProxy server URL, e.g. scheme://host:port.
TOOL_TIMEOUTNoTimeout for a whole tool call in seconds (default: 180).180
PROXY_PASSWORDNoProxy password.
PROXY_USERNAMENoProxy username.
UV_HTTP_TIMEOUTNoHTTP timeout in seconds for uvx to download dependencies. Recommended to set to 300 on slow connections.300
LOGIN_INLINE_WAITNoHow long a tool call waits for a login to finish before telling the model to retry, in seconds (default: 25, max 45; 0 = return at once).25
LINKEDIN_MCP_CONTAINERNoOverride container detection. Set to 'false' to force non-container, 'true' to force container.
AUTO_IMPORT_FROM_BROWSERNoImport a session from a signed-in local browser on the first tool call that needs one. Set to 'false' to disable. Default: on.true
FASTMCP_HTTP_ALLOWED_HOSTSNoJSON array of allowed host names for the HTTP server, e.g. '["mcp.example"]'.
EXPERIMENTAL_PERSIST_DERIVED_RUNTIMENoKeep the derived browser profile in Docker across restarts.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_person_profileA

Get a specific person's LinkedIn profile.

search_peopleC

Search for people on LinkedIn.

connect_with_personA

Send a LinkedIn connection request or accept an incoming one.

The tool is annotated with destructiveHint so MCP clients will prompt for user confirmation before execution.

get_sidebar_profilesA

Get profile links from sidebar recommendation sections on a LinkedIn profile page.

Extracts profiles from "More profiles for you", "Explore premium profiles", and "People you may know" sidebar sections. Follows "Show all" links to return the full list from each section. Sections that redirect to linkedin.com/premium are skipped.

get_my_profileA

Get the authenticated user's own LinkedIn profile.

Navigates to /in/me/ and resolves the redirect to obtain the real username before scraping, so the url field in the result is the actual profile URL (e.g. linkedin.com/in/johndoe/) rather than /in/me/.

get_company_profileA

Get a specific company's LinkedIn profile.

get_company_postsC

Get recent posts from a company's LinkedIn feed.

search_companiesB

Search for companies on LinkedIn.

get_company_employeesA

List employees at a company from the LinkedIn /people/ page, including the demographics aggregate that this view exposes: where employees live, where they studied, and a function breakdown (Engineering, Sales, Operations, etc.). The demographics are unique to this tool.

For filtered search by network degree (1st/2nd/3rd) or location, prefer search_people with current_company set to the company URN id. That path also returns more result pages than the /people/ tab.

The optional keywords filter narrows results by name, title, or skill.

company_name must be the exact LinkedIn URL slug (the path segment after /company/), not the display name. LinkedIn assigns unique slugs and the display name often does not match. For example, the AI lab Anthropic lives at /company/anthropicresearch/, not /company/anthropic/. If you are unsure of the slug, call search_companies first and pick the slug from the returned references.

get_job_detailsA

Get job details for a specific job posting on LinkedIn.

search_jobsA

Search for jobs on LinkedIn.

Returns job_ids that can be passed to get_job_details for full info.

get_saved_jobsA

List job postings saved by the authenticated LinkedIn user.

Returns job_ids that can be passed to get_job_details for full info.

get_inboxC

List recent conversations from the LinkedIn messaging inbox.

The returned inbox text and result URL come from the ordinary messaging inbox. Click-derived conversation references are collected separately after requesting the compose page, which avoided inbox auto-opening on the measured variant. A row contributes a click-derived reference only after its click is followed by an observed different thread path. The scan stops at its first unverifiable click. section_errors.inbox reports that stop or unavailable scan rows; captured inbox text and independently extracted anchors retain their normal handling. A known thread_id can bypass row attribution when calling get_conversation.

get_conversationA

Read a specific messaging conversation.

Provide either linkedin_username or thread_id to identify the conversation.

When looked up by linkedin_username, resolution searches the messaging inbox for the participant's display name and click-visits every matching row to capture its thread ID — LinkedIn's sidebar has no anchor hrefs or thread-id attributes, so this is the only available path. Each visit selects the row in the LinkedIn UI and may mark it as read. Pass thread_id directly to skip this enumeration.

Username resolution scans matching rows from a requested compose page first. Its indexable sequence ends before the first unresolved click, missing matching click target, or admitted row that fails the existing exact display-name check. An index outside that verified prefix is refused with its reason. Search is a fallback only when the inbox scan has no observed matching result and no such barrier; it never substitutes a result after a stopped or gapped inbox scan. Pass a known thread_id to bypass username/index resolution.

search_conversationsC

Search messages by keyword.

Click-derived references require an observed different thread path after each row click. The first unverifiable click stops further row clicks and is reported in section_errors.search_results. Already-read text and independently extracted anchors retain their normal handling. A result without that diagnostic does not guarantee that every conversation was enumerated.

send_messageA

Compose and send a new message to a LinkedIn user.

Profile-based targeting opens LinkedIn's compose flow. It is not a safe reply path for an existing recruiter/InMail or messaging thread: it may create a separate DM even after you inspect that thread with get_conversation or search_conversations. Those tools only read an existing thread; they do not send a reply. Until a thread-targeted send path is available, do not treat profile-based send_message as a reply.

The recipient must be directly messageable from the profile page. If LinkedIn does not expose a normal Message action, use connect_with_person first, then retry send_message only after the connection request is accepted. Recipient authorization comes from validating one recipient-specific Message action carrying the target URN, then following its browser navigation and pinning the exact final route. Visible profile links or recipient URNs in the composer are optional corroboration; any contradiction fails closed. No Voyager or other private API is used. This is a write operation when confirm_send is True.

get_feedA

Get posts from the authenticated user's LinkedIn feed.

search_postsA

Search LinkedIn posts/content globally by keyword (the "Posts" tab).

Use this to catch informal hiring posts ("we're hiring", "Buscamos ...", "estamos contratando", "join our team") that often appear before a formal job listing exists. This is global content search, distinct from get_feed (your own home feed) and get_company_posts (one company's page).

close_sessionA

Close the current browser session and clean up resources.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 19 tools

Disambiguation4/5

Most tools target clearly distinct resources or actions, and descriptions explicitly differentiate potentially overlapping ones like search_people vs get_company_employees and get_feed vs search_posts vs get_company_posts. A few read-oriented messaging tools (get_inbox, get_conversation, search_conversations) could be confused at a glance, but the descriptions disambiguate them.

Naming Consistency4/5

The set follows a largely consistent verb_noun pattern (search_people, get_person_profile, get_company_posts, send_message, close_session). connect_with_person is a minor prepositional deviation but still readable and idiomatic.

Tool Count4/5

19 tools is on the heavier side but justified by the broad LinkedIn surface spanning people, companies, jobs, messaging, and posts. Each tool maps to a real capability rather than redundant variants.

Completeness4/5

Coverage is strong across all major domains: people search/connect/profile, company search/profile/posts/employees, jobs search/details/saved, messaging read/send, and feed/post search. Gaps exist on the write side for content engagement (no create_post, comment, like/reaction, or job apply), but core workflows are supported.

Maintenance

ActivityMaintained
ResponsivenessNo issues