linkedin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_MCP_CONFIG | No | Path to the configuration JSON file. Overrides config.json resolution. Relative paths are resolved from the working directory. | config.json |
| LINKEDIN_MCP_COUNTERS | No | Path to the counters.json file that persists daily action counts. Overrides the default inside the state directory. | |
| LINKEDIN_MCP_LOG_LEVEL | No | Log level: debug, info, warn, or error. All diagnostics go to stderr. | info |
| LINKEDIN_MCP_READ_ONLY | No | Set to '1' to enable read-only mode, equivalent to --read-only. Refuses write tools before any action is attempted. A malformed value (e.g. 'enabled') causes a config_invalid error. | 0 |
| LINKEDIN_MCP_STATE_DIR | No | Directory for runtime state (storageState.json, chromium-profile, counters, screenshots). Relative paths are resolved from the working directory. | ./.linkedin-mcp |
| LINKEDIN_MCP_STORAGE_STATE | No | Path to the Playwright storageState.json file that holds your LinkedIn session. Overrides the default inside the state directory. | |
| LINKEDIN_MCP_USER_DATA_DIR | No | Path to the persistent Chromium profile directory. Overrides the default inside the state directory. | |
| LINKEDIN_MCP_SCREENSHOT_DIR | No | Path to the directory where diagnostic screenshots are written. Overrides the default inside the state directory. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_loginA | Opens a visible Chromium window on LinkedIn’s login page and waits for the human to sign in themselves, including any 2FA or CAPTCHA step. This tool never types credentials and never reads the password field. When LinkedIn shows a signed-in feed, the browser session is saved to local disk (permissions 0600) and reused by every other tool. Takes no arguments. Not available under --dry-run. |
| linkedin_session_statusA | Reports whether the locally saved LinkedIn session still works, when it was saved, and when it was last verified. Loads the feed once to check; no cookie or session content is ever returned. Under --dry-run this always reports valid. Takes no arguments. |
| linkedin_create_postA | Publishes a text post to the signed-in member’s LinkedIn feed. This is a two-step tool: called without |
| linkedin_send_connection_requestA | Sends one connection invitation to a member, optionally with a note. Two-call handshake: without |
| linkedin_send_messageA | Sends one direct message, either to a 1st-degree connection (pass a profile URL or slug) or into a conversation that already exists (pass the id from its /messaging/thread// URL). Two-call handshake: without |
| linkedin_scrape_profileA | Reads a LinkedIn member profile and returns it as structured data: name, headline, about, location, connection degree, experience, education and skills. |
| linkedin_scrape_feedA | Reads the signed-in member's home feed and returns the posts as structured data: author name and headline, post text, permalink, reaction and comment counts, and a timestamp. |
| linkedin_search_jobsA | Searches LinkedIn job postings and returns them as structured data: job id, title, company, location, whether the posting supports Easy Apply, and a URL. |
| linkedin_apply_to_jobA | Submits a LinkedIn Easy Apply application. |
| linkedin_list_pending_invitesA | Lists invitations that are still awaiting a decision. |
| linkedin_list_connectionsA | Lists the signed-in member’s 1st-degree connections, most recently added first (LinkedIn’s default sort). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bansalsahab/linkdin-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server