remote-mcp-linkedin
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REMOTE_MCP_LINKEDIN_LOG_LEVEL | No | Server log level. | INFO |
| REMOTE_MCP_LINKEDIN_BRIDGE_HOST | No | WebSocket listener host for bridge connections. | 127.0.0.1 |
| REMOTE_MCP_LINKEDIN_BRIDGE_PORT | No | WebSocket listener port for bridge connections. | 8765 |
| REMOTE_MCP_LINKEDIN_RESULTS_DIR | No | Local directory for extracted profile/dossier JSON results. | .remote-mcp-linkedin/results |
| REMOTE_MCP_LINKEDIN_BRIDGE_TOKEN | Yes | Shared token used to authenticate the local bridge. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_profile_getB | Return normalized raw visible profile sections via the local bridge. |
| linkedin_profile_dossierC | Build a deterministic structured dossier from visible profile sections. |
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 2 tools
The two tools have clearly distinct purposes: one produces a structured dossier, the other returns raw profile sections. There is no ambiguity about which to use for a given task.
Both tools share the 'linkedin_profile_' prefix, but one uses a noun ('dossier') and the other a verb ('get'), which is inconsistent. A consistent verb-noun pattern would be clearer.
With only two tools, the server feels thin for a platform as broad as LinkedIn. However, the tools are well-focused on profile data, so the count is borderline reasonable for that narrow scope.
The server covers only profile retrieval in two formats, missing many common LinkedIn operations like searching, messaging, or managing connections. This is a significant gap for general LinkedIn usage.