About linkedin-osint-mcp
linkedin-osint-mcp is an MCP server that uses Serper-backed Google searches to collect employee usernames from LinkedIn. It is intended for OSINT tasks such as finding people associated with an organization and formatting the results.
Key features
- 01Search Google via Serper
- 02Collect LinkedIn employee usernames
- 03Search across multiple result pages
- 04Format names as email addresses
- 05Save results to CSV
Use cases
- 01Find LinkedIn profiles associated with an organization
- 02Expand employee searches across result pages
- 03Format names into an email pattern
- 04Export collected names to CSV
MCP support
It exposes LinkedIn employee-search functionality to MCP clients. Configure it in an MCP client and provide a Serper API key.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMElinkedin-osint-mcp
Uses Serper to perform a Google search to gather a list of employees from LinkedIn.
Usage
- Install uv
- Get an API key from Serper and add it to
.envfile. - Configure MCP client:
E.g., Claude Desktop
{
"mcpServers": {
"linkedin_osint": {
"command": "uv",
"args": [
"--directory",
"C:\\path\\\\to\\linkedin-osint-mcp",
"run",
"main.py"
]
}
}
}
Example Queries
"Get a list of users that work at Bullworth Academy." // basic
"Get a list of users that work at Bullworth Academy and find as many as you can." // will search through multiple pages
"Find all users that work at Bullworth Academy and format the results as "[email protected]" and save to a csv file." // format names into emails
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.