linkedin-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_CLIENT_ID | Yes | Your LinkedIn application client ID | |
| TOKEN_STORAGE_PATH | No | Path to store OAuth tokens | ~/.linkedin-mcp-tokens.json |
| LINKEDIN_COMPANY_ID | No | Optional LinkedIn company ID for posting on company pages | |
| LINKEDIN_REDIRECT_URI | Yes | Redirect URI for OAuth callback | http://localhost:3000/auth/callback |
| LINKEDIN_CLIENT_SECRET | Yes | Your LinkedIn application 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_get_profileA | Get your LinkedIn profile information (name, email, etc.) |
| linkedin_create_postB | Create and publish a post on your LinkedIn profile |
| linkedin_get_my_postsB | Get your recent LinkedIn posts |
| linkedin_delete_postB | Delete one of your LinkedIn posts |
| linkedin_get_company_pageB | Get information about a LinkedIn company page (e.g., GD Dev Solutions) |
| linkedin_create_company_postA | Create and publish a post on behalf of a company page |
| linkedin_get_company_postsA | Get recent posts from a company page |
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 7 tools
Each tool targets a distinct resource and action: profile, user posts, and company posts are clearly separated. The verb+noun naming makes it impossible to confuse create_post with create_company_post or get_my_posts with get_company_posts.
All tools follow the linkedin_<verb>_<target> pattern with consistent verbs (get, create, delete). Singular/plural usage matches the action (create one post, get multiple posts), and prefixes remain uniform.
Seven tools is well-scoped for a LinkedIn server covering profiles, user posts, and company pages. Each tool serves a clear purpose with no redundancy.
Core workflows are covered: profile retrieval, post creation/listing/deletion for users, and company page info with post creation/listing. Missing update operations and company post deletion, but these are minor gaps for typical use.