LinkedIn MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_ACCESS_TOKEN | Yes | Your LinkedIn OAuth 2.0 access token with necessary scopes (e.g., w_member_social, r_liteprofile, r_organization_admin). |
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 |
|---|---|
| get_my_profileB | Retrieve the authenticated user's LinkedIn profile information. |
| create_text_postC | Share a simple text update on the user's feed. |
| create_article_postB | Share an article with a URL and description. |
| get_connectionsA | List the user's 1st-degree connections (requires r_network permission). |
| get_organizationsA | List organizations the user administers. |
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 5 tools
Each tool has a clear and distinct purpose: two for posting (article vs text), three for retrieval (connections, profile, organizations). No overlap or ambiguity.
All tools follow a consistent verb_noun pattern (create_*, get_*), making the API predictable and easy to navigate.
5 tools is slightly lean for a social network API, but covers essential profile and posting operations. The set feels focused rather than incomplete.
Core operations are present (post, retrieve profile/connections/organizations), but notable gaps exist such as updating or deleting posts, commenting, or searching.