About

One person, one product, one read-only permission.

LinkIntel is not a platform, a suite or a company with departments. It is a small service that reads the performance of the posts you already published, and hands those numbers to the assistant you already write with.

Marcos Placona

Who runs it

Marcos Placona

I am a developer relations consultant based in London. I publish on LinkedIn most weeks, which is how I ended up needing this: I wanted to know which of my posts actually did something, without opening yet another dashboard to find out.

LinkIntel is operated by DevRel Bridge Ltd, a company registered in England and Wales (company number 15979110), registered office 128 City Road, London, EC1V 2NX. There is no staff behind that name. If you email support, I am the one who reads it, and I am also the one who can change the thing you are writing about.

support@getlinkintel.com

Why it exists

The dashboard was the wrong shape. So it went.

LinkIntel started as a dashboard for LinkedIn Page analytics. It worked, and I used it, and it changed nothing about what I posted. The numbers were in one place, my writing happened in another, and the gap between those two places was where all the good intentions went to die.

Two things then happened at once. LinkedIn moved the interesting analytics to personal profiles and opened a proper API for them, and I noticed I had stopped drafting posts in a text editor: I was drafting them by talking to an assistant. The dashboard was competing with a habit it could never win against.

So the Page product was retired in August 2026 and the read side was rebuilt as an MCP server. Now the assistant that helps me draft a post can also ask what happened to the last thirty, in the same conversation, without me going anywhere. That turned out to be the entire product. Everything else was scaffolding.

There is still a small web view at /analytics, showing exactly the same data, for the times you would rather just look.

Plainly

What it is, and what it is not.

This product asks for access to your LinkedIn account, so the boundary matters more than the pitch does.

It is

  • Analytics for posts you published on your own LinkedIn profile
  • Read through LinkedIn's official Member Post Analytics API, with one permission you grant on LinkedIn's own screen
  • Delivered as an MCP server, so the assistant that helps you write can also read what worked
  • $39 a month, one plan, cancel whenever you like

It is not

  • Not a scraper. Nothing here reads a page it was not given permission to read
  • Not able to post, comment, react, message or follow as you. We hold no write permission at all
  • Not for LinkedIn Pages. Organisation analytics is a different API this product no longer covers
  • Not a place your numbers get sold, shared or used to train a model

The single scope requested

r_member_postAnalytics

You grant it on LinkedIn’s consent screen and you take it back on LinkedIn’s permitted services page, without asking me first.

If that sounds like the shape of thing you wanted, it is right here.

Checkout first, then you connect LinkedIn. No evaluation period, so there is nothing to remember to cancel.