One URL, OAuth, about two minutes
The server is at https://nilyo.com/mcp over streamable HTTP. Add it as a connector in Claude, ChatGPT, Cursor, VS Code or any MCP client and choose OAuth: the client registers itself through dynamic client registration, opens a browser once, and you sign in and authorize the accounts the agent may reach. There is no client id to create, no key to copy into a config file, and revoking access later is a click in your account. Runtimes without an OAuth flow, such as a self-hosted n8n, use a personal token as a bearer instead.
Is there an official LinkedIn MCP server?
No. LinkedIn publishes a developer API, not an MCP server, and the third-party servers you find are almost all built on that API — which means they can identify you and publish a post, and very little else. A few drive a headless browser on linkedin.com instead, which breaks when the interface moves and puts the account at risk, because that traffic is exactly what LinkedIn looks for. Nilyo is the third option: a hosted server that acts as your own connected account, through a connection layer that speaks the provider protocols directly.
Not a posting MCP
Most LinkedIn integrations stop where the official API stops: publish a post, and nothing else. Nilyo acts as your connected account, so the inbox, people and company search, your network, invitations and the comments under a post are all reachable. If what you need is an API to build a product on rather than an agent to use, that is a different tool, and the LinkedIn API page explains which one.
Human references in, stable IDs underneath
A LinkedIn URL is not an identifier, and a display name is not an identity. The tools make the resolution step explicit: linkedin_get_profile_from_url turns a URL into a profile carrying the provider user id, linkedin_resolve_person turns a name plus a company into a ranked set of candidates, and only then does linkedin_send_invitation or linkedin_start_conversation accept that id. Pass a URL where an id belongs and you get a corrective error naming the tool to call first, instead of a silent failure or an invitation sent to the wrong person.
“Find the right Alex Chen at Acme before inviting them.”
“Who in my network works at Stripe?”
“Find John’s comment on my last post and draft a response.”
Every tool says which ID it consumes
Chaining is the whole difficulty of agent work on LinkedIn, so each tool description names the identifier it expects, where that identifier comes from, and the identifiers people confuse it with. Errors follow the same rule: they come back structured, with the code, a readable message and the next tool to call. An agent that hits a stale conversation id is told to list conversations again rather than guessing, and an ambiguous write is never retried blindly — the state is read back first.
Sales Navigator MCP and Recruiter MCP, kept distinct from Classic
LinkedIn publishes no Sales Navigator MCP server and no Recruiter MCP server, and most LinkedIn MCP servers ignore the distinction entirely. Nilyo exposes both when the connected account holds the seat. They share one account but they are not interchangeable: each has its own search and its own inbox, and a message sent from the wrong one is the wrong kind of message. linkedin_list_inboxes reports which seats the connected account actually holds, linkedin_sales_navigator_search_people and the Recruiter search have their own tools with their own filters, and starting a conversation from a specific inbox is an explicit action. Nothing silently falls back to Classic.
“Search Sales Navigator for VP Operations in Lyon and tell me who we already spoke to.”
“Which LinkedIn inboxes does my account have?”
More than sixty LinkedIn tools
Profiles and company pages, people, company, post and job search, connections, followers and following, invitations sent, received, accepted and cancelled, conversations and messages across every inbox, posts with their comments, replies and reactions, Classic job postings with their applicants and resumes, Recruiter projects, and InMail credits so an agent can check the ceiling before starting. They are grouped into capability families on the LinkedIn capabilities page, and the same account can be combined in one prompt with WhatsApp, email or your calendar.
Pacing is part of the server, not your problem
Calls are serialized per connected account and a daily budget of roughly one hundred LinkedIn actions applies, live reads included. When it is reached the agent receives an explicit limit error rather than a retry loop, and writes carry their own rate limit. This is deliberate: an assistant that can burn an account in one afternoon is not a feature, and LinkedIn reacts to rhythm as much as to volume.
Common questions
Is there a Sales Navigator MCP or a Recruiter MCP server?
Not from LinkedIn — it publishes neither. Nilyo exposes both from the same server when the connected account holds the seat: Sales Navigator keeps its own people search and its own inbox, Recruiter its own search and projects, and nothing silently falls back to Classic.
Does LinkedIn have an official MCP server?
No. LinkedIn publishes a developer API and no MCP server. Third-party servers built on that API inherit its limits — publishing a post, essentially. Nilyo drives your own connected account instead, which is why search, the inbox, invitations and comments are reachable.
What can a LinkedIn MCP server do?
It depends entirely on what is behind it. A server built on the official LinkedIn API can publish a post and little else. Nilyo drives your own connected account, so search, profiles, network, conversations, invitations, posts and comments are all available as tools.
How do I connect it to Claude or ChatGPT?
Add a custom connector with the URL https://nilyo.com/mcp and choose OAuth. The client registers itself, a browser opens once for you to sign in and authorize your accounts, and the tools appear. Nothing is installed and no key is stored in the client.
Do I need my LinkedIn password in the agent?
No. The account is connected on the Nilyo side through hosted authentication, and the agent only ever receives tools. Provider credentials are never returned to the client or visible in a tool argument.
Is this browser automation?
No. There is no headless browser. The connection layer speaks the provider protocols directly, which is why the session survives interface changes and why pacing can be applied before a request leaves rather than after an account is flagged.
Can I use it from n8n, Make or Zapier instead of a chat client?
Yes. Make and Zapier connect the same server URL through their MCP client with OAuth. n8n has a verified Nilyo community node with a personal token, and its nodes can be attached to an AI Agent as tools.
Does it work with a free LinkedIn account?
Yes. Sales Navigator and Recruiter add their own searches and inboxes when the account has those seats, but the standard capabilities need nothing extra.
How LinkedIn works with Nilyo
Connection. Secure hosted sign-in (your LinkedIn credentials go to LinkedIn, never to the agent). Sales Navigator and Recruiter are detected automatically when your account has them.
What your agent can do. People and company search, profile lookup from a name or URL, your network and invitations, private conversations (classic, Sales Navigator, Recruiter inboxes), posts, comments and reactions, job postings and applicants, Recruiter projects.
Pacing and safety. About 100 actions per day per account, profile views and searches included; calls are serialized so an agent can never run LinkedIn requests in parallel.
- Profile URLs are resolved to stable profile IDs before any action.
- Invitations carry an optional note of up to 300 characters.
- Private or restricted profiles return an explicit “not accessible” result instead of a retry loop.
All LinkedIn guides
Related guides
Give Nilyo to your agent.
Paste one setup link. Your agent can guide OAuth, account connection and the first useful action.