TL;DR, Quick Answer
9 min readAdd https://mcp.flowsery.com/mcp as a custom plugin at chatgpt.com/plugins in developer mode, sign in to Flowsery in the window that opens, and never paste a token into the dot chat. OpenAI has not documented whether a dot uses a developer-mode plugin, so prove it with one read call. 23 of Flowsery's 28 API operations only read, which is why the ChatGPT Pro read/fetch limit on custom MCP costs an analytics dot very little.
Connecting an OpenAI dots plugin for web analytics takes one URL, one sign-in and one read-only test, and the test is the step that matters. OpenAI launched dots at DevDay on 29 September 2026: an always-on ChatGPT agent, powered by GPT-6 Astra, with its own cloud computer and browser. Flowsery is not in ChatGPT's plugin directory as of 29 September 2026, so the way in is Flowsery's hosted MCP server, added by hand in developer mode.
The short version: turn on developer mode, add https://mcp.flowsery.com/mcp at chatgpt.com/plugins, sign in to Flowsery when its window opens, then ask your dot to list your Flowsery websites before you ask it anything that matters.
What is an OpenAI dots plugin?
An OpenAI dots plugin is a service connection your dot can call, and OpenAI's plugin docs define a plugin as MCP servers plus skills in one directory shared by ChatGPT and Codex. OpenAI's dots docs say a dot "can use supported plugins installed and enabled for your account". Flowsery's hosted MCP server is not in that directory, so developer mode adds it as a custom plugin, and that detail decides the next question.
Can a dot use a developer-mode plugin?
OpenAI has not documented whether a dot uses a custom plugin added in developer mode, as of 29 September 2026. The dots docs say "supported plugins" and stop there. OpenAI's August help article on MCP in ChatGPT contains a warning from an older product: it says agent mode "will not use custom apps". Dots are a separate product, and OpenAI has said nothing about them either way.
So treat the first conversation as an experiment. Ask the dot to list your Flowsery websites and show the raw response. Website IDs and domains mean the dot is calling the plugin. A tidy explanation of how Flowsery works means the dot browsed instead, and nothing further in this guide applies until that changes.

How do you add Flowsery to ChatGPT for a dot?
Flowsery goes into ChatGPT as a custom MCP server in four steps, all on a desktop app or desktop browser, because OpenAI says you cannot create a dot on mobile or mobile web.
https://mcp.flowsery.com/mcp. OpenAI's developer docs ask for the full URL including the /mcp path.Use the Flowsery plugin only. Do not open flowsery.com in your browser.
1. List the Flowsery workspaces and websites you can reach. Show the raw
website IDs and domains.
2. For the first website, get last week's overview against the week before,
timezone Europe/Berlin. Show visitors, sessions, bounce rate and revenue
for both weeks.
3. Do not create, update or delete anything in Flowsery. If a step needs a
write, stop and ask me.
Where does the Flowsery credential go?
The Flowsery credential goes into Flowsery's own sign-in window, never into a message to your dot. OpenAI's safety post says a secret "placed separately in a readable message or document may still be visible to the model", and its safety FAQ says password protections don't cover passwords shared in a chat or through a plugin. Flowsery's MCP server signs you in with OAuth, so the secret never enters the conversation. The server also takes a Bearer header for clients without OAuth, and a dot chat has no header field.
Signing in with OAuth has two consequences. Flowsery's API reference says an OAuth sign-in "can reach every workspace its member belongs to, across organizations", and a call that names no workspace lands in your default one, so an agency has to name the client workspace in every task. And your Flowsery role decides what the dot can change: a write from a role without the flowsery.write permission gets a 403 permission_denied, and only Admins and Editors hold it. A dot signed in as a Viewer cannot write to Flowsery, whatever ChatGPT allows.
Which Flowsery calls are safe reads, and which write?
Flowsery's public API documents 28 operations as of 29 September 2026, and 23 of them only read. The other five change data.
| Call | What it returns | Changes data |
|---|---|---|
GET /overview, /timeseries, /breakdown | Headline metrics, trends, any dimension | No |
GET /pages, /referrers, /channels, /campaigns and the other breakdowns | Where visitors came from and landed | No |
GET /goals, /realtime, /realtime/map | Completions, and who is on the site now | No |
GET /issues, /issues/{issueId}, /visitors/{visitorId} | AI-detected issues, one visitor's timeline | No |
GET /websites, /workspaces, /metadata | What this sign-in can reach | No |
PATCH /issues/{issueId} | Moves an issue between statuses | Yes |
POST /goals, DELETE /goals | Records or deletes goal completions | Yes |
POST /payments, DELETE /payments | Records or deletes payments | Yes |
Flowsery's hosted MCP server exposes the write tools too, including the ones that update issues and delete goals or payments. PATCH /issues/{issueId} is the one to guard: a suspended issue disappears from the default list, so a dot tidying the backlog shortens the list without fixing anything on it.
OpenAI says a dot always confirms before "permanently deleting data", which on paper covers both DELETE calls. Your Flowsery role is the check that does not depend on how the dot classifies a call. Teams that want writes impossible at the server can deploy Flowsery's read-only worker from github.com/Flowsery/remote-mcp, where every tool is a GET.
Does the ChatGPT Pro read-only limit block an analytics dot?
The ChatGPT Pro limit barely touches an analytics dot, because 23 of Flowsery's 28 operations are reads. OpenAI's August help article says full MCP is available only to Business and Enterprise/Edu, and that "Pro users can connect MCPs with read/fetch permissions in developer mode." For a dot that publishes posts, that rule is a wall. For analytics it removes five writes and leaves every report, breakdown and issue list.
On Business Premium, full MCP puts the write tools back in reach, and the gate becomes Custom Rules, OpenAI's four settings: take action without asking, take action when you say so or if pre-approved, ask before taking action, and hand off to you. Start on "Ask before taking action", and keep the Flowsery role at Viewer until a month of reads has earned more.
Flowsery
Start FREE Trial
Real-time dashboard
Goal tracking
Cookie-free tracking
Does a dot's own browsing show up in Flowsery?
A dot visits your site in a real Chrome browser on a Linux machine that OpenAI maintains, and whether Flowsery counts that visit turns on one flag OpenAI has not documented. Flowsery's tracking script at cdn.flowsery.com/main.js skips any browser that reports navigator.webdriver as true, and session recording skips it too. OpenAI's dots documentation, checked 29 September 2026, names no user agent string, no IP range and no robots.txt token for a dot, and says nothing about that flag.
That leaves two outcomes for a dot that opens your pricing page. If its Chrome sets the flag, Flowsery drops the visit. If it does not, the visit counts as an ordinary Chrome session with nothing marking it as an agent, the same way Meta Muse visits land as human ones.
- Each dot has its own cloud computer and browser
- OpenAI maintains the Linux system and the Chrome browser
- Flowsery's tracker ignores
navigator.webdriver === true
- A user agent string for dots
- An IP range for dot computers
- A robots.txt token
- Whether a dot's Chrome sets
navigator.webdriver
Test it once. Ask the dot to open a URL nobody else uses, such as /pricing?src=dot-test, then check Flowsery's realtime view. GET /realtime/map lists visitors from the last five minutes with browser, operating system and current URL, so a counted dot visit shows up under that URL. Plugin calls never touch the site: an API overview loads no page and fires no tracker. Bot traffic filtering covers the wider problem.
What does an analytics dot cost?
Your first dot is included in ChatGPT Pro ($100, $200 or $500 a month) or Business Premium at no extra cost, according to OpenAI's launch post. Flowsery includes its API on both plans: Team at $250 a month and Pro at $500, each with a 14-day free trial and no card. Geography is the real gate. Dots on ChatGPT Pro exclude the EEA, the UK and Switzerland and Business Premium covers all supported ChatGPT regions.
Where do reporting and session analysis go from here?
The OpenAI dots plugin for analytics reporting puts the Monday numbers on a recurring task and covers the approval a dot wants before it posts into Slack. The OpenAI dots plugin for session analysis points the dot at Flowsery's AI-detected issues. Other agents get the same setup in the Meta Muse connector guide and the Grok bot template guide, and the dot reads the same numbers as Flowsery's web analytics dashboard.
Frequently Asked Questions
Is Flowsery in the ChatGPT plugin directory?
No, not as of 29 September 2026. Add the hosted MCP server at https://mcp.flowsery.com/mcp as a custom plugin in developer mode, then sign in to Flowsery in the window that opens.
Can I paste a Flowsery API token into my dot instead?
No. OpenAI says a secret in a readable message can be visible to the model. Flowsery's MCP server signs you in with OAuth, so no token crosses the conversation. Delete any token that lands in a chat at flowsery.com/api-tokens.
Why does the dot describe Flowsery instead of reading my data?
The dot browsed the web instead of calling the plugin. Confirm the plugin is enabled in ChatGPT's Plugins tab, tell the dot "use the Flowsery plugin, not the browser", and ask for raw website IDs.
Can the dot change my Flowsery data?
Only through five calls: PATCH /issues/{issueId} and the POST and DELETE calls on goals and payments. OpenAI's August help article limits ChatGPT Pro to read/fetch on custom MCP. On any plan, a Flowsery Viewer sign-in gets a 403 on every write.
Why are the numbers from the wrong client?
An OAuth sign-in reaches every workspace your Flowsery account belongs to, and a call that names none lands in the default workspace. Name the workspace at the top of each task.
How do I remove the dot's access to Flowsery?
Remove the Flowsery plugin in ChatGPT's Plugins tab, and lower the Flowsery role of the account it signed in with. OpenAI says you cannot view or edit a dot's memories, and deleting the dot is the only way to clear them, so numbers it already learned stay with it.
Can a ChatGPT Pro dot read my Flowsery data?
OpenAI's August 2026 help article says Pro users can connect MCPs with read/fetch permissions in developer mode, and 23 of Flowsery's 28 API operations only read. That covers every report, breakdown and issue list. OpenAI has not documented whether a dot uses a plugin added in developer mode, so ask it to list your Flowsery websites first. Dots on ChatGPT Pro are not available in the EEA, the UK or Switzerland.
Do I need a paid Flowsery plan to connect the plugin?
Flowsery includes its API on both plans, Team at $250 a month and Pro at $500. Each comes with a 14-day free trial and no card.
Can I set up a dot on my phone?
OpenAI says you cannot create a dot on mobile or mobile web. Do the setup on the desktop app or a desktop browser, starting with developer mode and chatgpt.com/plugins.
Will a dot's visit to my site count in Flowsery?
Flowsery's tracker skips any browser that reports navigator.webdriver as true, and OpenAI has not documented whether a dot's Chrome sets it. Open a URL nobody else uses, such as /pricing?src=dot-test, and check the realtime view. Plugin calls never load a page, so they never count as visits.
Flowsery
Start FREE Trial
Real-time dashboard
Goal tracking
Cookie-free tracking
Start a Flowsery trial and connect the MCP server, or read the API reference first.
Sources: Introducing dots, How we build safety, security and privacy into dots, OpenAI help on getting started and safety, the dots user docs, ChatGPT plugins, connecting a plugin to ChatGPT, OpenAI's MCP help article (updated August 2026), the Flowsery API reference and the Flowsery OpenAPI spec. Checked 29 September 2026.
Was This Article Helpful?
Let us know what you think!
See us more often in Google
One click marks Flowsery as a preferred source, so our articles sit higher in your Top Stories, AI Mode, and AI Overviews.
Before you go...
Flowsery
Revenue-first analytics for your website
Track every visitor, source, and conversion in real time. Simple, powerful, and cookie-free.
Real-time dashboard
Goal tracking
Cookie-free tracking
Related Articles


Ask Your Traffic Questions Through a Manus Cue Connector for Web Analytics
Build a Manus Cue connector for web analytics on the Flowsery MCP server: where Manus takes the URL and token, what Cue leaves out, and which calls write.


Schedule the Monday Report With an OpenAI dots Plugin for Analytics Reporting
Run a weekly report with an OpenAI dots plugin for analytics reporting: six Flowsery reads on a recurring task, and the Slack post that needs a rule.


Rank Broken Sessions With an OpenAI dots Plugin for Session Analysis
Point an OpenAI dots plugin for session analysis at Flowsery issues: three reads rank what broke, and PATCH /issues is the one write to keep out of reach.

