How to Connect LinkedIn Pages to Claude with MCP
Connect your LinkedIn Company Page to Claude with the Data Bloo MCP and pull follower growth, impressions and engagement straight from the chat, no exports, no screenshots. It runs on LinkedIn's official Pages API, it's read-only, and here's the 2-minute setup.
The Data Bloo connector
Open the Data Bloo listing in Claude's directory, hit Connect and sign in. There's no server URL, no client ID and no API key anywhere in this setup. Everything below is just where to click.
What connecting LinkedIn Pages to Claude actually means
You can ask Claude about your LinkedIn Company Page and get a real answer, pulled from your actual page analytics, in seconds. Type "how did our LinkedIn page do last month" and Claude reads your numbers and tells you, no export, no screenshot of the analytics tab. The connection runs through the Data Bloo MCP, takes about two minutes to set up, and it's read-only, so Claude can analyze your page but can never post, comment or change anything.
One thing worth knowing before you search any further: there is no official LinkedIn MCP. What you'll mostly find are community servers that scrape public profiles using your login session, useful for prospecting research, risky for your account, and blind to your page analytics. Want Claude to read, analyze and report on your company page, follower growth, impressions, engagement, demographics, through LinkedIn's official Pages API, blended with your other channels and feeding your Data Studio dashboards? That's Data Bloo, and that's what the rest of this guide covers.
Stop screenshotting analytics. Start asking.
The same LinkedIn Page you already trust for your Data Studio reports, now answering questions in a chat. No exports, no analytics tab to dig through.
Ask, get instant answers
"Which LinkedIn posts drove the most engagement last week?" Claude pulls the numbers and explains them.
Reports inside the chat
Ask for a 30-day LinkedIn Page view and get tables plus a summary ready to share, no Data Studio setup.
Client-ready summaries
"Turn last month's LinkedIn Page performance into an executive summary." Paste it into Slack, email or a doc.
Diagnose dips fast
"Why did our impressions drop this week?" Claude looks across posts, dates and engagement and explains it.
Blend beyond LinkedIn
Line your organic page up against LinkedIn Ads, Instagram Insights or Facebook Insights in one answer.
Connect once, use everywhere
The same LinkedIn Page you linked for Data Studio is instantly available to Claude, zero duplicate setup.
LinkedIn Pages, plus every other connector
Already connected in Data Bloo? It's instantly available to Claude, connect once, use everywhere.
Three ways to connect LinkedIn to Claude
There are three real options, built for different people. Here's the honest version, including the case where the answer isn't us, so you pick the right one the first time.
A connector like Data Bloo
Paste one URL, sign in once, ask in plain English. Built on LinkedIn's official Pages API, read-only, no scraping, no cookies. Blends across channels, and the same connection feeds your Data Studio reports.
A community LinkedIn MCP
LinkedIn doesn't publish an official MCP, so the community filled the gap, linkedin-mcp-server is the one you'll find first. It logs in with your session cookie and scrapes profiles, companies and jobs. Clever, and free. The trade-off: it's against LinkedIn's terms, it risks your personal account, and it can't see your page analytics.
LinkedIn's native export
Open the page as an admin, go to Analytics, export the XLS, upload it to Claude. Free, official, and it works once. Then you do it again next week, tab by tab, for every page you manage.
Data Bloo vs a community MCP vs a manual export
The bottom line: if you want Claude to research people and companies on LinkedIn, a community MCP does that, with real risk attached. If you want Claude to read and report on your own company page, safely, across LinkedIn and everything else, and feed the same data to your dashboards, that's Data Bloo.
When a community LinkedIn MCP is enough
Data Bloo isn't the right tool for everyone. There's no official LinkedIn MCP, but the community built its own, linkedin-mcp-server is the best-known, and it does things we don't: it reads public profiles, company pages and job listings, so Claude can research a prospect before a call or scan candidates for a role. If your job is sales research and recruiting, not page reporting, that's a real capability and the open-source route is worth a look.
Go in knowing two things. First, how it works: there's no sanctioned API behind it, so it signs in with your personal session cookie and scrapes what a browser would see, from a server you install and keep running yourself. Second, the risk: automated scraping is against LinkedIn's user agreement, and LinkedIn actively detects it. The account on the line is yours, the one with your network and your job history. That's a real trade for real convenience, just make it deliberately.
Data Bloo does the other half, and does it safely. It reads your company page's actual analytics, follower growth, impressions, engagement, demographics, through LinkedIn's official Pages API with page-admin OAuth, blends them with the rest of your marketing, and feeds the same Data Studio dashboards you already send clients. No scraping, no cookie, nothing LinkedIn could flag.
What you need
Three things, and you probably already have them.
How to connect LinkedIn Pages to Claude
Pick your Claude client. Desktop & Web are easiest for most marketers; Claude Code is a one-liner for developers.
Go straight to Data Bloo in the Claude directory. You’ll see what it does and every source it supports.
Open Data Bloo in Claude →The Connect button sits at the top right of the listing. It works the same on claude.ai and Claude Desktop.
Claude opens Data Bloo’s sign-in page. Log in with your Data Bloo account and approve read access. Nothing in your accounts can be changed.
Try: "Using Data Bloo, show me my key metrics for the last 30 days and what changed." Claude returns a table plus a short analysis you can share.
Open your terminal and run:
claude mcp add --transport http databloo https://mcp.databloo.com/mcp
Next time you start a Claude Code session, Claude opens your browser to sign in to Data Bloo. Sign in once, the connection persists across sessions.
Run /mcp list, you should see databloo with status connected.
Confirm it works: in a fresh chat, ask "Using Data Bloo, list all the data source accounts I have connected." If Claude returns your accounts, you're fully connected.
Take the MCP for a spin
Walk through connecting LinkedIn Pages to Claude and pulling a report, no signup, right here in the page.
Seven read-only tools, why this can't get you banned
You just ask in plain language, Claude picks the right tool. The typical flow: list_data_sources → get_connector_accounts → list_fields → query_data.
get_userlist_data_sourcesget_connector_accountslist_fieldsquery_datalist_accountsget_datesRead-only, always. Claude can pull and analyze your LinkedIn Page, it can never publish a post, reply to a comment or send a message. No scraping, no cookies, nothing LinkedIn could ever flag.
Read-only safety and your dashboards, in one connection
The scraping-based tools make you choose: hand an AI your LinkedIn login, or keep exporting by hand. Data Bloo doesn't ask you to choose. It reads through the official API, it reports, and the exact same connection already powering your Data Studio dashboards now answers questions in Claude.
It can't touch your page, or your account
All seven tools are read-only, and the data comes through LinkedIn's official Pages API with admin-approved OAuth, not a session cookie and a scraper. Claude can't post, comment, message or connect on your behalf, so there's no wrong instruction that could put your page, or your personal profile, at risk.
One connection, two surfaces
The LinkedIn Pages source you built for Data Studio is the same one Claude reads. No second setup, no second bill, and the numbers Claude quotes always match the dashboards you send clients. It's the one thing a profile-scraping tool structurally can't give you.
What Claude actually gives you back
Three real prompts and the kind of answer Claude returns once LinkedIn Pages is connected through Data Bloo, numbers, then a plain-language read.
Claude: Last 30 days on your LinkedIn Page, 148,230 impressions, 4,127 clicks and 612 new followers. Engagement rate landed at 5.4%, up 9% on the prior period.
Claude: Top post, the customer-story carousel, 18,940 impressions, 214 reactions and a 7.9% engagement rate. Lowest, the product-update link post at 1.2%. Your carousels average about 2.6× the engagement of link posts this month.
Claude: Top industries, IT Services 28%, Financial Services 14%, Marketing & Advertising 11%. By seniority, senior-level 38%, manager 24%, director 12%.
Example outputs shown for illustration; your figures come live from your own connected page.
What do you want to create?
Pick a format, a source and an account. Data Bloo uses AI to build it with your numbers and your branding.




What LinkedIn Pages data you can pull
The same metrics you use in your reports, sliced by post, by date and by audience segment.
Total followers, new followers and follower growth over time, so you see exactly when the page picks up speed.
Impressions, unique impressions, clicks, reactions, comments, shares and engagement rate, the full organic picture.
Page views and unique visitors, so you know how many people actually check the page out, not just scroll past it in the feed.
Slice by post and by date, plus follower and visitor demographics, industry, seniority, company size and location.
Prompts to paste into Claude
Once connected, drop any of these into a fresh chat. Name Data Bloo in your first message, then drill in.
Built for how you actually work
Same connection, different job to be done. Here's the prompt each type of marketer tends to start with.
Agencies
Pull and compare across every client page without switching logins, then draft the monthly social report in the chat.
B2B marketing teams
See which topics actually move impressions and engagement, and prove the page is filling the pipeline's top end.
Employer brand & comms
Check whether the right seniority and industries are following, and whether culture posts out-perform corporate news.
Common issues and fixes
You're likely not signed in yet, or LinkedIn Pages isn't connected in Data Bloo. Ask "Using Data Bloo, list the accounts I have connected." If it comes back empty, open Data Bloo and connect your page, remember you need admin access on the LinkedIn Company Page, LinkedIn only shares page analytics with admins.
Small gaps are normal. LinkedIn keeps processing recent activity for a day or two, unique-member metrics can't simply be summed across days, and time-zone boundaries shift which day an impression lands in. For trends, comparisons and reporting the Data Bloo pull is solid; for the last few hours of a fresh post, LinkedIn's own analytics tab is freshest.
That's LinkedIn, not us. The API reports audience splits, industry, seniority, company size, as shares rather than raw counts, and hides very small segments to protect member privacy. Ask Claude for the split and the direction of change, that's the decision-grade part anyway.
That's on purpose. The connection is read-only. If you need to publish or schedule posts from a tool, use LinkedIn's own composer or a scheduling platform, this is the reporting half, kept deliberately safe.
Query notes & FAQs
No. LinkedIn doesn't publish an official MCP server. What you'll find are community servers that scrape public profiles using your login session, unofficial and against LinkedIn's terms. Data Bloo takes the other route: your company page's analytics through LinkedIn's official Pages API, read-only.
Yes, it's safe, because of how the data flows. Data Bloo reads your page through LinkedIn's official Pages API with admin-approved OAuth, no scraping, no session cookies, no browser automation, which is exactly the behavior LinkedIn restricts accounts for. And the connection is strictly read-only, so nothing can ever be posted in your name.
Yes. LinkedIn only exposes page analytics to page admins, so you connect the page in Data Bloo with an account that has admin access. Any admin level that can see the Analytics tab works.
No. The connector covers LinkedIn Company Pages, LinkedIn's official API doesn't expose personal profile analytics. The tools that promise profile data do it by scraping, which is the part that risks your account.
No. All seven MCP tools are strictly read-only. Claude can pull and analyze your page data but can never publish a post, reply to a comment, send a message or change any page setting.
Any MCP-compatible client, Claude Desktop, Web and Code, plus ChatGPT, and Gemini. The same URL works across all of them.
Yes. As long as they're connected in Data Bloo, ask Claude to compare your LinkedIn Page against LinkedIn Ads, Instagram Insights or Facebook Insights, and it pulls one blended answer, ideal for a full organic-social report.
It's free to start, no credit card. The free tier includes MCP access with usage limits; paid plans raise the limits and add more connected accounts.
No. A free Claude account is enough to add the Data Bloo connector and start pulling LinkedIn Page reports. Your Claude plan is separate from Data Bloo, and the connector works on Claude Desktop, Web and Code.
Yes. Ask Claude to list your connected LinkedIn Pages, and it can pull and compare across them, handy for agencies reporting on multiple clients.
Yes. Pair the MCP with Claude's scheduled tasks or Claude Code for an automatic Monday-morning page digest, follower-growth alerts or a recurring client update, unattended.
Pick how many accounts. Everything else is included.
Every data source, every destination, the Data Bloo MCP and white-label reports come with every paid plan.
Chat with your LinkedIn Page today
Connect LinkedIn Pages to Claude in under 2 minutes and pull reports straight from the chat. Free to start, no credit card.

