linkedin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_SCOPES | No | Space-separated override of the default member scopes | |
| LINKEDIN_VERSION | No | Posts API version header, YYYYMM. Defaults to 202609 | 202609 |
| LINKEDIN_CLIENT_ID | Yes | App client id | |
| LINKEDIN_TOKEN_PATH | No | Session file path. Defaults to ~/.config/echohello/linkedin-mcp/tokens.json | ~/.config/echohello/linkedin-mcp/tokens.json |
| LINKEDIN_REDIRECT_URI | No | OAuth redirect URI. Defaults to http://127.0.0.1:53682/callback | http://127.0.0.1:53682/callback |
| LINKEDIN_CLIENT_SECRET | Yes | App client secret |
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 | Start LinkedIn member sign-in. Returns a URL the member must open and approve. When the redirect URI is loopback, a local listener waits for the callback. Tokens are never returned. |
| linkedin_finish_loginA | Finish member sign-in. Waits for the loopback callback, or exchanges a pasted redirect URL. Saves the session locally. |
| linkedin_statusB | Show whether a member session is stored. Does not return tokens. |
| linkedin_logoutA | Delete the stored member session. |
| linkedin_profileA | Read the signed-in member's OpenID profile (name, email, picture, member id). |
| linkedin_create_postA | Publish a text post as the signed-in member. Requires the Share on LinkedIn product (w_member_social). |
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 6 tools
Each tool has a distinct function: the login/finish_login pair forms a clear two-step flow, and status, logout, profile, and create_post are all sharply separated. The only mild risk is confusion between linkedin_login and linkedin_finish_login, but descriptions disambiguate the sequence.
All six tools use a consistent linkedin_ prefix with snake_case verb/noun naming (linkedin_login, linkedin_finish_login, linkedin_status, etc.). The convention is predictable throughout.
Six tools is well-scoped for an auth-plus-basic-actions server, with each tool earning its place across the session lifecycle and core member operations.
The auth lifecycle (login, finish, status, logout) plus profile read and post creation covers the core member flow. Minor gaps exist—no post delete/list, no profile update—but the surface is coherent for its apparent scope.