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. |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/alexanderskorokhodov/remote-mcp-linkedin'
If you have feedback or need assistance with the MCP directory API, please join our Discord server