Live — included in the Pro plan

The ContentIn LinkedIn MCP Server

The ContentIn LinkedIn MCP connects Claude, Claude Code, 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 See the two-minute setup

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. Copy-paste config for Claude Code, Claude Desktop and Cursor is further down this page; 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. For the plain-language definition, read our LinkedIn MCP glossary entry.

The ContentIn LinkedIn MCP is remote and key-based. You create an MCP key in the Connections tab of your ContentIn profile, paste it into your client once, and that key authorises every call — scoped to a single profile, revocable from that same tab 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.

The tool surface

What an MCP server for LinkedIn lets your assistant do

Eleven tools, one connection, all of it part of Pro. Some wire LinkedIn itself into your AI — publishing, scheduling, analytics, the people engaging with you. 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.

Send the picture with the post

attach_images

Attach up to 5 images to a draft — a public image URL or the file itself — then publish or schedule it as usual. JPG, PNG or WEBP, 8 MB each; one image goes out as a single image, two or more as a LinkedIn multi-image post. No GIFs, video or PDFs. Fair use: 30 images an hour, 100 a day per key.

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 & audience

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

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.

See who's actually engaging

list_leads

Everyone who reacted to, commented on or shared your posts — name, headline, profile, ContentIn's ICP fit score, lead status and the posts that pulled them in. Filter by status, score or last interaction. A single reaction is enough to create a lead; an unscored one means not scored yet, not a poor fit.

Find the comments you left

list_my_comments

The comments you wrote on other people's posts, with a link back to each one, what it got, and the post it sits under. Read from a daily sync, so the last day can still be missing — and only the counts, never who reacted.

Every tool here ships with the Pro plan, one key per profile. Your assistant picks the right one from what you ask — you never call them by name. Connecting takes two minutes; the steps are just below.

Included in Pro

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

ContentIn's LinkedIn MCP server comes with the 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.

Two-minute setup

Get started with the ContentIn LinkedIn MCP in two minutes

The same remote server works in Claude Desktop, Claude Code, claude.ai and Cursor. Nothing to install — a key and one config entry, and your assistant is working with your profile.

  1. 1

    Create an MCP key in ContentIn

    Open the Connections tab of your ContentIn profile, find Connect AI clients under your connected LinkedIn profile and create a key. It starts with cimcp_ and is shown once — copy it straight into your client.

  2. 2

    Paste the server URL and your key into your client

    The LinkedIn MCP server URL is the same for every client; the key travels in the X-MCP-Key header.

    Server URL
    https://mcp.contentin.io/mcp-server
    Auth header
    X-MCP-Key: YOUR_KEY

    For Claude Desktop (claude_desktop_config.json) and Cursor (~/.cursor/mcp.json), add this entry with your key filled in: 

    {
  "mcpServers": {
    "contentin": {
      "type": "http",
      "url": "https://mcp.contentin.io/mcp-server",
      "headers": {
        "X-MCP-Key": "YOUR_KEY"
      }
    }
  }
}

    In Claude Code it's one terminal command: claude mcp add contentin --transport http https://mcp.contentin.io/mcp-server --header "X-MCP-Key: YOUR_KEY". In claude.ai in the browser, add https://mcp.contentin.io/mcp-server?mcp_key=YOUR_KEY as a custom connector instead, since browser connectors can't send headers.

  3. 3

    Try a first prompt

    Restart your client so it picks up the server, then ask it something real. Your assistant chooses the right tool from the eleven above — you never call them by name.

    “What have I got scheduled for next week, and what did my last three published posts do?”

Per-client walkthroughs, the full tool list with example prompts, and troubleshooting live in the LinkedIn MCP setup guide.

Frequently asked questions

What is the LinkedIn MCP server URL?
ContentIn's remote LinkedIn MCP server URL is https://mcp.contentin.io/mcp-server. Point Claude Desktop, Claude Code, Cursor or any Streamable HTTP MCP client at that URL and send your ContentIn MCP key in the X-MCP-Key header; in claude.ai's browser connector, which can't send headers, use https://mcp.contentin.io/mcp-server?mcp_key=YOUR_KEY instead. There is no LinkedIn-hosted MCP URL — every LinkedIn MCP server is run by a third party, and this one is ours.
Is there a LinkedIn MCP for Claude?
Yes. The ContentIn LinkedIn MCP works in Claude Desktop, Claude Code and claude.ai, as well as Cursor, ChatGPT and any other client that speaks the Model Context Protocol over Streamable HTTP. It's a remote server, so you connect it once rather than installing something per app — the three steps are in the Get started section above, with copy-paste config for each client.
How do I get started with the LinkedIn MCP server?
Three steps, about two minutes. First, create an MCP key in ContentIn on the Profiles page under the Connections tab (it needs a Pro plan and a connected LinkedIn profile). Second, add https://mcp.contentin.io/mcp-server to your client with the key in the X-MCP-Key header. Third, restart the client and ask it something real — list your scheduled posts, write a draft in your voice, or pull last week's analytics.
Can the ContentIn LinkedIn MCP read my LinkedIn analytics?
Yes, through LinkedIn's official API for the LinkedIn account connected to your ContentIn profile. get_post_analytics returns impressions, members reached, reactions, comments, shares and engagement rate per published post; list_leads shows everyone who reacted, commented or shared, with ContentIn's ICP fit score; list_my_comments returns the comments you left on other people's posts and what they earned. The tools cover your personal profile — company-page analytics are not part of the tool surface today.
Does LinkedIn have an official MCP server?
No — LinkedIn doesn't publish an MCP server of its own, so every LinkedIn MCP server you'll find is third-party, including ours, which runs on the official LinkedIn API through your connected account rather than on scraping. For how the available servers differ, see LinkedIn MCP servers compared.
Is it secure?
Yes. You authorise with an MCP key you create in ContentIn, on the Profiles page under the Connections tab — we never see your LinkedIn password, the key is scoped to a single profile, and you can revoke it from that same tab 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 plan includes the MCP server?
Pro. The whole tool surface — publishing, scheduling, analytics, your comments and leads, 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.

Connect your AI to LinkedIn

The ContentIn LinkedIn MCP 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