linkedin_mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IPFOXY_HOST | No | IPFoxy proxy host | |
| IPFOXY_PORT | No | IPFoxy proxy port | |
| DATABASE_URL | Yes | PostgreSQL database connection string | |
| PROXY_PROVIDER | Yes | Proxy provider to use (e.g. oxylabs, ipfoxy) | |
| IPFOXY_PASSWORD | No | IPFoxy proxy password | |
| IPFOXY_USERNAME | No | IPFoxy proxy username | |
| OXYLABS_PASSWORD | No | Oxylabs proxy password | |
| OXYLABS_USERNAME | No | Oxylabs proxy username |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| set_cookiesA | Set LinkedIn authentication cookies (li_at) for a profile. Use this for purchased accounts. |
| loginA | Login to LinkedIn with credentials and optional 2FA. First tries stored cookies. |
| get_session_statusC | Get status of a browser session. |
| open_manual_browserA | Open and pin a persistent browser window for manual profile actions. |
| save_session_cookiesB | Save cookies from active browser session to profile storage. |
| close_sessionB | Close a browser session and save cookies. |
| read_feedC | Read LinkedIn feed posts. |
| get_profileB | Get LinkedIn profile details by URL. |
| get_companyB | Get LinkedIn company details by URL. |
| search_peopleB | Search for people on LinkedIn. |
| search_postsB | Search for LinkedIn posts by keywords. |
| get_postA | Get a LinkedIn post by URL. Returns post details including whether the current account has liked or commented on it. |
| like_postB | Like a LinkedIn post. |
| comment_postC | Comment on a LinkedIn post. |
| like_and_comment_postA | Like and comment on a LinkedIn post in one operation (single page load). |
| read_messagesC | Read LinkedIn messages/conversations. |
| send_messageC | Send a direct message to a LinkedIn connection. |
| send_inbox_messageB | Send a message using conversation-id thread routing or profile-url compose routing. |
| send_connection_requestC | Send a connection request to a LinkedIn user. |
| create_postA | Create a personal post on LinkedIn. |
| create_company_postA | Create a post on behalf of a company page (requires admin access). |
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 21 tools
Most tools map to distinct resources/actions, but send_message and send_inbox_message overlap in purpose, and like_and_comment_post partially overlaps with like_post and comment_post. Otherwise clear.
All tools use a consistent verb_noun snake_case pattern (e.g., get_profile, send_message), with only 'login' deviating slightly. Naming is predictable and clear.
At 21 tools, the server is on the heavier side but justifiable given the breadth of LinkedIn actions covered (auth, feed, search, messaging, posting). Each tool addresses a distinct workflow, so it avoids bloat.
Core LinkedIn operations are covered: auth/session management, feed reading, profile/company retrieval, people/posts search, post interaction, messaging, and connection requests. Minor gaps like connection request responses or post editing prevent a perfect score.