Everyone keeps telling me MCP is dead.
Meanwhile our MCP traffic just 7x’d in 5 weeks.
We shipped the Octolens API + MCP server earlier this year as a side bet.
The thesis: brand monitoring shouldn’t live in a dashboard, it should be a data layer your team (and your agents) can pull from.
Turns out a lot of people agree.
What’s unexpected for me is that API and MCP are growing together, not cannibalizing each other.
API is how devs build internal workflows and MCP is how AI agents consume data.
We’re going all-in on this.
Social data infrastructure for humans and agents → that’s the next chapter for Octolens.
octolens is one of the most underrated marketing products i've used in years
so simple and just works
not to say @LottiSchmitt somehow read my mind last year as i was thinking how shitty all of the social listening products out there were
her "want to try @Octolens again?" email couldn't have come at a better time
Redirecting complaints into a megathread can mean missed feedback and more frustrated customers.
I saw this mod post and thought: this isn't the best strategy.
From a moderation point of view, grouping complaints into one place is tidy.
But for other teams this strategy creates problems:
- important feedback gets easier to miss
- users can feel dismissed on top of being frustrated
If someone is unhappy about pricing, limits, or a product change, and the response they get is “post it somewhere else,” you may lose the original feedback point and you may now also have a user who feels ignored.
That is why product teams need their own visibility into what people are upset about, independent of how a subreddit is moderated.
Not every complaint needs a public response.
But missed feedback is expensive, and annoyed customers do not usually get quieter.
I set up a workflow that turns actionable product mentions into Linear issues automatically.
Reddit bug report → Linear issue
X feature request → Linear issue
LinkedIn customer feedback → Linear issue
Built with @Octolens + @linear MCP.
Short walkthrough below + full copy and paste prompt 👇
Last week we fully redesigned @Octolens
We released API V2 (which now covers the whole product), new dashboard, new keyword management page and killed multiple features
It felt scary at first to change so many things, but in the end you have to move fast these days to stay relevant
I am really excited for the new chapter of agent-first Octolens, with a lot of cool features coming soon
We're just getting started
Saas isn't dying. Saas that doesn't evolve is.
In the last month, we've switched from
@typefully => Ordinal
@brand24 => @Octolens
its obvious who is clued in, locked in, and is are using LLMs to build the best product
just don't be complacent
i love @Octolens. it's a bat signal for val town mentions
honestly i tried to build it myself, but it's easier to pay octolens the $120 / month
we have a val that receives their webhook and forwards it to a public discord channel, formatted with useful buttons
12 Social Media Search Engines in 2026
Octolens
Social Searcher
Brand24
Mention
Hootsuite
Talkwalker
SearchAll
Social Search Engine
Boardreader
Twitter/X Advanced Search
Reddit Search (+ Redditle)
Google Site Search + Google Alerts
https://t.co/Cb49tfFfiI
By @LottiSchmitt
Railway has 2.7 million users. Their brand name is also a common English word.
Their DevRel engineer @thisismahmoud once replied to someone complaining to @railway about a 5hr train delay.
The post went viral, but the underlying problem was real: how do you track a brand like Railway?
So he built an API-powered system (deployed on Railway ofc) with @Octolens. Mahmoud routes relevant mentions across every platform into dedicated channels with daily digests.
@sarahkb125, who leads growth, on the other hand uses Octolens to correlate mention trends with signup data. She saw the need to prioritize Reddit as a channel for their brand awareness flywheel.
From one platform with a blocklist to infrastructure that runs both real-time DevRel and growth strategy.
The @vercel team is always listening and engaging with customers on @x. We shape the product as a result of these conversations.
Vercel gives us the velocity to ship, X gives us a nonstop stream of user feedback. Thanks @simhskal & @riyvir!
We analyzed 522M Reddit mentions across 300K+ B2B SaaS brands.
Reddit is quietly becoming one of the highest-converting channels for B2B software.
7 findings the data showed 🧵
Our DevEx team replaced community insight SaaS subscriptions with an agent that monitors activity, suggests replies, and self-improves with agent memory.
We use @Octolens for a data firehose of Warp mentions from X, LinkedIn, Reddit, etc, and set up a scheduled agent using Oz to review mentions. This agent has a repo of Skills to:
- Decide how to engage (skip, like, or reply)
- Suggest replies
- Review our own feedback to the agent via Slack
Then, the agent can PR changes to itself based on our feedback. The prompting for this self-improvement Skill is wild; reads like a product manager doc.
You don't need agent memory tools. Let agents PR Markdown changes.