mcp-server-linkedin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIMEOUT | No | Timeout for a single browser page operation, in milliseconds (equivalent to the --timeout CLI option). Raise it if page operations fail with elements not found or navigation hangs. | 5000 |
| CHROME_PATH | No | Path to a Chrome/Chromium executable, for when Chrome is installed in a non-standard location (equivalent to the --chrome-path CLI option). | |
| PROXY_BYPASS | No | Comma-separated hosts to reach directly without the proxy, e.g. localhost,127.0.0.1,::1. With a proxy set, Chromium routes localhost through it too. | |
| PROXY_SERVER | No | Route browser traffic through a proxy, as scheme://host:port, with http, https, socks4 or socks5 (equivalent to the --proxy-server CLI option). Only browser traffic is routed, not the MCP transport. Set it up before --login. | |
| TOOL_TIMEOUT | No | Timeout for a whole tool call, in seconds (equivalent to the --tool-timeout CLI option). Raise it for calls that read many pages, slow networks, or a cold-start browser. | 180 |
| PROXY_PASSWORD | No | Password for proxy authentication. A wrong proxy password shows up as a timeout or failed sign-in. | |
| PROXY_USERNAME | No | Username for proxy authentication. Chromium cannot authenticate to a SOCKS proxy, so credentials require an http(s) endpoint. | |
| UV_HTTP_TIMEOUT | No | uv's HTTP timeout in seconds. On slow connections uv's default 30s timeout may be too short during the first run, so the recommended config sets this to 300. | 300 |
| LOGIN_INLINE_WAIT | No | How 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). Equivalent to the --login-inline-wait CLI option. | 25 |
| INSTALLER_TEMP_DIR | No | Existing directory to use for browser installation temporary files (equivalent to the --installer-temp-dir CLI option). | |
| LINKEDIN_MCP_CONTAINER | No | Override container runtime detection. Set LINKEDIN_MCP_CONTAINER=false to force non-container behavior (e.g. when a Linux host running a Docker daemon is misdetected), or true to force the opposite. | |
| AUTO_IMPORT_FROM_BROWSER | No | Import a session from a signed-in local browser on the first tool call that needs one, before falling back to manual login (equivalent to --auto-import / --no-auto-import; default: on). Skipped in Docker, behind a proxy, and on a non-loopback HTTP bind. | |
| FASTMCP_HTTP_ALLOWED_HOSTS | No | JSON list of extra host names the HTTP server will answer for, e.g. '["mcp.example"]'. Needed when reaching the server under a machine name or behind a reverse proxy, otherwise requests are refused with 421. | |
| EXPERIMENTAL_PERSIST_DERIVED_RUNTIME | No | In Docker, keep the derived runtime profile instead of rebuilding it from scratch on every start. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_person_profileC | 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 reading the profile, so the url field in the result is the actual profile URL (e.g. linkedin.com/in/johndoe/) rather than /in/me/. |
| get_company_profileC | 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. |
| get_job_apply_urlA | Get how a job posting takes applications, and the employer's application link. Reads the posting without clicking anything. |
| 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. A |
| 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). |
| update_headlineC | Update the headline of the LinkedIn profile at the given URL. |
| update_aboutB | Update the About section of the LinkedIn profile at the given URL. |
| create_postB | Create a new text post on LinkedIn. |
| create_post_with_imageC | Create a new LinkedIn post with an attached image. |
| delete_postC | Delete one of your LinkedIn posts. |
| react_to_postC | React to a LinkedIn post. |
| comment_on_postC | Add a comment to a LinkedIn post. |
| reply_to_commentC | Reply to a comment on a LinkedIn post. |
| get_post_reactionsC | Read the reaction summary of a LinkedIn post. |
| list_pending_invitationsB | List incoming pending connection invitations. |
| accept_invitationA | Accept a pending connection invitation by the sender's name. |
| decline_invitationA | Decline (ignore) a pending connection invitation by sender name. |
| withdraw_connection_requestC | Withdraw a previously sent connection request. |
| save_jobC | Save a LinkedIn job posting. |
| unsave_jobB | Remove a saved LinkedIn job posting from your saved list. |
| apply_to_jobB | Start the application flow for a LinkedIn job posting. |
| follow_personC | Follow a LinkedIn member. |
| unfollow_personC | Unfollow a LinkedIn member. |
| follow_companyC | Follow a LinkedIn company page. |
| unfollow_companyC | Unfollow a LinkedIn company page. |
| get_notificationsB | List LinkedIn notifications. |
| mark_notifications_readB | Mark all LinkedIn notifications as read. |
| list_settings_sectionsB | List the sections available in LinkedIn settings. |
| get_settingC | Read settings rows from a settings section page. |
| update_settingC | Update a setting in a LinkedIn settings section. |
| debug_profile_controlsC | Dump visible button/link controls on a profile page. |
| remove_skillC | Remove a skill from the profile's skills section. |
| close_sessionA | Close the current browser session and clean up resources. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 47 tools
Most tools map to a distinct resource+action (posts, jobs, invitations, messaging, profile, settings), so an agent can generally pick correctly. There is some overlap: connect_with_person claims it can also accept an incoming request, colliding with accept_invitation, and create_post vs create_post_with_image differ only by media attachment, but these are minor and descriptions clarify them.
Nearly every tool follows a clean verb_noun snake_case pattern (get_company_posts, create_post, delete_post, accept_invitation, search_jobs, update_headline). The few noun-leading outliers like close_session and debug_profile_controls still read as consistent imperative names, so the pattern is predictable throughout.
47 tools is very heavy for this surface and well past the 25+ threshold. While the LinkedIn domain is broad, the set is inflated by granular settings tools (list_settings_sections, get_setting, update_setting) and an internal debug_profile_controls that most agents would never need, suggesting the surface could be meaningfully consolidated.
Coverage is strong across posts, comments/reactions, jobs, invitations/connections, messaging, feed, and profile editing, covering the main write and read lifecycles. Minor gaps remain, such as listing your own connections/followers or retrieving your own authored posts, but these are workable limitations rather than dead ends.