LinkedIn MCP for OpenWorker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_VERSION | No | LinkedIn API version | 202607 |
| LINKEDIN_CLIENT_ID | Yes | Your LinkedIn OAuth client ID | |
| LINKEDIN_REDIRECT_URI | Yes | Your LinkedIn OAuth redirect URI | |
| LINKEDIN_CLIENT_SECRET | Yes | Your LinkedIn OAuth 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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_start_oauth_flowA | Start a browser-based LinkedIn OAuth flow, capture the localhost callback, exchange the code, and store the token locally. |
| linkedin_auth_statusA | Check whether this MCP server has a stored LinkedIn OAuth token. |
| linkedin_logoutA | Delete the locally stored LinkedIn OAuth token for this MCP server. |
| linkedin_exchange_authorization_codeA | Exchange a LinkedIn OAuth authorization code for tokens and store the token locally. |
| linkedin_get_my_profileA | Read the authenticated LinkedIn member profile using the OIDC userinfo endpoint. |
| linkedin_create_text_postA | Publish or draft a text-only LinkedIn post for a member or organization author URN. |
| linkedin_get_postA | Retrieve a LinkedIn post by URN. |
| linkedin_find_posts_by_authorB | Find LinkedIn posts by member or organization author URN. |
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 8 tools
Most tools are clearly distinct, but linkedin_start_oauth_flow and linkedin_exchange_authorization_code overlap since the start flow already includes exchanging the authorization code. An agent could be unsure which to use for a given OAuth scenario.
All tool names follow a consistent linkedin_verb_noun snake_case pattern. Verbs are clear and predictable, making the toolset easy to navigate.
Eight tools is well-scoped for a LinkedIn MCP covering authentication, profile access, and post management. Each tool earns its place without unnecessary bloat.
Core auth and post workflows are covered, but the post surface is read/create only—there is no update or delete post tool. This is a minor gap for typical LinkedIn content management workflows.