Axel Schapmann
Floriane Bobée
Benjamin Allouch
Victor Grandchamps
Loved by 4,000+ users

LinkedIn MCP server for Claude, ChatGPT and Perplexity

Connect Claude, ChatGPT, Perplexity, Gemini or Cursor to your MyFeedIn account: your assistant reads the analytics behind your own posts, searches the comments you left on other people's, and builds outreach campaigns from the people you saved.

Connected to MyFeedIn

What worked on my LinkedIn this past month?

compare_periodsget_top_performing_posts

Compared to the previous 30 days:

  • Impressions are up 42% and comments up 31%.
  • Your 3 best posts all open with a question and stay under 120 words.
  • Tuesday-morning posts outperform your average by 2.1x.

Want me to draft the next one using what's working?

Add the LinkedIn MCP server to Claude, ChatGPT or Perplexity

You connect it once. After that you just ask, and your assistant does the work inside your own account, from your real numbers rather than generic LinkedIn advice.

mcp.myfeedin.co
Add connectorConnected

1. You connect once

Paste the MyFeedIn server URL into your assistant and approve the consent screen. We host the server, so there is nothing running on your machine and nothing to keep up to date.

Find the people who commented on my best post this quarter and start a campaign for them.

2. You ask in plain language

Ask the way you would ask a teammate: name a period, a topic, a person. No command to memorise, no parameter to fill in.

search_people
create_campaign
set_campaign_steps
Draft ready, nothing sent

3. It works in your account

Your assistant picks the tools it needs and calls them one at a time. The campaign lands in your dashboard as a draft: nothing goes out until you launch it yourself.

What a LinkedIn MCP server actually gets you

Four things you cannot do with a chat window alone, because the model has no idea what happened on your account.

Find out what actually worked

Ask what changed this month and get the real deltas: impressions, comments, best day, best hour, best post length. From your own history, not from a LinkedIn best-practices article.

compare_periodsget_top_performing_postsanalyze_engagement_patterns

Draft in your own voice

Your assistant reads how you actually write, your structure, your recurring words, your hooks, then drafts from that. It can also surface opening lines that worked and that you have not reused in months.

summarize_my_voicefind_unused_hooks

Schedule your next post from the chat

Ask for a post in your voice, and your assistant saves it as a draft in your calendar and schedules it for the slot you confirm. MyFeedIn publishes it on LinkedIn at that time, first comment included.

summarize_my_voicecreate_post_draftschedule_post

See what your commenting is worth

Nothing else measures the comments you leave on other people's posts. Ask which ones landed, on whose posts, and whether the time you spend engaging is paying you back.

list_my_commentssearch_my_commentssearch_people

Turn a conversation into a campaign

Name the people you want to reach, and your assistant builds the campaign: the audience, the sequence, the delays. It lands in your dashboard as a draft, and nothing goes out until you launch it.

search_peoplecreate_campaignset_campaign_steps

Is there an official LinkedIn MCP server?

No. LinkedIn does not publish one, and its public API does not expose your feed, your post analytics or your comments. Every LinkedIn MCP server is third-party, and they come in three kinds.

What a LinkedIn MCP server is

A Model Context Protocol server is a small service an AI assistant can call for tools. A LinkedIn MCP server gives Claude, ChatGPT or Cursor tools that read LinkedIn data, so the model answers from what actually happened on an account instead of generic advice.

Where MyFeedIn sits

MyFeedIn's server is the hosted kind. It connects over OAuth, holds no LinkedIn cookie and never scrapes LinkedIn. It answers from the data already in your MyFeedIn account: your posts and their analytics, the comments you left, your feeds and saved people, and on the Growth plan your outreach campaigns.

Open-source scrapersData-extraction APIsMyFeedIn
How it reaches LinkedInYour logged-in browser sessionCloud scrapersYour MyFeedIn account
Where it runsOn your machineHostedHosted, one URL
How you log inSession cookieAPI keyOAuth, approved in your browser
Your own post analytics
Your comments and saved people
Bulk profile and company extraction
Outreach campaigns from the chatGrowth plan
Can post or message as youSome can
PriceFreePer requestIncluded in paid plans

Pick a scraper or an API when the job is pulling other people's profiles in bulk. Pick MyFeedIn when the job is your own account: what you posted, how it performed and who you engage with.

LinkedIn MCP server URL

MyFeedIn is a remote server, so there is nothing to install. Paste this URL into any client that supports remote MCP servers with OAuth, approve the connection in your browser, and the tools appear. No API key to copy.

https://mcp.myfeedin.co

Works with every major assistant

Use whichever one you already pay for. They all get the same 31 tools and the same view of your account.

https://mcp.myfeedin.co

34 LinkedIn MCP tools on your own account

Grouped by what you would ask for. Campaign tools need the Growth plan; everything else works on any active plan.

Posts

07
  • list_my_posts
  • search_my_posts
  • get_top_performing_posts
  • search_top_performing_posts
  • get_posts_by_period
  • get_posts_one_year_ago
  • get_post

Analytics

04
  • get_post_analytics
  • compare_periods
  • analyze_engagement_patterns
  • generate_share_card

Comments

02
  • list_my_comments
  • search_my_comments

Feeds & people

03
  • list_my_feeds
  • get_feed_people
  • search_people

Workspace

01
  • list_workspace_members

Voice & drafting

02
  • summarize_my_voice
  • find_unused_hooks

Publishing

05
  • list_my_scheduled_posts
  • create_post_draft
  • update_post_draft
  • schedule_post
  • unschedule_post

Campaigns (Growth)

07
  • list_my_campaigns
  • get_campaign
  • create_campaign
  • set_campaign_steps
  • add_profiles_to_campaign
  • pause_campaign
  • resume_campaign

Client compatibility

03
  • search
  • fetch
  • ping

Built to be trusted

Your LinkedIn presence is your asset. Here is exactly what a connected assistant can and cannot do with it.

Every tool, every scope and the OAuth flow, written down. The REST API covers the same data with an API key if you would rather script it.

It only publishes what you schedule

Nothing goes out on its own. Drafts stay drafts, a post is only published at the slot you confirmed, and campaigns are Growth-plan tools.

No scraping, no session cookie

It never touches your LinkedIn session. Only the data already in your MyFeedIn account, nothing scraped from LinkedIn.

You approve every connection

You pick whether it sees your personal account or one workspace. It can never see the other.

Revocable in one click

Settings, then Connected apps, lists every assistant. Revoking cuts it off immediately.

Try these prompts

Written to work as they are. Copy one in once you are connected, and swap the bracketed parts for your own topic.

Analytics

Compare my last 30 days on LinkedIn to the 30 days before. Show me the 3 metrics that moved the most (impressions, comments, reactions) with the percent change. Then pick my single best post in that window and break down what made it work: hook, length, posting time, and how it compares to my average.

Voice

Read my last 20 posts and summarize my voice in 5 bullets: average post length, opener style, formatting habits (line breaks, bullets, emoji use), recurring themes, and the 3 hook patterns that drive the most engagement. End with a 2-line guide I can paste into any AI tool to write in my style.

Hooks

Pull 5 hooks from my posts that got more than 500 impressions in the past year and that I haven't reused in the last 90 days. Adapt each one to a post about [topic] without changing the hook's structure. Keep every hook under 12 words.

Repurposing

Find my 3 best-performing posts from 11–13 months ago. For each one, give me: the original hook, two reasons it worked, and a fresh angle to repurpose it today (not a copy-paste rewrite). Order them by potential, easiest repurpose first.

Drafting

Draft a LinkedIn post in my voice about [topic]. 150 words. Structure: hook under 10 words, two beats with one concrete example each, close ending in a question. Plain text only, no markdown, no emojis. Pull the hook pattern from one of my top 5 performers and tell me which one you used.

Timing

Analyze my engagement patterns over the past 90 days: best days, best hours, and how post length correlates with engagement. Then give me a simple posting schedule for next week (day, time, suggested length) based only on my own data, not generic best practices.

Engagement

List the people in my [feed name] feed, then check my recent comments: who in that feed have I not engaged with in the last 30 days? Give me the top 5 to reconnect with, and for each one a reason based on their headline.

Planning

Look at my top 10 posts from the past year and group them into 3 to 5 recurring themes, ranked by average engagement. For each theme, suggest 2 new post ideas I haven't covered yet. Format it as a 2-week content calendar.

Publishing

Draft a LinkedIn post in my voice about [topic]: 150 words, hook under 10 words, plain text, no emojis. Save it as a draft, then schedule it for next Tuesday at 08:30 in my timezone with a first comment that links to [URL]. Confirm the exact slot it will go live and give me the editor link.

Outreach

Create a draft campaign called [name]. Sequence: a connection request with a short note using my first name variable, then a message 3 days later that opens with a spin variation and stays under 60 words. Write both in my voice, based on my last 20 posts. Then add these profiles: [paste 3 profile URLs], and tell me who was newly created versus already in my CRM, and who got skipped for being active in another campaign.

Ready to save time on LinkedIn?

Try it free for 7 days, no credit card required. Cancel anytime.

Starter

Seats:
1
10US dollars/month

Solo creators building presence on LinkedIn

Your posts

  • Write, schedule and publish
  • Track your post and comment analytics

Your network

  • Unlimited custom feeds
  • Save people, take notes, build your pipeline

7-day free trial · No credit card required

Growth

Seats:
1
19US dollars/month

Founders & teams who post and prospect every week

Everything in Starter

Outreach

  • 30 invitations or messages a day
  • Multi-step sequences
  • Steal prospects from competitors' posts

Cancel anytime

Wait... you don't want a subscription?

We've got something for you.

Lifetime Deal

Pay once, use forever.

  • All Starter features included
  • Outreach campaigns not included
149US dollarsOne-time

Frequently asked questions

Can't find the answer you're looking for? Send us a message and we'll help you out.

No. LinkedIn does not publish an MCP server, and its public API does not expose your feed, your post analytics or your comments. Every LinkedIn MCP server you will find is third-party: open-source projects that drive your own logged-in browser session, data-extraction APIs that run cloud scrapers, or hosted servers like MyFeedIn's that read an account you already own.
No. The server never touches your LinkedIn session and holds no cookie. It only reads the data already in your MyFeedIn account, over OAuth, with a connection you can revoke at any time.
Yes. Connecting MyFeedIn to any external MCP client requires an active MyFeedIn paid plan (lifetime or active subscription). Free accounts can still use the in-product agent, but external connections are gated. You'll see a clear upgrade prompt during the connection flow if your plan doesn't qualify.
No. There is no tool to publish a post, write a comment or send a direct message. Your assistant can analyze, summarize, search and help you draft, but you stay in control of what gets published. The exception is outreach: on the Growth plan it can build a campaign end to end, meaning create the draft, write the sequence and add people to it. A draft sends nothing, and the first launch of a campaign is always your click in the dashboard. After that it can pause and resume the campaign on request, and adding people to a campaign that is already running does start sending to them. The tools say so when they do.
Your published LinkedIn posts and engagement, post analytics, your comments on others' posts, your custom feeds and the people you've saved in them. On the Growth plan it also reaches your outreach campaigns: their sequences, their audience and their results. Nothing about your inbox, your network beyond saved people, or anything you haven't already imported into MyFeedIn.
Anything that speaks the Model Context Protocol with OAuth 2.1: Claude, ChatGPT, Perplexity, Cursor, the Gemini CLI, plus any other MCP-compatible client. The server uses standard PKCE + Dynamic Client Registration, so no custom integration code is required.
From your MyFeedIn dashboard → Settings → Connected apps. You'll see every active MCP connection and can revoke any of them in one click. The token is invalidated immediately on the server side.
Only what your assistant pulls in to answer your question, the same as any other context you would paste into a chat. We don't proactively send anything, and we don't store your prompts or the assistant's responses on the MyFeedIn side. What happens to the conversation itself is governed by your AI provider's own policy.
If you're in one or more workspaces, the consent screen lets you pick which scope to bind the connection to. A personal connection sees your own LinkedIn data; a workspace connection sees that workspace's data. Tokens are scoped, so switching scope means revoking and reconnecting.

Ready to reclaim your LinkedIn time?

Join hundreds of professionals who've already transformed their LinkedIn experience.