linkedin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LINKEDIN_TIMEOUT | No | HTTP request timeout in seconds. | 30 |
| LINKEDIN_CACHE_TTL | No | Seconds to keep snapshot data in memory. 0 disables the cache. | 3600 |
| LINKEDIN_ACCESS_TOKEN | Yes | OAuth access token. |
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 |
|---|---|
| get_profileA | Get the user's basic LinkedIn profile: name, headline, summary, location. |
| list_conversationsB | List LinkedIn message conversations, most recently active first. |
| get_conversationA | Get one LinkedIn conversation with its messages in chronological order. |
| search_messagesB | Search LinkedIn messages, newest first. Matching ignores case and accents. |
| search_connectionsA | Search the user's first-degree LinkedIn connections, most recent first. Email addresses are only present for connections who allow exporting them. |
| list_postsA | List the user's LinkedIn posts, newest first. Posts made after the user's consent may only appear in get_recent_activity. |
| get_recent_activityA | Get the user's LinkedIn activity since consent (last 28 days), newest first. Covers new messages, posts, comments and reactions. Times are epoch milliseconds. |
| list_data_domainsA | List all LinkedIn data domains that have data for the user, with row counts. The first call fetches all data and takes several seconds. |
| get_data_domainA | Get raw data rows from any LinkedIn data domain, for example POSITIONS or SKILLS. |
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 9 tools
Most tools target distinct resources and actions: profile, conversations, messages, connections, posts, recent activity, and raw data domains. The only mild overlap is between get_recent_activity and list_posts/list_conversations, but the description clarifies its aggregate, consent-window scope.
All names use consistent snake_case with clear verb_noun patterns: get_profile, list_conversations, get_conversation, search_messages, search_connections, list_posts, get_recent_activity, list_data_domains, get_data_domain. The verbs are appropriate and predictable.
Nine tools is well-scoped for a LinkedIn data-access MCP server. Each tool covers a meaningful area without excessive fragmentation.
The surface covers core read access: profile, conversations, messages, connections, posts, recent activity, and generic raw domain retrieval. Minor gaps exist, such as no dedicated search_posts or get_post, but the generic data-domain tools provide a workaround.