MCP server that brings your LinkedIn professional profile and experience into you context.
If you already use Unlinked, the unlinked mcp server is the piece that lets your assistant work with it directly. MCP server that brings your LinkedIn professional profile and experience into you context.
Bring your LinkedIn professional profile into AI assistants — without copy-pasting, scraping, or guessing.
npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
linkedin_get_profile — Get the user's LinkedIn résumé: bio, work history, education, skills, certifications, projects, etclinkedin_get_activity — Get the user's LinkedIn activity: connections, posts, articles, comments, likes, job applicationslinkedin_get_section — Get raw data for one specific LinkedIn section by exact namelinkedin_get_recent_changes — Get recent changes to the user's LinkedIn data (past 28 days), with cursor-based pollinglinkedin_check_access — Check whether the user has granted LinkedIn data access — useful for diagnosing missing dataConfiguration is passed through the environment: LINKEDIN_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Unlinked's toolset — linkedin_get_profile, linkedin_get_activity, linkedin_get_section and 2 more — is a fair guide to whether it matches your workflow. It is maintained by larsbaunwall; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| linkedin_get_profile | Get the user's LinkedIn résumé: bio, work history, education, skills, certifications, projects, etc. |
| linkedin_get_activity | Get the user's LinkedIn activity: connections, posts, articles, comments, likes, job applications |
| linkedin_get_section | Get raw data for one specific LinkedIn section by exact name |
| linkedin_get_recent_changes | Get recent changes to the user's LinkedIn data (past 28 days), with cursor-based polling |
| linkedin_check_access | Check whether the user has granted LinkedIn data access — useful for diagnosing missing data |
{
"mcpServers": {
"unlinked": {
"command": "npx",
"args": ["-y", "@larsbaunwall/unlinked"],
"env": {
"LINKEDIN_TOKEN": "<your_access_token>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| LINKEDIN_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.