linkedin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host to bind to in HTTP mode | 127.0.0.1 |
| PORT | No | Port to listen on in HTTP mode | 3000 |
| MCP_AUTH_TOKEN | No | Secret for the HTTP endpoint (used in HTTP mode) | |
| LINKEDIN_SCOPES | No | Scopes requested by the `auth` command | openid profile email w_member_social |
| LINKEDIN_CLIENT_ID | No | Client ID used by the `auth` command if not prompted | |
| LINKEDIN_TOKEN_FILE | No | Path to the token storage file | ~/.config/linkedin-mcp/token.json |
| LINKEDIN_API_VERSION | No | LinkedIn-Version header (YYYYMM) | 202608 |
| LINKEDIN_ACCESS_TOKEN | No | Access token; takes precedence over the token file (useful for hosting) | |
| LINKEDIN_REDIRECT_URI | No | Redirect URI must match the LinkedIn app's Auth settings | http://localhost:8787/callback |
| LINKEDIN_CLIENT_SECRET | No | Client Secret used by the `auth` command if not prompted |
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_get_profileA | Returns the authenticated member's basic profile (name, email, picture) and their person URN. Use this to verify the connection. |
| linkedin_create_postA | Publishes a post on LinkedIn as the authenticated member (or an organization). Supports plain text, a link preview (article) or a single image. #hashtags in the text become real hashtags; all other special characters are escaped automatically. This publishes publicly and immediately — confirm the final text with the user before calling. |
| linkedin_delete_postA | Deletes a post you (or your organization) authored. Irreversible — confirm with the user first. |
| linkedin_get_postA | Fetches a single post by URN. Reading member posts requires the r_member_social permission (restricted); organization posts require r_organization_social. |
| linkedin_list_postsA | Lists recent posts by an author (default: yourself). Requires r_member_social (restricted) for members or r_organization_social for organizations. |
| linkedin_list_organizationsA | Lists LinkedIn company pages the authenticated member administers (Community Management API, scope rw_organization_admin). |
| linkedin_comment_on_postA | Adds a comment to a post as yourself or an organization. Publishes immediately — confirm with the user first. |
| linkedin_react_to_postA | Adds a reaction (like, celebrate, support, …) to a post as yourself or an organization. |
| linkedin_get_post_statsA | Returns the like and comment summary of a post (socialActions). |
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 9 tools
Each tool targets a distinct resource-action pair: profile, post CRUD, organization listing, commenting, reacting, and stats. There is no overlap between getting a single post vs. listing posts, and comment/react/stats are clearly separate operations. The descriptions further clarify any potential boundary (e.g., get_post vs. list_posts).
All tools follow the same linkedin_<verb>_<noun> pattern with snake_case throughout. Each name starts with the domain prefix and then uses a clear action verb (get, create, delete, list, comment, react). Even the phrasal verbs like comment_on_post and react_to_post are internally consistent.
The 9 tools are well-scoped for a LinkedIn social API surface. The count covers profile verification, post management, engagement actions, and stats without being bloated. It sits comfortably in the ideal 3–15 range.
The tool set covers the core social workflow: create/read/delete posts, comment, react, and fetch stats. Missing operations like updating a post or listing individual comments/reactions are minor since LinkedIn edits are limited and stats provide summaries. No major dead ends exist for the stated purpose.