linkedin-local-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_auth_statusB | Check the local token and identify the authenticated LinkedIn member. |
| linkedin_publish_postA | Publish a text post. Set confirmed=true only after explicit user approval. |
| linkedin_list_commentsB | Read comment threads for a LinkedIn post, subject to granted read permissions. |
| linkedin_reply_to_commentA | Reply to a specific comment. Requires explicit user approval. |
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 4 tools
Each tool targets a clearly distinct concern: authentication, publishing, reading comments, and replying to comments. There is no meaningful overlap between read and write operations or between posts and comments.
Most tools follow a consistent linkedin_verb_noun pattern (publish_post, list_comments, reply_to_comment). linkedin_auth_status is a slight deviation because it uses a noun phrase rather than an explicit verb like get or check.
Four tools is a compact but reasonable set for a focused LinkedIn posting and comment engagement workflow. It is not overly thin given the apparent scope, though it stays at the smaller end of the typical range.
The core workflow of checking auth, publishing a post, viewing comments, and replying is covered without obvious dead ends. However, there is no way to fetch a user's own posts, update/delete a post, or delete a comment, which are minor gaps for a fuller LinkedIn integration.