LinkedIn Custom MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_CLIENT_ID | Yes | Your LinkedIn Developer App Client ID | |
| LINKEDIN_REDIRECT_URI | Yes | The Authorized redirect URL configured in your LinkedIn App | http://localhost:8000 |
| LINKEDIN_CLIENT_SECRET | Yes | Your 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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {
"tasks": {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
}
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_get_oauth_urlA | Generate the LinkedIn OAuth 2.0 authorization URL for browser login. |
| linkedin_exchange_codeB | Exchange the browser-provided authorization code for a persistent access token. |
| linkedin_get_my_profileA | Fetch the authenticated user's profile information (Name, Email, Picture). |
| linkedin_get_member_profileA | Fetch a specific member's profile by their URN (e.g., 'urn:li:person:123'). |
| linkedin_create_postA | Create a new text-based update on the user LinkedIn feed. Args: text: The content of the post. visibility: 'PUBLIC' or 'CONNECTIONS'. |
| linkedin_create_image_postB | Create a post with an image. Args: text: Post caption. image_source: Local file path or public URL of the image. visibility: 'PUBLIC' or 'CONNECTIONS'. |
| linkedin_update_postA | Update a post's text. ⚠️ Warning: This deletes the old post and creates a new one with a new ID, as LinkedIn does not support editing published posts via API. |
| linkedin_delete_postA | Delete a LinkedIn post by its URN (e.g., 'urn:li:share:123'). |
| linkedin_get_recent_postsA | List the user's recent posts (Requires 'r_member_social' permission). |
| linkedin_create_commentB | Create a comment on a LinkedIn share, article, or video. Args: object_urn: The URN of the content to comment on (e.g., 'urn:li:share:123'). text: The text of the comment. |
| linkedin_get_post_commentsB | Get comments for a specific post/share. |
| linkedin_delete_commentC | Delete a specific comment. Args: comment_urn: The URN of the comment to delete. object_urn: The URN of the parent post/object. |
| linkedin_get_company_profileA | Fetch a company's profile information by its URN (e.g., 'urn:li:organization:123'). |
| linkedin_search_companiesB | Search for companies on LinkedIn by keywords. |
| linkedin_search_jobsB | Search for jobs on LinkedIn by keywords and optional location. |
| linkedin_get_job_detailsB | Fetch details for a specific job posting by its URN. |
| linkedin_search_peopleC | Search for people on LinkedIn by keywords. |
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 17 tools
Every tool has a clearly distinct purpose targeting specific LinkedIn resources and actions. For example, linkedin_create_post, linkedin_create_image_post, and linkedin_create_comment handle different content types, while search tools (companies, jobs, people) and get tools (profile, post details) are well-separated. No tools appear to overlap in functionality.
All tools follow a consistent 'linkedin_verb_noun' pattern with snake_case throughout. The verbs are appropriate and predictable (e.g., create, delete, get, search, update), and nouns clearly indicate the resource (e.g., post, comment, profile). There are no deviations in naming conventions.
With 17 tools, the count is slightly high but reasonable for a comprehensive LinkedIn API server covering posts, comments, profiles, companies, jobs, and OAuth. It includes core CRUD operations and search functionalities, though it might benefit from slight consolidation in some areas like OAuth-related tools.
The tool set provides strong coverage for LinkedIn's social and professional features, including create, read, update, delete for posts and comments, profile fetching, and searches. Minor gaps include lack of tools for liking/reacting to content or managing connections, but agents can perform core workflows effectively without dead ends.