bubble-agent-mcp
This server provides AI assistants access to real-time and historical internet conversation trends ('Bubbles') to identify, analyze, compare, and create content from emerging topics gaining momentum. You can:
Discover high-priority Bubbles with
get_bubbles– retrieve trending conversations filtered by category, timeframe (6h, 24h, 7d), and minimum score, returning up to 20 results.Search for specific topics with
search_bubbles– find Bubbles by keyword, company, product, or industry, with optional platform and timeframe filters (up to 30 days).Get detailed insights with
get_bubble_details– see why a Bubble is growing, including its timeline, pain points, opportunities, and verified sources.Compare opportunities with
compare_bubbles– rank 2–5 Bubbles against a goal (content, product idea, launch, distribution) and get a recommendation.Generate content drafts with
generate_content– create evidence-based drafts in multiple formats (X/Twitter, LinkedIn, Reddit, newsletter, Product Hunt comment) with customizable tone and goal, without auto-publishing.Access workspace context via the resource
bubble://workspace/profilefor personalized results based on company and audience data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@bubble-agent-mcp What are today's strongest AI infrastructure Bubbles?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Subio Scrape
Read what people are actually posting — in a browser that is never signed in.
An MCP server that opens a browser on your own machine, reads the public posts a signed-out visitor is shown on X, LinkedIn and Hacker News, and hands them back as structured data your agent can reason about.
Install · Tools · What signed-out access buys you · Blocks · Security
What this is
Ask your agent "what have @naval and @paulg been posting about onboarding this week?" and it opens a real browser window, reads those two timelines, and answers with the posts, their engagement counts and their links.
Everything happens locally. There is no API key, no account, no cloud service and no data leaving your machine except the page requests themselves.
It never signs in. Session cookies are deleted from its browser profile before every run. It reads exactly what a logged-out visitor is shown — nothing behind a login, nothing behind a challenge. It does not solve CAPTCHAs, does not disguise that it is automated, and does not retry a refusal.
That constraint is the point, and it shapes what the tool can and cannot do. The sections below are honest about both.
Related MCP server: contextium-mcp-server
Quick start
claude mcp add subio-scrape -- npx -y github:alijancb/subio-mcpThen ask, in plain language:
собери, что @naval и @paulg писали за неделю про онбординг
Using a different agent — Codex, Cursor, Windsurf, Cline, Zed, VS Code? See INSTALL.md, which has a one-page guide per client that your agent can follow for you.
For Claude Code there is also a plugin, which adds a /scrape command and a
workflow skill on top of the tools:
git clone https://github.com/alijancb/subio-mcp.git ~/subio-mcp && cd ~/subio-mcp && npm installclaude plugin marketplace add ~/subio-mcp && claude plugin install subio-scrape@subioRequirements
Node.js 20 or newer.
A browser. It uses Chrome or Edge if you have one. If not, run
npx playwright install chromiumonce.A desktop session. The window has to be visible — see below for why. This does not run on a headless server.
Tools
Tool | What it reads |
| Posts from named X accounts, with exact view / like / repost / reply counts. |
| Bio, followers, post count for one account |
| A public company or person page, from its JSON-LD |
| A company's posts, when LinkedIn serves them signed out |
| Hacker News stories and comments on a topic |
| Which browser will be driven, from where, how fast, and what happens on a block |
| Close the window early |
Every tool returns the same item shape, so results from four sources merge into one report:
{
"source": "x",
"externalId": "1960...",
"url": "https://x.com/naval/status/1960...",
"author": "naval",
"text": "…",
"publishedAt": "2026-08-27T02:22:11.000Z",
"engagement": { "views": 8499257, "likes": 14021, "replies": 689, "reposts": 1367 },
"via": "@naval"
}Results tell you what actually happened
Collector tools answer with { items, notes, partial }, and notes is not
decoration. A source that was blocked, walled or misspelled returns zero items
— and so does a genuinely quiet week. Without the notes, an agent reports the
second for both:
notes: [
"@naval: 2 items",
"@paulg: 2 items",
"@definitely-not-real: FAILED — not-found: X sent @definitely-not-real to its
signup page instead of a profile. Either the handle does not exist, or X
declined to serve it signed out."
]
partial: trueWhat signed-out access actually buys you
Worth reading before you plan anything around this.
X serves account timelines to a signed-out browser, and serves search to nobody.
x.com/search, hashtags and explore all redirect to a login wall. There is deliberately no search tool here, because there is no signed-out search. A topic on X is answered by reading the accounts that discuss it and filtering withmatch.X answers a headless browser with a bare 403 and an empty document. The window is visible by default for that reason, and not as a preference.
SUBIO_MCP_HEADLESS=1exists and mostly does not work.A missing X handle is not a 404. X answers 200 and redirects into its signup flow, which reads exactly like an empty timeline. The final URL is what gives it away, and is checked.
LinkedIn gives the least and takes it away fastest. A public company or person page renders, usually with JSON-LD on it. After a handful of pages from one client it becomes a sign-in wall — served with a 200 status and carrying an
og:titleof its own, so a wall parses as a page named "Sign Up | LinkedIn" unless you check for the JSON-LD. Expect to be walled within a session.Hacker News has a real public API and is the one source with no ceiling.
Reddit was removed rather than worked around. It closed
/*.jsonto clients without a session, and its public RSS feed carries neither score nor comment count, so what remained could not be ranked against anything else.
Blocks, and what to do about them
Nothing here retries a refusal. A 403, a 429, a challenge or a sign-in wall is the site answering, and asking again is how being throttled becomes being banned. The first block also ends the whole run: the accounts that were not read are listed in the notes, with an instruction not to retry them now.
If you are getting blocked, what helps, in order:
Read fewer accounts per run. This is the whole answer most of the time.
Widen the gap —
SUBIO_MCP_MIN_INTERVAL_MS=10000. Reads are already jittered by ±25% so they do not arrive on a metronome.Wait. A signed-out quota refills on its own, and nothing you change locally makes it refill faster.
What does not help is a fresh browser per account. Blocks are counted against
your IP address, and a new browser profile does not change your address — a
hundred brand-new fingerprints from one address is a stronger bot signal than one
returning visitor. SUBIO_MCP_ISOLATE=1 exists if you want to try anyway: it
opens a throwaway browser on a throwaway profile per account and deletes it
afterwards. It costs a browser launch per account, and it resets the
cookie-scoped guest quota — which is working around a limit rather than
respecting one, and is the opposite of every other decision here. Off by default.
One window, one tab
A scan does not open a browser per account. The server keeps a single browser with a single tab and drives every account, company and page through it, one load at a time — lighter on your machine than a tab per source, and less conspicuous to the sites being read.
The window closes itself five minutes after the last read, and immediately if the client goes away, so nothing is ever left running with nobody driving it.
Configuration
Everything has a working default. Set these only if you need to.
Variable | Default | |
|
| Browser profile, kept apart from your own Chrome |
|
| Read cache |
|
| How long a read counts as fresh |
|
| Minimum gap between two loads of one host |
|
| Close the window after this long idle. |
| unset |
|
| unset | Force |
| unset |
|
Session cookies (auth_token, ct0, li_at, …) are deleted from the profile
before every run, so the promise on the tin holds even if you once opened that
profile by hand and signed in.
Development
npm installnpm run check && npm run build && node scripts/probe.mjsscripts/probe.mjs starts the built server over stdio the way a client does and
exercises the tools that need no browser. It catches a broken build, a bad tool
schema, or anything accidentally written to stdout — all of which look like a
silent hang from inside an agent. scripts/live.mjs is the manual counterpart
that reads the real sites; it is not in CI, because CI should not scrape.
Where things live:
Path | |
| The tool surface |
| One window, pacing, signing out, idle close |
| One module per source |
| Everything known about X's markup — the only file to edit when X changes |
| The same for LinkedIn, parsed as HTML in node |
| The Claude Code plugin's workflow |
The X parser runs inside the page. The LinkedIn parser deliberately does not: LinkedIn redirects on entry, and anything evaluated in the document loses its execution context when it does. It reads the HTML as a string instead, which makes it immune to that rather than lucky about it — and testable from a fixture.
Contributions welcome: see CONTRIBUTING.md.
History
This repository previously held a different Subio MCP server — one that brought a
live Subio workspace into MCP clients over the Subio API. It was replaced rather
than extended, because a local signed-out scraper and an API client share a name
and nothing else. That work is preserved on the
legacy/subio-api-server
branch and under the v0.1.0 tag.
License
MIT.
Available Tools
5 toolscompare_bubblesCompare BubblesARead-only
Compare two to five Bubbles and recommend the strongest one for a specific goal.
Inputs: bubble_ids (required), goal.
generate_contentDraft content from a BubbleA
Generate an evidence-based content draft from a Bubble. This tool never publishes automatically.
Inputs: format (required), bubble_id (required), goal, tone, +1 more.
get_bubble_detailsExplain a BubbleARead-only
Explain why a Bubble is growing and return its timeline, pain points, opportunities, and verified sources.
Inputs: bubble_id (required).
get_bubblesGet today's BubblesBRead-only
Return the highest-priority internet conversations currently gaining momentum.
Inputs: limit, category, min_score, timeframe.
search_bubblesSearch BubblesBRead-only
Search current and historical Bubbles about a company, product, technology, industry, or keyword.
Inputs: query (required), limit, platforms, timeframe.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool targets a distinct step in the bubble workflow: listing current, searching, getting details, comparing, and generating content. There is no functional overlap.
All tools use a consistent verb_noun snake_case pattern with clear verbs (get, search, compare, generate). Naming is predictable and follows a uniform convention.
With 5 tools, the surface is well-scoped for the domain. Each tool serves a necessary purpose without redundancy or bloat.
The toolkit covers the full lifecycle of bubble analysis: discovery, deep dive, comparison, and content generation. No critical operations are missing for the intended use case.
Maintenance
Related MCP Connectors
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
Real-time chat hub for AI agents — Claude Code, Cursor, Cline, Codex over MCP or REST.
Hosted MCP server for live public-data APIs and Skills for AI agents.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseAqualityDmaintenanceAn MCP server that gives any agent real-time news plus the contextual intelligence to use it well — tone distribution, emerging stories, narrative shifts, spike alerts, and tone-over-time charts — powered by Overtone's publisher network. Works with any MCP-compatible client: Claude Desktop, Claude Code, Cursor, Windsurf, Codex, Kimi K2, and more.72MIT
- AlicenseBqualityDmaintenanceMCP server for Contextium — pipe team SOPs, coding standards, agents, skills, and workflows directly into Claude, Cursor, and other AI coding assistants.67MIT
- AlicenseCqualityBmaintenanceMCP server to connect Claude Code, Codex, or Cursor to the Lightbulb Partners Agents platform, enabling domain agents, code workspaces, connectors, and more.500Apache 2.0
- AlicenseNot gradedqualityBmaintenanceMCP server for SentientUI that gives AI agents in Claude Code, Cursor, and Copilot direct access to experiment data and management actions.76 npm1MIT