get_profileLABSCO SUMMARY
One tool, one key, one API.
There is nothing to configure beyond the RapidAPI key, and the whole surface is a profile URL in, JSON out — which makes the third-party dependency the thing to weigh. Profile data comes from the Fresh LinkedIn Profile Data API on RapidAPI, so coverage, rate limits and cost are that provider's, not this server's.
What it is
A single-purpose MCP server that reads LinkedIn profile data. It takes a profile URL, calls the Fresh LinkedIn Profile Data API through RapidAPI, and returns the profile as JSON for the model to work with.
What you get
- Profile data for one LinkedIn URL, returned as JSON —
get_profile - Skills included, with most of the optional extra sections turned off, so the response stays to the profile itself
- Non-blocking calls through
httpx, so a slow lookup does not stall the server - A clear failure path: a missing key raises at startup, and a failed API call returns a message saying the profile could not be fetched rather than an empty result
Requirements
A RapidAPI key in RAPIDAPI_KEY, read from a .env file in the project directory or from the environment. Python 3.12 or newer with the MCP framework, httpx and python-dotenv — the documented install is uv add mcp[cli] httpx requests. The server runs as uv run linkedin.py over stdio, and the client entry points at the project directory.
Setup effort
Build from source — git clone https://github.com/Ayesha0300/linkedin-profile-mcp.git
USE CASES
01
Reading a profile into a draft
Pull the profile JSON while writing outreach or a candidate summary, without leaving the conversation.
02
Screening a candidate's background
Fetch skills and profile details as structured data instead of copying from the page.
03
Enriching a list of contacts
Pass profile URLs one at a time and collect the JSON for each.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- Python 3.12+
- RAPIDAPI_KEY in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/Ayesha0300/linkedin-profile-mcp.git
cd linkedin-profile-mcp
uv add "mcp[cli]" httpx requestsCreate a .env file in the project directory containing RAPIDAPI_KEY=<YOUR_RAPIDAPI_KEY>.
MCP Clients
Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"linkedin_profile_scraper": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_LINKEDIN_PROFILE_MCP>",
"run",
"linkedin.py"
]
}
}
}The configuration on this page does not set RAPIDAPI_KEY; the project's instructions put it in a .env file. Check which folder the server reads that file from before you rely on it.
