Scrape LinkedIn profiles and companies, get recommended jobs, and perform job searches.
LinkedIn MCP MCP server exists for a simple reason — assistants are far more useful when they can act on LinkedIn MCP directly instead of describing what you should do. Scrape LinkedIn profiles and companies, get recommended jobs, and perform job searches.
An MCP server that lets AI assistants like Claude read LinkedIn data through your own logged-in browser session. Access profiles and companies, search for jobs, or get job details.
Once LinkedIn MCP is connected, these are the calls the assistant has available:
Auto — import is skipped while a proxy is configured: a session taken from a local browser was created on your real address, and moving it to the proxy isget_person_profile — Get profile info with explicit section selection (experience, education, interests, honors, languages, certifications, skills, projectsget_my_profile — Get the authenticated user's own LinkedIn profile (same sections as get_person_profile)connect_with_person — Send a connection request or accept an incoming one, with optional noteget_sidebar_profiles — Extract profile URLs from sidebar recommendation sections ("More profiles for you", "Explore premium profiles", "People you may know") on a profileget_inbox — List recent conversations from the LinkedIn messaging inboxget_conversation — Read a specific messaging conversation by username or thread IDsearch_conversations — Search messages by keywordsend_message — Send a message to a LinkedIn user (requires confirmation)get_company_profile — Extract company information with explicit section selection (posts, jobs); about-section references may include a company_urn entry carrying theget_company_posts — Get recent posts from a company's LinkedIn feedsearch_companies — Search for companies on LinkedIn by keywordsYou will need one environment variable: UV_HTTP_TIMEOUT. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. LinkedIn MCP's toolset — Auto, get_person_profile, get_my_profile and 11 more — is a fair guide to whether it matches your workflow.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Auto | import is skipped while a proxy is configured: a session taken from a local browser was created on your real address, and moving it to the proxy is the very change that triggers a checkpoint. Use --login. |
| get_person_profile | Get profile info with explicit section selection (experience, education, interests, honors, languages, certifications, skills, projects, contact_info, posts) |
| get_my_profile | Get the authenticated user's own LinkedIn profile (same sections as get_person_profile) |
| connect_with_person | Send a connection request or accept an incoming one, with optional note |
| get_sidebar_profiles | Extract profile URLs from sidebar recommendation sections ("More profiles for you", "Explore premium profiles", "People you may know") on a profile page |
| get_inbox | List recent conversations from the LinkedIn messaging inbox |
| get_conversation | Read a specific messaging conversation by username or thread ID |
| search_conversations | Search messages by keyword |
| send_message | Send a message to a LinkedIn user (requires confirmation) |
| get_company_profile | Extract company information with explicit section selection (posts, jobs); about-section references may include a company_urn entry carrying the numeric id used by LinkedIn's people-search currentCompany URL facet |
| get_company_posts | Get recent posts from a company's LinkedIn feed |
| search_companies | Search for companies on LinkedIn by keywords |
| get_company_employees | List employees at a company from the /people/ page, with optional keyword filter |
| search_jobs | Search for jobs with keywords and location filters |
{
"mcpServers": {
"mcp-server-linkedin": {
"command": "uvx",
"args": ["mcp-server-linkedin@latest"],
"env": { "UV_HTTP_TIMEOUT": "300" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| UV_HTTP_TIMEOUT | Configuration value read at startup. | Optional |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.