A LinkedIn MCP server gives an AI agent tools for LinkedIn, so a model can act on your account instead of only writing text about it. Point Claude, Cursor, or any MCP client at Outstand's server and the agent can draft, schedule, and publish LinkedIn posts, attach media, read engagement metrics, and reply to comments. Every action goes through the official LinkedIn API over an OAuth connection you approve once.
https://mcp.outstand.so/mcpclaude mcp add -t http \ -H "Authorization: Bearer ost_your_key" \ outstand https://mcp.outstand.so/mcp
Works with Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT, and any MCP client.
The server URL is https://mcp.outstand.so/mcp. Paste it into your client and connect LinkedIn.
claude mcp add -t http \ -H "Authorization: Bearer ost_your_key" \ outstand https://mcp.outstand.so/mcp
// claude_desktop_config.json
{
"mcpServers": {
"outstand": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.outstand.so/mcp",
"--header",
"Authorization: Bearer ost_your_key"
]
}
}
}// .cursor/mcp.json
{
"mcpServers": {
"outstand": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.outstand.so/mcp",
"--header",
"Authorization: Bearer ost_your_key"
]
}
}
}# Add a custom connector in your client's settings and paste # this URL, then sign in once in the browser. No API key to copy. https://mcp.outstand.so/mcp
Works with Claude Desktop, Claude Code, Cursor, Windsurf, ChatGPT, and any other MCP client. Full client setup guide.
The tools that apply to LinkedIn, out of 27 on the server.
create_postPublish or schedule a LinkedIn post, on its own or alongside other connected accounts.list_postsList posts, filterable by account, status, and date range.get_postFetch a single post and its per-platform publish status.get_post_analyticsFetch engagement metrics for a published post: likes, comments, shares, impressions.repost_postReshare a published post, with optional commentary on top of the reshare.create_replyReply to a comment on a post published through Outstand.get_repliesRead comments and replies on a post published through Outstand.delete_postDelete a post record in Outstand, cancelling it if it is still scheduled.delete_remote_postDelete the published post on LinkedIn itself.upload_mediaStart a media upload and get a signed URL for an image or video.confirm_media_uploadConfirm an upload once the bytes are transferred and get the public URL to attach.list_social_accountsList connected social accounts, so the agent can find your LinkedIn account.get_account_metricsFetch follower and profile-level metrics for a connected LinkedIn account.get_auth_urlGenerate an OAuth URL to connect a new LinkedIn account.get_account_usageRead current billing-period post usage.No. LinkedIn does not publish an MCP server and has not announced one. Every LinkedIn MCP server you can install today is built by a third party, and they fall into three groups.
The first group is open-source servers that drive LinkedIn by scraping the web app, usually authenticating with a session cookie lifted from your browser. They are free and they can read things the API will not expose, but they operate outside LinkedIn's terms, the cookie expires, and a front-end change can break them without warning.
The second group is community servers listed in MCP directories. Quality varies a great deal: some wrap the official API properly, others are thin scrapers with a nicer README, and many are unmaintained. Read the source before you trust one with an account.
The third group is hosted servers built on the official LinkedIn API, which is what Outstand is. You connect LinkedIn through a normal OAuth consent screen, the server calls the documented publishing endpoints, and there is no cookie to expire. The trade-off is that you can only do what the API permits, which is publishing and post analytics rather than anything scraped from a profile.
Three realistic ways to give an agent LinkedIn access, and what each one actually costs you.
| Approach | Setup time | Auth | Reliability | Compliance |
|---|---|---|---|---|
| Self-hosted open-source (scraper) | An hour or two: clone, install, extract a session cookie | Session cookie copied from your browser | Breaks when LinkedIn changes its front end or the cookie expires | Outside LinkedIn terms of service. Account risk is yours |
| Directory-listed community server | Minutes to hours, depending on the project | Varies: your own LinkedIn developer app, or a cookie | Depends entirely on the maintainer. Many are abandoned | Varies. Check whether it calls the official API before trusting it |
| Hosted API-based (Outstand) | A few minutes: sign in, approve OAuth, paste the URL | Hosted OAuth link flow. Managed Keys included, no developer app | Maintained against the official API, with token refresh handled | Official LinkedIn API. No scraping, no session cookies |
Connecting LinkedIn is an OAuth link flow: Outstand opens LinkedIn's own consent screen, you approve, and the connection is done. There is no LinkedIn developer app to register, no client ID or secret to manage, and no access token to store yourself - Managed Keys are included on every plan and cover LinkedIn.
This is also completable by an agent. Your agent calls get_auth_url, hands you the link, you sign in, and it picks the connection up from there. Bring your own OAuth app if you want your brand on the consent screen, but for LinkedIn nothing requires it.
This is a publishing server, not a data-mining one. It does not scrape profiles or company pages, does not touch Sales Navigator, Recruiter, or LinkedIn Ads, and does not export your connections or read your inbox. If you came looking for lead lists or profile enrichment, this is the wrong tool - what it does is let an agent create, schedule, publish, and measure LinkedIn posts through the official API.
No. LinkedIn has not shipped or announced an MCP server, so every LinkedIn MCP server available today is third-party. The options are open-source scrapers that authenticate with a browser session cookie, community servers listed in MCP directories, and hosted servers built on the official LinkedIn API such as Outstand.
Yes. Outstand's MCP server works with Claude Desktop, Claude Code, and Claude on the web, along with Cursor, Windsurf, ChatGPT, and any other MCP-compatible client. Add https://mcp.outstand.so/mcp as a remote MCP server or a custom connector and Claude gets tools for publishing to LinkedIn. The server speaks streamable HTTP, so nothing needs to run on your machine.
Create an Outstand account, connect LinkedIn through the hosted OAuth link, and add https://mcp.outstand.so/mcp to your MCP client. There is no developer app to register and no keys to generate. From there you ask your agent to post and it handles the rest.
Outstand's MCP server URL is https://mcp.outstand.so/mcp. It is one endpoint for every platform Outstand supports, not a LinkedIn-only URL, so the same connector also covers X, Instagram, YouTube, and the rest. Which accounts an agent can reach depends on what you have connected.
Yes. The create_post tool takes a scheduled time, so an agent can queue a LinkedIn post for a future slot up to 30 days ahead. Scheduled posts can be listed, edited by deleting and recreating, or cancelled with delete_post before they go out.
The MCP server is included with every Outstand account at no extra cost. Pricing is $19/month, 3,000 posts included, and posts published by an agent draw on the same quota as posts published through the REST API. Connected accounts are unlimited, and there is no per-seat pricing.
Yes. Every LinkedIn action goes through LinkedIn's documented API over an OAuth connection you approved. Nothing is scraped, no session cookie is used, and no automation is driven through the LinkedIn web app. That is the main practical difference from the scraper-based servers you will find on GitHub.
Every claim on this page is restated, dated, and citable on the facts page.
Sign in, approve LinkedIn once, paste the server URL into your client. Then just ask your agent to post.
https://mcp.outstand.so/mcp