linkedin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_CLIENT_ID | Yes | LinkedIn Developer App Client ID | |
| LINKEDIN_REDIRECT_URI | No | OAuth redirect URI (default: http://localhost:3000/callback) | http://localhost:3000/callback |
| LINKEDIN_CLIENT_SECRET | Yes | LinkedIn Developer 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 | Authenticate with LinkedIn via OAuth. Opens a browser for the user to log in and grant permissions. Only needed once -- tokens persist across sessions -- unless the token has expired or |
| create_image_postA | Publish an image with text to the logged-in user's personal LinkedIn feed. Requires linkedin_login to have been run first. Provide exactly one of imagePath or imageUrl. |
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 2 tools
The two tools have completely distinct purposes: one handles authentication, the other handles posting. There is no overlap or ambiguity between them.
Naming conventions are inconsistent: 'create_image_post' follows a verb_noun pattern while 'linkedin_login' follows a noun_noun pattern. However, both names are clear and understandable.
With only 2 tools, the server feels thin for a social media platform, but it may be intentionally scoped to image posting only. The count is borderline acceptable.
The server covers the basic workflow of authentication and posting an image, but lacks operations like updating, deleting, or retrieving posts. Notable gaps exist for a complete CRUD surface.