Unlinked
Let your coding agent read your LinkedIn profile and work history when drafting bios, pitches, or portfolio copy.
Overview
Unlinked is an MCP server for the Grow phase that loads your LinkedIn profile and experience into the agent’s context.
What is this MCP server?
- Stdio MCP server (@larsbaunwall/unlinked v1.0.4) exposing LinkedIn profile and experience to the agent
- OAuth-linked LINKEDIN_TOKEN env var (required for EEA/Switzerland members)
- Optional LINKEDIN_API_VERSION override (YYYYMM, default 202312)
- Bearer or bare token formats accepted for authentication
- Server version 1.0.4
- Default LinkedIn API version 202312
- Two documented environment variables (one required for EEA/Switzerland)
Community signal: 3 GitHub stars.
What problem does it solve?
Agents invent career details when your real LinkedIn history is not in the workspace.
Who is it for?
Indie founders and consultants who refresh landing copy, newsletters, or pitch decks and want LinkedIn as the source of truth.
Skip if: Teams that need bulk prospecting, automated posting, or LinkedIn data without a member token.
What do I get? / Deliverables
After you register the stdio server with LINKEDIN_TOKEN, the agent can cite your actual roles, skills, and timeline while you write.
- Agent-accessible LinkedIn profile and experience fields in chat context
- Version-stable calls when LINKEDIN_API_VERSION is set
Recommended MCP Servers
Journey fit
How it compares
LinkedIn profile MCP integration, not a social scheduling or CRM skill.
Common Questions / FAQ
Who is unlinked for?
Solo builders and consultants who want their agent grounded in their real LinkedIn profile when writing professional content.
When should I use unlinked?
Use it during grow and launch content passes whenever bios, case studies, or outreach must mirror your LinkedIn experience.
How do I add unlinked to my agent?
Install @larsbaunwall/unlinked as a stdio MCP server, set LINKEDIN_TOKEN from LinkedIn’s OAuth Token Generator, and restart your client.