LinkedIn Jobs MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@LinkedIn Jobs MCP ServerCheck if my LinkedIn cookie is valid"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
LinkedIn Jobs MCP Server
Self-hosted MCP server that scrapes LinkedIn jobs via the linkedin-api Voyager wrapper.
Runs in Docker. No Apify, no per-run costs.
Setup
1. Configure credentials
cp .env.example .env
# Edit .env and fill in your LinkedIn email and password⚠️ Use a burner LinkedIn account — automated access violates LinkedIn's ToS and risks the account being restricted.
2. Build and test
# Build the Docker image
docker build -t linkedin-mcp .
# Quick smoke test — should print the MCP server startup log
docker run --rm --env-file .env linkedin-mcp
# Ctrl+C to stop3. Wire into Claude Desktop
Edit your Claude Desktop config file:
Mac:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"linkedin-jobs": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"--env-file", "/ABSOLUTE/PATH/TO/linkedin-mcp/.env",
"linkedin-mcp"
]
}
}
}⚠️ Use the absolute path to your .env file.
~/does not expand here.
4. Restart Claude Desktop
After saving the config, fully quit and reopen Claude Desktop.
You'll see a 🔧 tools icon in the chat bar — click it to confirm
scrape_jobs, get_job_details, and check_auth are listed.
5. First conversation
You: Check if my LinkedIn session is authenticated
Claude: [calls check_auth] ✓ Authenticated as John Doe
You: Scrape 20 AI Engineer or ML Engineer jobs posted in the last 3 days in the US
Claude: [calls scrape_jobs] ...returns full job list with descriptionsRelated MCP server: LinkedIn MCP Server
Development
# Run with live source reloading
docker compose up
# Inspect MCP tools without Claude Desktop
npx @modelcontextprotocol/inspector docker run --rm -i --env-file .env linkedin-mcpProject structure
linkedin-mcp/
├── src/
│ ├── server.py # MCP server — tool definitions and handlers
│ ├── scraper.py # linkedin-api Voyager wrapper calls
│ ├── models.py # Pydantic models for Job data
│ └── __init__.py
├── Dockerfile
├── docker-compose.yml
├── requirements.txt
├── .env.example
└── .gitignoreThis server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/FuriousApe/linkedin-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server