The LinkedIn MCP server thatdoesn't need your LinkedIn account
Octolens monitors LinkedIn posts and comments for your keywords, filters the noise with AI, and serves clean mentions to Claude, ChatGPT, and Cursor over MCP. No session cookies, no scraping on your login, no account risk.
5-minute setup • OAuth sign-in, read-only • MCP on every planTeam is evaluating social listening tools this month. Brandwatch feels like overkill — what are people actually using?
Post · 31 comments · 2h ago
Comment: “We moved to a tool that catches the LinkedIn posts where nobody tags us — game changer”
Comment · under a post with 213 reactions
Trusted by brands people talk about online
LinkedIn Is the Hardest Platform to Monitor
It's where B2B buyers ask for recommendations and compare vendors in public — and it's the one platform every monitoring approach struggles with.
There is no public API
LinkedIn doesn't offer a keyword-search API to third parties. There's nothing official to build on — which is why almost every "LinkedIn MCP server" you'll find is a workaround.
Cookie scrapers risk your account
Most open-source LinkedIn MCPs authenticate with your li_at session cookie. Sessions expire, coverage is limited to what your account can see, and automated access violates LinkedIn's User Agreement — accounts get restricted for it.
You're only notified when tagged
Most brand mentions on LinkedIn happen in comment threads under other people's posts. No tag, no notification — the highest-intent conversations are invisible from your own feed.
Octolens fixes this upstream: LinkedIn collection runs on our side, against posts and comments, for the keywords you choose. Your AI tools get clean, scored data over MCP — and your LinkedIn account is never involved.
From LinkedIn Thread to Answer in Your AI Tool
One pipeline: Octolens does the collection and filtering, MCP does the delivery. You just ask.
Add keywords
Your brand, competitors, and the category phrases your buyers use — plus negative keywords for noise.
octolens.com → KeywordsOctolens collects
Posts and comments matching your keywords, with a 7-day backfill per keyword and continuous collection after. Hourly refresh on Pro, real-time on Scale.
posts + commentsAI scores everything
Every mention arrives scored for relevance and sentiment, tagged with labels like buy_intent, competitor_mention, or complaint.
"relevanceScore": "high"Your assistant queries it
23 MCP tools: list and search mentions, run analytics, manage keywords and feeds — from Claude, ChatGPT, or Cursor.
list_relevant_mentionsFull tool reference in the MCP docs. The same data is available over the REST API and webhooks — on every plan. Prefer alerts and a feed over an AI assistant? See LinkedIn monitoring.
Connected in Five Minutes
No LinkedIn credentials at any step. You need an Octolens account (7-day free trial) and an MCP-compatible tool.
Add your keywords in Octolens
Brand, competitors, category terms. LinkedIn collection (posts + comments) starts with a 7-day backfill.
Connect your client
One URL for every tool. Authentication is a browser sign-in to your Octolens account — there's no API key or token to paste.
Ask
Try: “show linkedin mentions from today” — you should see your first scored mentions come back.
claude mcp add --transport http octolens \
"https://app.octolens.com/api/mcp/v2"
# then, inside Claude Code:
/mcp # → octolens → AuthenticateRun the command, then run /mcp inside Claude Code, select octolens → Authenticate, and sign in when the browser opens.
Verify it works
@octolens show linkedin mentions from todayNew keywords can take up to 24 hours to index fully — check mentions in the Octolens dashboard first if nothing comes back.
What You'll Actually Ask It
Copy-paste these into Claude, ChatGPT, or Cursor once you're connected.
7-day free trial · No credit card required
MCP Is One Door Into the Same Data
Octolens is the data layer for what people say online. Your assistant queries it over MCP — your team and your agents can consume it everywhere else too.
Webhooks → your stack
Push instead of poll: scored LinkedIn mentions delivered to Slack or your own endpoint as they're found. Wire buying-intent posts straight into your CRM.
Explore webhooks →Agent skills
Ready-made playbooks agents can run over the MCP server — mentions to Linear issues, churn signals to CS, public conversations to pipeline.
Browse agent skills →API → your product
The same LinkedIn data over one REST endpoint with one schema across 15+ sources. Build monitoring into your own product or internal tools.
Build with Octolens →Your Three Options for LinkedIn via MCP
LinkedIn has no public keyword API, so every option is a trade-off. Here's the honest version.
| Octolens MCP | Cookie-based LinkedIn MCP | Manual monitoring | |
|---|---|---|---|
| LinkedIn login required | No | Yes — your session cookie | Yes |
| Account restriction risk | None | Real risk | None |
| Keyword monitoring across LinkedIn | Yes | Limited & fragile | Tagged mentions only |
| Comment coverage | Posts + comments | Partial | Only if tagged |
| AI relevance & sentiment scoring | Built-in | You build it | Your eyeballs |
| Historical data & trends | Yes | Limited | No |
| Other platforms via the same server | 15+ sources | LinkedIn only | — |
| Cost | $199/mo ($159/mo annual) | Free + your time + account risk | Free + hours every week |
Cookie-based servers are fine for experimenting with MCP itself. Manual monitoring works until the first untagged comment thread recommends your competitor. If LinkedIn actually matters to your pipeline, monitor it properly.
LinkedIn MCP Server & Monitoring, Answered
Setup, account safety, and coverage — everything about monitoring LinkedIn from Claude, ChatGPT, or Cursor.
No. LinkedIn doesn't offer a public API for keyword monitoring, and Octolens never asks for your LinkedIn login, session cookie, or API credentials. Octolens handles LinkedIn data collection on its side — you configure keywords and connect the MCP server with a browser sign-in to your Octolens account.
Both posts and comments. Comment coverage matters more than most people expect: the majority of brand mentions on LinkedIn happen in comment threads under other people's posts, where LinkedIn never notifies you unless you're tagged.
No. Nothing runs through your LinkedIn account — Octolens doesn't use your login or session cookies. This is the key difference from most open-source LinkedIn MCP servers, which authenticate with your personal li_at session cookie and can get your account restricted for automated access.
No — MCP access is read-only by design. You can monitor mentions, analyze them, and draft replies in Claude, but you post them yourself on LinkedIn. That keeps a human in the loop and your account safe from automation flags.
Depends on your plan: hourly refresh on Pro ($199/mo, or $159/mo billed annually), real-time on Scale ($599/mo, or $499/mo billed annually). For LinkedIn, hourly is enough to reply while a post is still in the algorithm's distribution window.
Yes. Add competitor names and category phrases like "[competitor] alternative" as keywords. You'll see complaint threads, comparison discussions, and evaluation posts — often before the competitor does.
Claude Code, Claude Desktop and Web, ChatGPT, Cursor, and any other MCP-compatible client. It's one remote server URL with OAuth sign-in — there's no API key to manage and nothing to run locally.
Every new keyword gets a 7-day backfill, then collects continuously — your archive builds from the day you add a keyword. That's enough history for trends, sentiment shifts, and share-of-voice over time.
Give your AI tools ears on LinkedIn
Add your keywords, connect the MCP server, and ask your assistant what LinkedIn is saying about you — all inside the 7-day free trial.
No credit card required · API access on all plans · Cancel anytime