linkedin-web-scrapper-mcp-server
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 |
|---|---|
| search-linkedin-peopleB | Search for LinkedIn profiles using web scraping. Returns profile names, URLs, and headlines. |
| scrape-linkedin-profileA | Scrape comprehensive data from a specific LinkedIn profile URL. Returns detailed profile information including experience, education, skills, licenses & certifications, and more. |
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 discovers profiles via search, the other extracts detailed data from a specific profile URL. There is no overlap in functionality.
Both tools follow a consistent verb_noun pattern using 'search-linkedin-people' and 'scrape-linkedin-profile', maintaining the same structure and style.
With only two tools, the server is minimal but each serves a necessary step in the LinkedIn people-scraping workflow. The count feels slightly thin, yet it aligns with the focused purpose of the server.
The tools form a complete flow: search for profiles and then scrape any selected profile. Minor gaps exist (e.g., no company or job search), but for a people-focused scraper, the core lifecycle is covered.