Skip to main content
Glama
LinkedIn MCP

LinkedIn MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_TRANSPORTNoTransport for the MCP server. Defaults to stdio; can be set to streamable-http.stdio
LINKEDIN_CLIENT_IDYesLinkedIn OAuth client ID for your LinkedIn developer app.
LINKEDIN_REDIRECT_URIYesOAuth redirect URI that exactly matches the redirect URI configured in the LinkedIn Developer Portal.
LINKEDIN_CLIENT_SECRETYesLinkedIn OAuth client secret for your LinkedIn developer app.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
linkedin_connection_statusA

Check whether a LinkedIn access token is stored; never returns the token.

linkedin_start_oauthA

Create a LinkedIn OAuth authorization URL. Open it and sign in to authorize the app.

linkedin_exchange_codeA

Exchange an OAuth authorization code for a token after checking the state generated in this session.

linkedin_get_my_profileA

Read the signed-in member's basic OpenID profile fields, if the app has the required permissions.

linkedin_draft_profile_changesB

Prepare suggested headline/About/experience text. This tool drafts only; it does not edit LinkedIn.

linkedin_prepare_postB

Validate and prepare a post for review; does not publish it.

linkedin_publish_approved_postB

Publish a post through LinkedIn's official Posts API only when the caller explicitly confirms approval.

linkedin_get_my_postsB

Retrieve the authenticated member's posts. Requires LinkedIn approval for r_member_social.

linkedin_get_postC

Retrieve a specific post by its LinkedIn URN, if the app has permission.

linkedin_delete_approved_postB

Delete a post only after explicit approval. This is irreversible and depends on LinkedIn API access.

linkedin_capabilities_and_limitsA

Explain which features are implemented and which depend on LinkedIn API approval.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 11 tools

Disambiguation4/5

Tools map cleanly to distinct steps: the three OAuth tools (status/start/exchange) are sequential and separable, and get_my_posts vs get_post vs delete_approved_post are clearly differentiated. Minor overlap between linkedin_connection_status and linkedin_capabilities_and_limits, and between the two 'draft' tools, but descriptions make the boundaries clear.

Naming Consistency4/5

Every name uses the linkedin_ prefix with snake_case and mostly verb_noun structure (start_oauth, exchange_code, get_my_profile, prepare_post, publish_approved_post). A couple of names are noun phrases (connection_status, capabilities_and_limits), a small but readable deviation.

Tool Count5/5

11 tools is well within the ideal range and each earns its place: three auth steps, profile read/draft, and a full post draft-publish-read-delete lifecycle. No filler or redundant tools.

Completeness3/5

Auth, profile read, and the post lifecycle are covered, but linkedin_draft_profile_changes is a dead end with no corresponding apply/publish tool, and there is no token refresh, revoke/logout, or engagement (comment/reaction) surface. Some gaps are attributable to documented LinkedIn API restrictions, but agents still hit walls.