linkedin-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| linkedin_meA | Get the authenticated member's profile via OpenID Connect (sub, name, email, locale, picture). Works with the |
| linkedin_network_statsA | Get the member's network size (1st-degree connection count). Requires the r_1st_connections_size product/scope. |
| linkedin_connectionsC | List the member's 1st-degree connections (paginated). Requires an approved connections product/scope. |
| linkedin_get_profileA | Retrieve a member profile by person id (publicId or numeric/URN id). Requires an approved profile product/scope. |
| linkedin_search_peopleC | Search member profiles by keywords / location / company / industry. Requires an approved search product/scope. |
| linkedin_search_jobsA | Search job postings by keywords / location / company / job type. Requires an approved jobs product/scope. |
| linkedin_send_messageA | Send a message to a connection. Requires the w_member_social (messaging) product/scope. |
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 7 tools
Each tool has a distinct purpose: self-profile, profile by ID, search people, search jobs, send messages, connections list, and network size. Although 'me' and 'get_profile' both retrieve profiles, one is self and the other is arbitrary, so there is no ambiguity. The two search tools clearly target different resources.
All tools share the 'linkedin_' prefix, which is consistent. However, the pattern after the prefix varies: some use bare nouns (me, connections, network_stats) while others use verb_noun (search_people, search_jobs, send_message, get_profile). This is a minor inconsistency but still predictable and readable.
With 7 tools, the server is well-scoped for a LinkedIn integration. Each tool covers a core functionality area without unnecessary bloat, falling well within the typical 3-15 range for a focused server.
The tool surface covers the most common LinkedIn actions: viewing profiles, searching people and jobs, messaging, and managing connections. Missing capabilities like posting updates or managing connection requests are noticeable but not critical, as the core workflows are covered.