@maheidem/linkedin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_TOKEN_STORAGE_PATH | No | Path to directory where LinkedIn OAuth tokens are stored. Defaults to ~/.linkedin-mcp/tokens. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_get_auth_urlA | Generate LinkedIn OAuth authorization URL |
| linkedin_exchange_codeB | Exchange authorization code for access token |
| linkedin_get_user_infoC | Get user information via OpenID Connect |
| linkedin_create_postC | 🚀 Create a LinkedIn post (WORKING!) |
| linkedin_create_optimized_postC | ✨ Generate and create an optimized LinkedIn post |
| linkedin_analyze_profile_from_dataC | Analyze LinkedIn profile data and provide optimization recommendations |
| linkedin_generate_optimized_contentC | Generate optimized LinkedIn content (headlines, summaries, posts) |
| linkedin_post_profile_updateC | 📢 Create a post announcing your profile updates |
| linkedin_get_user_postsA | 📖 Get user's own posts with pagination |
| linkedin_get_feedC | 📰 Get LinkedIn feed/timeline posts |
| linkedin_get_post_detailsC | 🔍 Get detailed information about a specific post |
| linkedin_get_post_commentsC | 💬 Get comments on a specific post |
| linkedin_get_user_activityB | 📊 Get user's recent activity (likes, comments, shares) |
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 13 tools
Most tools are clearly distinct, but there is some overlap between linkedin_create_post, linkedin_create_optimized_post, and linkedin_post_profile_update, which all create posts. The first two are distinguished by optimization, but the third could be confused as a different action. Overall, boundaries are mostly clear.
All tools follow a consistent linkedin_verb_noun pattern using snake_case. Verbs like create, get, generate, and post are used predictably. The naming is uniform and easy to parse, with no mixing of conventions.
With 13 tools, the server covers a substantial but focused set of LinkedIn operations—auth, profile, posts, feed, comments, and activity. This is well within the typical 3-15 range and feels complete without being bloated.
The tool surface covers the main LinkedIn use cases (auth, profile, posts, feed, comments, activity, optimization). Minor gaps exist, such as lacking update/delete operations for posts or comments, but the core workflows are supported and agents can operate without major dead ends.