Vibewatch is now a ChatGPT app. Search "vibewatch" in ChatGPT's plugin directory, or find it under Data & Analytics, and you can connect your Vibewatch organization and ask about your community in plain language.
Before you connect anything to your community data, the fair question is what the other side can actually do with it. This post answers that at the level of the tool list, because that is the level where the answer is checkable.
Eight tools, and none of them writes
Once connected, ChatGPT can call eight tools against your organization:
get_organization— which org the connection is scoped to, and its collection status.get_sentiment_overview— composite score, positive/neutral/negative distribution, per-source breakdown and message counts for a window you choose.get_sentiment_timeseries— the daily trend, one point per day, with the change between the first and latest score.get_daily_insights— daily highlights and lowlights with their source citations.get_reports— the weekly reports, including the TL;DR and the Worth Addressing themes.search_messages— your own collected messages, filtered by platform, date, sentiment range, audience, author or keyword.get_market_context— the Fear & Greed Index, your tracked assets, and your sentiment plotted against them.get_stacks_ecosystem_sentiment— the public Stacks Vibe Index, the same numbers anyone can read without an account.
There is no ninth tool that posts, edits, deletes, or changes a setting. The server exposes queries and nothing else, and every tool declares readOnlyHint: true and destructiveHint: false in its annotations, which is what OpenAI's directory scan reads. The same connection works in Codex and in any other MCP client.
What it deliberately will not return
The Stacks tool is the interesting one, because it is the only tool that touches communities other than yours. It returns the composite score, the components, the counts and the opted-in project leaderboard. It does not return message text, quotes, in-server authors, or exact per-project message counts.
That line is not an oversight. The index is a public artifact built from communities that agreed to be on the panel, and an aggregate score is what they agreed to. Anything that would let you reconstruct who said what inside someone else's Discord stays out of the tool, exactly as it stays off the index page.
Your own messages are a different matter: search_messages returns them to you, because they are yours, and reading them is the job.
The connection is scoped to one organization
Signing in with your Vibewatch account authorizes one organization, and every tool call resolves against that org. A member who is removed loses access on the next call, a revoked key is invalidated immediately rather than at the next cache expiry, and an org that never turned MCP access on has nothing to connect to.
Plan does not gate it. MCP access is on every plan, including the trial, which is a deliberate decision rather than an oversight — the data is yours, so the door to it is not a tier. If collection has stopped because a trial or subscription ended, the tools still answer and say so in the response instead of quietly returning an empty week.
Rate limits protect the paying side
The anonymous and authenticated surfaces do not share a budget. The public mount, which only serves the Stacks index, has its own ring-fenced counter, so a burst of anonymous traffic cannot spend the capacity a paying organization is relying on. Authenticated calls run against per-org limits before a shared one.
Why read-only was never a compromise
We have taken the same position everywhere else: the bot in your Discord reads and does not post, the platform permissions we ask for are the narrow ones, and what we store is a short list. A write-capable AI connection to a community's own conversation data would be a different product with a different risk, and nobody has asked us for one.
What people do ask is what happened this week and why the number moved. That is a read.
To try it, search "vibewatch" in ChatGPT's plugin directory and connect your organization. The demo org shows the same data in the product itself if you want to see the shape first.