LinkedIn MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_CLIENT_ID | No | LinkedIn app client ID for interactive OAuth (PKCE). | |
| LINKEDIN_ENABLE_ORG | No | Enable organization tools once approved for Marketing Developer Platform. | false |
| LINKEDIN_ACCESS_TOKEN | No | Your LinkedIn access token (bring your own token). | |
| LINKEDIN_CLIENT_SECRET | No | LinkedIn app client secret (only if your app is confidential). | |
| LINKEDIN_MCP_TRANSPORT | No | Transport for the MCP server (stdio or http). | stdio |
| LINKEDIN_ENABLE_SOCIAL_FEED | No | Enable social feed tools (reactions/social metadata) once approved for Community Management API. | false |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_get_profileA | Get the authenticated member's LinkedIn profile. Returns name, email, profile picture, locale and — most importantly — the
member's person URN (e.g. |
| linkedin_upload_imageA | Upload a local image file and return its image URN. Pass the returned Args:
author_urn: The owner URN ( |
| linkedin_upload_videoB | Upload a local video file and return its video URN. LinkedIn processes video asynchronously; a freshly uploaded video may take a short while before a post referencing it goes fully live. Args: author_urn: The owner URN. file_path: Absolute path to a local video (MP4). |
| linkedin_upload_documentA | Upload a local document (e.g. PDF) and return its document URN. Reference the returned Args: author_urn: The owner URN. file_path: Absolute path to a local document (PDF). |
| linkedin_create_postA | Create a LinkedIn post. Supports text, image, multi-image, video, document, and article/link posts — pick ONE media type per call.
Args:
author_urn: |
| linkedin_create_pollA | Create a poll post with 2–4 options. Poll content cannot be edited after creation. Do not ask for political opinions, health status, or other sensitive data (LinkedIn policy). Args: author_urn: The author URN. question: The poll question (used as the post commentary). options: 2 to 4 answer options. duration: ONE_DAY, THREE_DAYS, SEVEN_DAYS, or FOURTEEN_DAYS. |
| linkedin_reshare_postC | Reshare an existing post, optionally with your own commentary. Args:
author_urn: The resharing author's URN.
reshared_post_urn: URN of the post to reshare ( |
| linkedin_update_postA | Edit an existing post's commentary (text). LinkedIn's partial-update only supports editing the commentary of an existing post; author, media, and poll content cannot be changed. Args:
post_urn: The post URN ( |
| linkedin_delete_postC | Delete a post. Args: post_urn: The post URN to delete. |
| linkedin_commentA | Comment on a post, or reply to a comment. Scope: Args:
actor_urn: Who is commenting ( |
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 10 tools
Each tool targets a distinct resource+action: three upload tools split cleanly by media type (image/video/document), and the post operations (create, create_poll, reshare, update, delete) plus comment and get_profile are mutually exclusive in purpose. Descriptions reinforce the boundaries, e.g. noting that create_post takes exactly one media type.
Every tool follows a uniform linkedin_verb_noun snake_case pattern (upload_video, create_post, create_poll, reshare_post, update_post, delete_post, get_profile). No mixed conventions or vague verbs appear.
Ten tools is well-scoped for the domain: uploads, post lifecycle, engagement, and identity lookup each earn their place with no redundancy or filler.
Post creation lifecycle (create/update/delete), media uploads, polls, reshares, comments, and profile lookup are all covered, forming a coherent surface. Minor gaps remain: no read/list tools for existing posts or comments, and no reaction/like operations, but core publishing workflows are fully achievable.