Is there an official LinkedIn MCP server?
LinkedIn's developer portal links a Develop with MCP entry. The MCP Registry lists no server under a LinkedIn namespace. The servers we found for member accounts are built by other teams. This page shows what exists and how to connect one.
What exists instead
Three shapes of LinkedIn MCP server are public today. They differ on who runs the server and whose account it acts on.
Hosted servers from LinkedIn tool companies
A company runs the server and connects it to an account you hold with them. You get one endpoint and a sign-in. Crispy works this way.
Open source servers you run yourself
You install the server on your own machine. It either drives your own LinkedIn session in a browser or calls the official REST API with an access token you create.
Listings in the official MCP Registry
The registry carries LinkedIn servers published by independent teams. A search on 2026-10-28 found none under a LinkedIn namespace.
The table at /compare/mcp-servers lists each server we could check against its own public README or website.
What Crispy is
Crispy is a hosted LinkedIn MCP server. One remote endpoint exposes documented tools for search, messaging, content, campaigns, contacts, lists, and account settings. Any client that speaks MCP can call them.
You connect your own LinkedIn account. The agent then works on that account, so the actions are yours and so are the limits.
The full product page is at /linkedin-mcp-server, and the tool catalog lives in the docs.
How to connect a client
Create a Crispy account and connect your LinkedIn account from the dashboard. Then add the remote endpoint to your MCP client. Each client has its own setup flow, so follow the guide written for yours.
claude mcp add --transport http crispy https://crispy.sh/api/mcp --header "Authorization: Bearer YOUR_API_KEY"Every guide on this list links to the full integration directory.
Authentication
The remote endpoint supports OAuth. Sign in once and the client holds no key. Clients that send an Authorization header can use a Bearer API key instead.
Keys are generated in the dashboard and start with crispy_. Scopes decide which tools the agent may call. Start on the core scope and widen it when the workflow needs it.
Safety and pacing
Crispy applies a default daily cap per action category on each connected account. The action is blocked while that cap is in force. Optional warm-up raises the caps in steps, and the caps can be lowered per account.
LinkedIn's User Agreement section 8.2 prohibits unauthorized automation. The caps do not authorize the activity. They do not guarantee against restriction.
Read the full picture on LinkedIn safety and in the docs.
Questions about LinkedIn MCP servers
Is there an official LinkedIn MCP server?
LinkedIn's developer portal links a Develop with MCP entry. The MCP Registry lists no server under a LinkedIn namespace. Every LinkedIn member-account MCP server we found is built by another team. Read LinkedIn's own page for its current status.
What LinkedIn MCP servers exist?
Hosted servers from LinkedIn tool companies, open source servers you run on your own machine, and open source servers that call the official REST API. Crispy is one of the hosted options.
Is Crispy a LinkedIn MCP server?
Yes. Crispy is a hosted LinkedIn MCP server with documented tools for search, messaging, content, campaigns, contacts, lists, and account settings.
How do I connect an AI client to Crispy?
Add https://crispy.sh/api/mcp as a remote MCP server, authenticate with OAuth or a Bearer API key, then follow the setup guide written for your client.
How does Crispy pace actions on my account?
Crispy applies a default daily cap per action category and blocks the action while that cap is in force. Optional warm-up raises the caps in steps. These controls do not guarantee against restriction.
Keep reading
All your LinkedIn growth in one place.
Create your account and connect LinkedIn. Then ask Claude or ChatGPT.