Getting Started With the ContentIn LinkedIn MCP Server
The ContentIn LinkedIn MCP server is live. This guide covers what it does, how to connect it to Claude or Cursor in about two minutes, and how publishing from your AI conversation actually works.
If you write LinkedIn posts with Claude or Cursor, you know the gap: you draft in the AI, then leave it to copy-paste into LinkedIn, fix the formatting, and schedule by hand. Creation and publishing live in two separate places. A LinkedIn MCP server closes that gap: it connects LinkedIn to your AI client so the assistant can publish to your feed without you leaving the conversation.
The ContentIn LinkedIn MCP server is live and included in the Pro plan — setup takes about two minutes and the exact steps are below. (Facts verified 2026-07-29.)
Key takeaways
The ContentIn LinkedIn MCP server is live, included in ContentIn Pro, and connects to any MCP-compatible client — Claude Code, Claude Desktop, Cursor and others.
Setup is key-based: you create a key in your ContentIn settings and add one server entry to your client. No developer account, no config archaeology.
Publishing and scheduling always show you the exact post text and ask for your confirmation before anything reaches LinkedIn.
Not all LinkedIn MCP servers are alike: API-backed servers and session-scraping servers carry very different account risk.
Before you start: which LinkedIn MCP server do you need?
"LinkedIn MCP server" is a category, not one product. The options fall into three families — open-source servers from GitHub (mostly driving your logged-in session with a browser cookie), automation-platform bridges like Zapier or Composio, and hosted servers from LinkedIn content tools that act through an approved API with your authorization. Our glossary entry on LinkedIn MCP servers breaks down the three families and the API-versus-scraping distinction that should drive your choice. This guide covers the third kind: ContentIn's hosted server, where the AI that drafts your posts is also the product that has learned your voice.
What the Model Context Protocol actually is
Model Context Protocol (MCP) is an open standard, introduced by Anthropic in late 2024, that lets AI clients talk to external tools through a shared language. Instead of every AI app building its own custom LinkedIn integration, someone writes one MCP server for LinkedIn, and then any MCP-compatible client (Claude, Cursor, and others) can use it.
That portability is the real point. The same server works across any client that supports the protocol, so you're not locked into one assistant or waiting for each app to build LinkedIn support of its own.
What the ContentIn LinkedIn MCP server does
The server connects your AI client to your ContentIn profile — and through it, to LinkedIn via ContentIn's approved API access, authorized by your own account. In practice that means your AI conversation can:
list your recent posts and check a post's real analytics,
write a post in your voice (using the voice profile ContentIn has trained on your actual posts) and save it as a draft in the app,
repurpose an old post with a new angle and generate post ideas grounded in your content pillars,
capture a story, opinion or data point from any conversation straight into your ContentIn idea bank,
schedule and publish — with a confirmation step that shows you the exact text first.
If you want the wider landscape of what's possible beyond MCP, our Ultimate Guide to LinkedIn Automation Tools covers the broader toolkit this fits into.
Is this allowed by LinkedIn?
The short version: it depends on how a server connects, not on MCP itself. A hosted server acting through an approved API, with permissions you explicitly granted via OAuth, performs member-authorized actions on your own content — the same posture as using the tool's web app. A server that automates your logged-in session with a scraped cookie falls under the automated-access restrictions in LinkedIn's User Agreement and carries real account risk. Before installing any LinkedIn MCP server, check which kind you're holding; the glossary entry covers the distinction in more depth.
What you'll need
A ContentIn Pro account (every plan starts with a 7-day free trial) with your LinkedIn profile connected.
An MCP-compatible AI client — Claude Code, Claude Desktop, or Cursor are the common starting points.
Two minutes. There is nothing to install and no developer account on your side.
Setup: connect ContentIn to your AI client
Create your key. In ContentIn, open Settings and find the “Connect AI clients” section. Create a key — it's shown exactly once, so copy it right away and treat it like a password. Keys are per-profile and you can revoke one at any time.
Add the server to your client. In Claude Code it's one command:
claude mcp add contentin --transport http https://cms.contentin.io/mcp-server --header "X-MCP-Key: YOUR_KEY"For Claude Desktop and Cursor the same server URL and key go into the client's MCP configuration — the copy-paste blocks for each client are in the official setup guide.
Say hello. Ask your assistant to “list my recent LinkedIn posts using ContentIn.” If your posts come back, you're connected — everything else follows from natural conversation.
How authentication works (two layers, both yours)
It helps to know what's connected to what. Your LinkedIn account is connected to ContentIn the way it always has been: OAuth — “log in with LinkedIn and approve permissions,” using LinkedIn's self-serve posting permission (w_member_social) among others. Your AI client, in turn, authenticates to ContentIn with the key you created. The key is scoped to one profile: everything your assistant does acts as that profile, and revoking the key cuts the connection instantly without touching your LinkedIn authorization.
Publishing safely from a conversation
Anything that writes to LinkedIn — publishing or scheduling — runs a two-step confirmation: the server first returns the exact text it is about to post, your assistant shows it to you, and only after you confirm does the action go through. If the post changes between preview and confirmation, the confirmation is rejected and you see the new text again. You always see precisely what reaches your feed before it does. There's also a daily call limit per key, so a runaway automation can't drain anything.
Frequently asked questions
Is the ContentIn LinkedIn MCP server available now?
Yes — it's live and included in ContentIn Pro. Every plan starts with a 7-day free trial, and the setup guide gets you connected in about two minutes.
Which AI clients does it work with?
Any MCP-compatible client. Claude Code and Claude Desktop are the reference cases; Cursor and other MCP-enabled clients follow the same configuration pattern.
Do I need a LinkedIn developer account?
No. Your LinkedIn is authorized through ContentIn's approved app via OAuth, and your AI client uses a ContentIn key — no developer setup on your side.
Can the AI post something without me seeing it?
No. Publishing and scheduling always show you the exact text and require your explicit confirmation in the conversation before anything reaches LinkedIn.
What about other LinkedIn MCP servers?
Options exist — but they differ sharply in how they connect and what risk they carry. Read the glossary entry on LinkedIn MCP servers before installing anything that asks for your session cookie.
Create Engaging LinkedIn Content
Use ContentIn's AI Ghostwriter to write posts that resonate with your audience and build your personal brand effortlessly.