agentic-linkedin
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., "@agentic-linkedinWrite a post announcing our Series A funding and approve it."
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.
agentic-linkedin
The LinkedIn MCP that never breaks.
An MCP server that gives an AI agent everything a person can do on LinkedIn: you describe what you want, the agent executes it, and you never touch the site.
Self-healing — selectors and endpoints live as data; provable fixes auto-apply when LinkedIn changes its DOM
Session hygiene — human-like pacing, write budgets, health probes, graceful re-auth; never locks you out
Reliable posting — verify-after-post, persisted dedupe keys, never an auto-retry: nothing double-posts
Humanized content — per-user voice profiles and an AI-tell audit; everything reads like you wrote it
Observable — plan-then-execute with field-level diffs and rendered previews; redacted failure artifacts
Install
npx agentic-linkedinRequires Node 20+. The package is published to npm; the repository lives at github.com/DarkLvrd/linkedin-mcp.
Related MCP server: LinkedIn MCP Server
Sign in (once)
Start the server with your MCP client (Claude Desktop, Cursor, …).
Call the
logintool. A browser window opens — sign in to LinkedIn and let it redirect to your feed.The session persists to disk (
~/.agentic-linkedin/session.json) and restores across restarts.
Identity is never stored in the repo or in failure artifacts. Cookie values are redacted from every log, tool output, and artifact by construction.
The workflow: plan-then-execute
Describe what you want. The agent calls plan with the intended writes and
gets back an ordered list with previews:
profile changes show field-level old → new diffs
posts and messages show rendered feed-style previews with their AI-tell audit
a raw toggle always exposes the exact arguments
Nothing executes until you approve the plan. reject cancels it. dry_run
previews without storing anything. During execution every write still passes
the pacing engine: per-sign-in budgets, the hourly ceiling, randomized
human-like delays, and health probes — on a challenge the engine pauses until
you re-authenticate.
Tools
Session:
session_status,loginReads:
get_me,get_profile,get_posts,get_conversations,get_conversation_history,get_connections_summary,get_invitations,get_jobs,get_analyticsProfile:
update_profile,add_skill,remove_skill,reorder_skills,delete_ghost_entryPosts:
create_post,edit_post,delete_post,comment,reactMessaging:
send_message(idempotency-keyed),recall_message,react_to_messageNetwork:
connect,respond_invitation,follow,endorse_skill,remove_connectionPlanning:
plan,dry_run,approve,rejectSelf-healing:
show_artifact,update_registryVoice:
get_voice_profile,set_voice_profile,bootstrap_voice_profile,audit_draft
Configuration (environment variables)
Variable | Default | Purpose |
|
|
|
|
| where the session persists |
|
| persisted post-dedupe keys |
|
| redacted failure artifacts |
|
| runtime selector-registry fixes |
|
| per-user voice profiles |
|
| browser-context writes per sign-in (the authwall threshold) |
|
| total writes per sliding hour |
|
| randomized delay range before writes |
|
| session health-probe interval |
Development
npm ci
npm run check # typecheck + build + full test suiteTests run fully offline: the transport seam is faked, Voyager/SDUI responses are replayed from recorded fixtures, and the binary is exercised end-to-end over stdio. Live LinkedIn actions are never automated in CI.
License
MIT — see LICENSE.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables AI agents to manage LinkedIn profiles, posts, connections, skills, education, and certifications through the LinkedIn API.1817664MIT
- AlicenseBqualityAmaintenanceEnables AI agents with read/write access to LinkedIn API, including profile, posts, media, organizations, comments, reactions, and analytics.2014MIT
- AlicenseAqualityAmaintenanceEnables AI agents to publish posts, images, comments, and reactions to LinkedIn as the authenticated user, with built-in safety features like daily budgets and deduplication.929Apache 2.0
- AlicenseAqualityBmaintenanceLets an AI assistant operate LinkedIn through an authenticated browser session, enabling profile management, posting, networking, messaging, job search, and automated applications.1003831MIT
Related MCP Connectors
Give AI agents the LinkedIn tools to find, qualify, engage, and follow up with prospects.
Live LinkedIn data for AI agents: profiles, companies, jobs, posts, email finding. No account risk.
Managed LinkedIn MCP server for AI agents: search, connect, message and enrich on accounts you own.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- 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/DarkLvrd/linkedin-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server