linkedin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_PERSON_URN | Yes | Your LinkedIn person URN, e.g. urn:li:person:SUB_VALUE. | |
| LINKEDIN_ACCESS_TOKEN | Yes | LinkedIn access token obtained via the OAuth 2.0 flow (valid for 60 days). | |
| LINKEDIN_ORGANIZATION_URN | No | Your LinkedIn organization URN for company page features (only needed if you enabled company page access). |
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 |
|---|---|
| post_to_profileA | Post to your personal LinkedIn profile. Returns the post URN and URL. |
| post_to_company_pageA | Post to a LinkedIn company page you administer. Requires LINKEDIN_ORGANIZATION_URN to be set. Returns the post URN and URL. |
| comment_on_postA | Comment on a LinkedIn post, as your profile or a company page. Useful right after publishing — LinkedIn's feed algorithm weighs early engagement heavily. |
| get_recent_postsA | List the most recent posts for your profile or company page, with their URNs and basic stats. Useful for finding post URNs to comment on. |
| get_post_analyticsA | Get performance stats (impressions, reactions, comments, shares, clicks) for a specific LinkedIn post. |
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 targets a clearly different action and resource: posting to a profile, posting to a company page, commenting, listing recent posts, and fetching analytics. There is no meaningful overlap or ambiguity between the tools.
All tool names follow the same snake_case verb-first convention, with clear patterns like post_to_* and get_*. The naming is predictable and makes the purpose of each tool immediately obvious.
Five tools is well-scoped for a LinkedIn content publishing and engagement server. Each tool covers a distinct core operation without unnecessary bloat or missing essentials.
The set covers the main lifecycle for LinkedIn posting: create posts, comment, retrieve recent posts, and view analytics. Delete and update operations are absent, but they are not core to the apparent purpose of publishing and measuring engagement.