Skip to main content
Glama
alexanderskorokhodov

remote-mcp-linkedin

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
REMOTE_MCP_LINKEDIN_LOG_LEVELNoServer log level.INFO
REMOTE_MCP_LINKEDIN_BRIDGE_HOSTNoWebSocket listener host for bridge connections.127.0.0.1
REMOTE_MCP_LINKEDIN_BRIDGE_PORTNoWebSocket listener port for bridge connections.8765
REMOTE_MCP_LINKEDIN_RESULTS_DIRNoLocal directory for extracted profile/dossier JSON results..remote-mcp-linkedin/results
REMOTE_MCP_LINKEDIN_BRIDGE_TOKENYesShared 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

CapabilityDetails
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

NameDescription
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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

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