Live — included in the Pro plan

The LinkedIn MCP Server

Connect Claude, Cursor or any MCP client straight to LinkedIn. Publish, schedule and read your analytics from the chat — and write posts in your own voice with the ContentIn ghostwriter you already know. Included in Pro, one key per profile.

Included in Pro — start your 7-day trial Read the setup guide

Two minutes to connect: create a key in ContentIn, paste one line into your client.

Works with the clients you already use

  • Claude Code
  • Claude Desktop
  • Cursor
  • ChatGPT
  • Any MCP client

One remote server, connected once. Every MCP-speaking client gets the same set of tools — nothing to install, no plugin per app. We publish copy-paste setup instructions for Claude Code, Claude Desktop and Cursor; anything else that speaks Streamable HTTP MCP connects the same way.

What is a LinkedIn MCP server?

MCP (Model Context Protocol) is the open standard that lets AI assistants like Claude securely connect to external tools and data. A LinkedIn MCP server exposes LinkedIn as a set of tools your AI can actually use — so instead of describing what you want and copy-pasting the result, your assistant publishes posts, reads engagement data, and manages your content directly.

ContentIn's server is remote and key-based. You create an MCP key inside ContentIn, paste it into your client once, and that key authorises every call — scoped to a single profile, revocable from your settings at any moment. Your LinkedIn password never touches it, and the two tools that can put something in front of an audience — schedule_post and publish_post — always show you the exact text and wait for your confirmation before anything happens.

New to it? Start with the setup guide, or read the definition in our LinkedIn MCP glossary entry.

The tool surface

What your assistant can do

Eight tools, one connection, all of it part of Pro. Some wire LinkedIn itself into your AI — publishing, scheduling, analytics. The rest wire in your ContentIn ghostwriter: your voice, your substance, your rules.

Only in ContentIn

Posts that sound like you — not like AI

write_post_in_my_voice

ContentIn learns your voice from the posts you've actually written: your hooks, your rhythm, the phrases you keep coming back to. Brain-dump into your AI client and get back a draft you'd put your own name on.

Only in ContentIn

Every AI conversation teaches your ContentIn

capture_substance

Hit a story worth telling, a strong opinion, a number you keep quoting? Save it from wherever you happen to be working. Your substance bank keeps growing outside the app — and every future draft inherits it.

The ghostwriter layer

Everything ContentIn does today, callable from your AI client. It runs on the model we've trained on your writing — which is the part a generic LinkedIn wrapper can't copy.

Never open a blank chat again

generate_ideas

Ideas drawn from your topics, your audience and what's already resonated — not generic prompts anybody could have gotten.

Turn one good post into another

repurpose_post

Take something that landed and rework it from a fresh angle that still sounds like you.

Publish & schedule

Your LinkedIn account, exposed to your assistant as tools it can actually call — so the draft you just approved doesn't need a copy-paste to go anywhere.

Publish the moment it's ready

publish_post

Your assistant shows you the final text, you confirm, it goes live. Nothing is ever published without your explicit yes.

Queue it for the right moment

schedule_post

Put a post on the calendar for a specific time, without leaving the conversation — same confirmation step, nothing queued behind your back.

See your whole pipeline in one ask

list_posts

Drafts, scheduled and published posts, straight into the chat. No tab-switching to check what's queued.

Analytics

The feedback loop, in the same conversation that writes the next post — so your AI can reason about performance instead of guessing at it.

Ask why a post worked

get_post_analytics

Impressions, members reached, reactions, comments and shares per post — the raw evidence behind what landed and what didn't.

Every tool here ships with the Pro plan, one key per profile. The setup guide shows what each one looks like from the chat, with example prompts.

Included in Pro

Your ghostwriter, wired into your AI tools — for every profile you run

The MCP server comes with the ContentIn Pro plan — nothing to buy separately. It's scoped per profile: every profile on your account gets its own key, so the assistant you're talking to is always working with that profile's voice, substance bank and calendar — and if you run clients, each client profile gets its own key, which makes it natural to keep every client in a dedicated AI project.

  • Part of Pro

    Not an add-on and not priced separately — the MCP server ships as part of the Pro plan.

  • One key per profile

    Each profile gets its own key: its voice model, its substance bank, its queue. Revoke it any time.

  • Built for running several

    Agency or multi-brand? Connect each client profile where you actually work on it.

Frequently asked questions

What is a LinkedIn MCP server?
It's a Model Context Protocol server that lets AI assistants like Claude connect to LinkedIn as a tool — so they can post content, read analytics, and manage your presence directly from your AI assistant.
Is it secure?
Yes. You authorise with an MCP key you create inside ContentIn — we never see your LinkedIn password, the key is scoped to a single profile, and you can revoke it from your settings at any time. Scheduling and publishing are confirmation-gated on top of that: your assistant has to show you the exact text and get your explicit go-ahead before anything reaches LinkedIn.
Which AI clients does it work with?
Any MCP-compatible client — Claude Desktop, Claude Code, Cursor, ChatGPT and anything else that speaks the Model Context Protocol over Streamable HTTP. It's a remote server, so you connect it once instead of installing something per app. Copy-paste config for each client is in the setup guide.
Which plan includes the MCP server?
Pro. The whole tool surface — publishing, scheduling, analytics and the ghostwriter tools — comes with the ContentIn Pro plan rather than being sold separately. It's scoped per profile: every profile on your account gets its own key, including each client profile if you run an agency, so you can keep each one in a dedicated AI project.
How is this different from a generic LinkedIn MCP server?
Anyone can wrap the LinkedIn API, and moving text from a chat window to your feed is the easy part. The difference is whose voice writes the post: ours is the only one where the model drafting it has learned from the posts you've actually published — your hooks, your rhythm, the phrases you keep coming back to. And it runs both ways: anything you capture in a conversation — a story, a strong opinion, a rule you never want broken — lands in your substance bank and shapes every future draft, in your AI client and in ContentIn.
Can I try ContentIn's AI writing before I subscribe?
Yes. The MCP server needs a Pro plan, but the writing engine behind it is open to everyone. Our free AI LinkedIn post generator drafts posts from your own LinkedIn profile in seconds, no login required, so you can see the voice-first approach for yourself today. The MCP server is that same engine wired into your AI client.
Is it available now?
Yes — it's live, and it's part of the Pro plan. Create an MCP key in your ContentIn settings and paste it into your client; the setup guide walks through it for Claude Code, Claude Desktop and Cursor.

Connect your AI to LinkedIn

The MCP server is part of the Pro plan. Start a trial, create your key, and your assistant is writing and publishing in your voice a couple of minutes later.

Included in Pro — start your 7-day trial Read the setup guide