LinkedIn MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | Yes | Host address for the MCP server. | 0.0.0.0 |
| MCP_PORT | Yes | Port for the MCP server. | 8050 |
| COOKIE_DIR | Yes | Directory path where cookies are stored. | |
| MCP_TIMEOUT | Yes | Timeout in seconds for MCP operations. | 150 |
| MCP_TRANSPORT | Yes | Transport protocol to use: 'sse', 'stdio', or 'streamable-http'. | |
| LINKEDIN_USER_1 | Yes | LinkedIn username for the first account. | |
| LINKEDIN_USER_2 | No | LinkedIn username for a second account (optional). | |
| LINKEDIN_PASSWORD_1 | Yes | LinkedIn password for the first account. | |
| LINKEDIN_PASSWORD_2 | No | LinkedIn password for a second account (optional). |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| linkedin_profileA | In 2019 I commenced my learning on Artificial Intelligence and Deep Learning and related technologies and participated in several Kaggle competitions. I dedicate my weekends to my pet projects for UK charities which promote well-being and meditation.", "summary": "", "industry_name": "Software Engineer at Onepoint Consulting", "geo_location": "London Area, United Kingdom", "linkedin_profile_url": "https://www.linkedin.com/in/gil-palma-fernandes", "experiences": [ { "institution_name": "Onepoint Consulting · Full-time", "linkedin_url": "https://www.linkedin.com/company/309728/", "website": "", "industry": "", "type": "", "headquarters": "", ... |
| profile_searchA | Search for LinkedIn profiles by name. Args: name: The name to search for Returns: A list of LinkedIn profiles as dictionaries Example output in case of success: [ { "person_name": "Gil Fernandes", "person_linkedin_url": "https://www.linkedin.com/in/gil-palma-fernandes/", "profile_id": "gil-palma-fernandes", "title": "Software Engineer at Onepoint Consulting" }, { "person_name": "Gil Fernandes", "person_linkedin_url": "https://www.linkedin.com/in/gil-fernandes-a7578334a/", "profile_id": "gil-fernandes-a7578334a", "title": "Passionate Holistic Therapist and Dynamic Team Leader with over 12 years of experience across diverse care settings. Skilled in crisis management and dedicated to fostering well-being in every aspect of care!" } ... Example output in case of error: { "error": "Error searching profiles: Error searching profiles" } |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| profile_search_by_name | Returns a prompt that you can use to search for a LinkedIn profile by name. |
| profile_experiences_by_profile_id | Returns a prompt that you can use to list the experiences of a LinkedIn profile by profile id. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| british_english_resource | Used to define a specific language and behaviour for the MCP. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one extracts a full profile from a URL or username, while the other searches for profiles by name. There is no overlap or ambiguity in their intended use.
The tool names do not follow a consistent verb_noun pattern. 'linkedin_profile' is a noun phrase, while 'profile_search' places the verb at the end. This is a minor inconsistency, but both names are descriptive and readable.
With only 2 tools, the server feels slightly thin for a comprehensive LinkedIn integration. However, the two tools cover the core search-and-retrieve workflow, so the count is borderline appropriate for a focused profile-scraping server.
The tool set covers the main workflow of finding a profile via search and then retrieving its full details. Missing features like connections or posts are not critical for the apparent purpose of profile extraction, so the coverage is solid with only minor gaps.