flowsery
OfficialThis MCP server lets an AI agent read and lightly manage Flowsery web analytics across one or more workspaces and websites.
Discover access: list workspaces you can act in, and list websites with domain, timezone, currency and KPI goal.
Website settings: fetch one site's domain, timezone, currency, KPI goal, logo and colors.
Traffic totals: visitors, sessions, bounce rate, session duration, revenue, revenue per visitor and conversion rate over any date range.
Trends: the same metrics bucketed by hour, day, week or month, with new, renewal and refunded revenue.
Realtime: count visitors active in the last 5 minutes, and map them at rounded city-level coordinates (no IPs).
Breakdowns: rank pages, referrers, channels, campaigns, countries, regions, cities, devices, browsers, operating systems and hostnames.
Any dimension: group visitors by any of 25 dimensions, including entry page, exit link, browser/OS versions, UTMs, ref, source, via and all params.
Filtering: narrow every report by country, region, city, device, browser, OS, page, hostname, referrer, channel, goal and UTM/ref/source/via tags, with is/not/contains/any-of operators.
Goals: list goals and completions, and record a custom goal completion (created on first use).
Revenue: record payments for attribution (never charging anyone), mark refunds and renewals, or delete payment records.
Visitor journeys: one visitor's location, device, source, visits, pages, goals, revenue and a newest-first activity timeline (no names, emails or IPs).
Session issues: list bugs, broken flows and UX problems the AI found, get full detail with occurrences, steps to replicate, comments and linked Linear/Jira tickets, and change status.
Cleanup: delete goal completions or payment records matching filters (destructive, irreversible).
Scoping: every tool accepts an optional
workspaceId, and reports acceptwebsiteIdordomain.
Enables automatic revenue and payment tracking from Stripe transactions for attribution in Flowsery analytics.
Flowsery agent
Let your AI agent query Flowsery, the privacy-first, cookie-free web analytics: live visitors, traffic breakdowns by 25 dimensions, goals, revenue, visitor journeys, and the bugs, broken flows and UX problems Flowsery's AI found in session recordings. 28 MCP tools, OAuth sign-in, no cookies on your site.
Connect in 30 seconds
claude mcp add --transport http flowsery https://mcp.flowsery.com/mcpAny other MCP client needs only the URL, https://mcp.flowsery.com/mcp. The first call opens a browser to sign in with your Flowsery account. Nothing to install and no key to paste. Setup for each client is below.
Related MCP server: Gizmo Analytics
What this repo is
This repo holds every Flowsery agent integration except the Claude Code and Hermes Agent plugin:
Path | What it is |
The agent skill for | |
Source of the MCP server that runs at | |
| The Gemini CLI extension. It connects to the hosted MCP server and signs in with OAuth. |
| Runs the MCP server over stdio, for Glama and anyone who wants it in a container. |
| The LobeHub marketplace listing for the hosted MCP server. |
The Kiro power. It connects to the hosted MCP server and signs in with OAuth. |
The Claude Code and Hermes Agent plugin lives in Flowsery/claude-plugin. It signs in with OAuth and never asks for an API key, which the Claude plugin directory and the Hermes catalog both require, so it ships its own MCP-only skill instead of the script skill here.
Pick your install
You use | Install | Sign-in |
Claude Code |
| OAuth |
Hermes Agent |
| OAuth |
Gemini CLI |
| OAuth |
Claude Desktop, Cursor, ChatGPT or any MCP client | Add | OAuth, or an API key header |
Cursor, Codex, Windsurf, Claude Code or any agent with skills |
| API key |
Setup by client
The server answers an unauthenticated call with a 401 that points at its OAuth metadata, so every client below opens the Flowsery sign-in on its own. One sign-in reaches every workspace you belong to.
Claude.ai and Claude Desktop
Open Settings > Connectors, add a custom connector with the URL https://mcp.flowsery.com/mcp, and sign in. A Claude Desktop build without connectors can go through mcp-remote, which handles the sign-in itself:
{
"mcpServers": {
"flowsery": {
"command": "npx",
"args": ["mcp-remote", "https://mcp.flowsery.com/mcp"]
}
}
}Claude Code
The plugin adds the server and a skill that knows how to use it:
/plugin install flowsery --marketplace Flowsery/claude-pluginOr add only the server:
claude mcp add --transport http flowsery https://mcp.flowsery.com/mcpRun /mcp, pick flowsery and sign in.
ChatGPT
Add a custom connector in Settings > Apps & Connectors with the URL https://mcp.flowsery.com/mcp and sign in.
Cursor
~/.cursor/mcp.json:
{
"mcpServers": {
"flowsery": { "url": "https://mcp.flowsery.com/mcp" }
}
}Windsurf
~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"flowsery": { "serverUrl": "https://mcp.flowsery.com/mcp" }
}
}VS Code
.vscode/mcp.json:
{
"servers": {
"flowsery": { "type": "http", "url": "https://mcp.flowsery.com/mcp" }
}
}Codex
~/.codex/config.toml:
[mcp_servers.flowsery]
url = "https://mcp.flowsery.com/mcp"Then sign in with codex mcp login flowsery.
Gemini CLI
gemini extensions install https://github.com/Flowsery/agentHermes Agent
hermes plugins install flowsery
hermes plugins enable flowseryHeadless agents and clients without OAuth
Create an API token on the API tokens page and send it as a header. Keys start with flow_ws_.
{
"mcpServers": {
"flowsery": {
"type": "http",
"url": "https://mcp.flowsery.com/mcp",
"headers": { "Authorization": "Bearer flow_ws_your_key" }
}
}
}Example prompts
"How's my traffic this week compared to last week?"
"Which channels and campaigns brought paying customers this month?"
"Visitors dropped on Tuesday. Check pages, referrers and devices and tell me why."
"How many people are on the site right now, and where are they?"
"How much traffic did ChatGPT, Perplexity and other AI assistants send us this month?"
"What did Flowsery find in session recordings this week? Mark the checkout bug as in progress."
"Show me the journey of the visitor who just started a free trial."
"Which landing pages convert best for mobile visitors from Germany?"
Tools
28 tools. Every report takes a date range, a timezone and filters on country, region, city, device, browser, OS, page, hostname, referrer, channel and UTM parameters.
Workspaces and websites
Tool | What it does | Changes data |
| List the workspaces the sign-in can act in; pass an id as | No |
| List the websites the token can read, with domain, timezone, currency and KPI goal. Call it first | No |
| One website's settings: domain, timezone, currency, KPI goal, logo and colors | No |
Traffic
Tool | What it does | Changes data |
| Headline totals for a date range: visitors, sessions, bounce rate, session duration, revenue, revenue per visitor and conversion rate | No |
| The same metrics by hour, day, week or month, with new, renewal and refunded revenue | No |
| Visitors active in the last 5 minutes | No |
| Active visitors with city-level location for a live map; coordinates rounded to 0.1 degrees, no IP addresses | No |
Breakdowns
Tool | What it does | Changes data |
| Page paths ranked by visitors | No |
| Referring sites ranked by visitors, with known sources such as Google, ChatGPT and Reddit named | No |
| Traffic grouped into GA4-style channels: Organic Search, Paid Social, Email, Direct and more | No |
| UTM campaigns ranked by visitors | No |
| Visitors by country | No |
| Visitors by region or state | No |
| Visitors by city | No |
| Desktop, mobile and tablet split | No |
| Visitors by browser | No |
| Visitors by operating system | No |
| Visitors by hostname, for sites that track several domains or subdomains | No |
| Group visitors by any of 25 dimensions, including entry page, exit link, browser and OS versions and every UTM parameter | No |
Goals and visitors
Tool | What it does | Changes data |
| Every goal, including the automatic payment and free trial goals, with completions in the window | No |
| Record one completion of a custom goal; the goal is created on first use | Yes |
| Permanently delete goal completions that match the filters | Yes |
| Record a payment for revenue attribution, or mark one refunded; never charges anyone | Yes |
| Permanently delete payment records that match the filters | Yes |
| One visitor's location, device, source, visits, goals, revenue and timeline | No |
Session issues
Tool | What it does | Changes data |
| Bugs, broken flows and UX problems the AI found in session recordings, ranked by severity | No |
| One issue with its occurrences, sessions, steps to replicate, comments and linked Linear or Jira ticket | No |
| Set an issue to open, in progress, resolved or suspended | Yes |
Roles, permissions and safety
Every call runs with the signed-in member's role in the workspace. Reads need
workspace.read; tracking or deleting goals and payments and changing an issue's status needflowsery.write, which Admin and Editor hold.Read-only tools carry
readOnlyHint. Onlytrack_goal,delete_goals,track_payment,delete_paymentsandupdate_issue_statuschange anything, so clients that confirm writes ask before those five. Payment tools change analytics records only; they never charge, refund or touch a payment provider.Visitor tools return the analytics of your own websites.
get_realtime_maprounds coordinates to 0.1 degrees, and no tool returns IP addresses or billing details.A website key (
flow_) reaches one website; a workspace token (flow_ws_) or an OAuth sign-in reaches every website in the workspace.
Workspaces
An OAuth sign-in can reach several workspaces, each with its own data and your own role there. list_workspaces returns them, and every other tool takes an optional workspaceId, which the server sends as the X-Workspace-Id header. Without it a tool works in the workspace list_workspaces marks current. A workspaceId the sign-in cannot reach answers 403 with code: workspace_access_denied. An API key belongs to one workspace.
The skill
npx skills add Flowsery/agentOr copy skills/flowsery/ into your project's skills folder. Cursor can also read it as a remote rule from https://raw.githubusercontent.com/Flowsery/agent/main/skills/flowsery/SKILL.md.
Setup
Create an account at flowsery.com, add your website and install the tracking snippet.
Create a workspace API token on the API tokens page.
Run:
./scripts/flowsery.js setup --key flow_ws_xxxxx
What the agent can do
Headline totals for any date range: visitors, sessions, bounce rate, revenue and conversion rate
Trends by hour, day, week or month
Visitors active right now, with a live map
Breakdowns by any of 25 dimensions: pages, landing pages, referrers, channels, UTM campaigns, countries, regions, cities, devices, browsers and more
Filters on country, device, browser, UTM parameters, page and channel
Goals and their completions, and recording custom goal events
Recording payments for revenue attribution (Stripe, LemonSqueezy and Polar are tracked automatically)
One visitor's full journey with their activity timeline
The issues Flowsery's AI found in session recordings, and changing their status
You: How's my traffic this week?
Agent: Your site had 2,847 visitors and 3,912 sessions this week.
Bounce rate is 62%. Revenue: $1,240 from 18 conversions.
Top sources: Google (41%), Direct (28%), Twitter (12%).Run the server yourself
The hosted server is the easy path. To run it yourself over stdio with Bun:
{
"mcpServers": {
"flowsery": {
"command": "bun",
"args": ["run", "/path/to/agent/mcp-server/src/index.ts"],
"env": { "FLOWSERY_API_KEY": "flow_ws_your_key" }
}
}
}Or in Docker:
docker build -t flowsery-mcp .
docker run -i -e FLOWSERY_API_KEY=flow_ws_your_key flowsery-mcpbun run src/index.ts --http in mcp-server/ serves the same tools over Streamable HTTP on port 3100, the way https://mcp.flowsery.com/mcp runs. Environment variables and local development are in mcp-server/README.md.
FAQ
Do I need an API key?
No. Point your client at https://mcp.flowsery.com/mcp and sign in with the email you use on Flowsery. Keys are for headless agents and clients without OAuth.
Does the agent see personal data? It sees what your Flowsery dashboard shows for your own websites: approximate location, device, source and activity. No IP addresses, and live map coordinates are rounded.
Can it change my analytics?
Five tools write: track_goal, delete_goals, track_payment, delete_payments and update_issue_status. Everything else is read-only.
Does it work with several websites?
Yes. Call list_websites and pass a websiteId or domain to the report tools.
What's the difference between this repo and Flowsery/claude-plugin?
The plugin is the Claude Code and Hermes package: OAuth only, with a skill that drives these MCP tools. This repo has the server's source, the API-key skill for npx skills add and the Gemini extension.
Links
License
MIT
Available Tools
28 toolsdelete_goalsDelete Goal EventsADestructiveIdempotent
Permanently delete recorded goal completions matching every filter given (filters combine with AND). At least one of visitorId, name, startAt, or endAt is required or the call fails before reaching the API; startAt and endAt are independent, so one bound alone is allowed. Without a date range, matches are deleted across the whole history. Returns the number of rows deleted. Cannot be undone: restate website, filters, and range and get explicit confirmation first. Deletes completions only; the goal definition stays and get_goals still lists it. Use delete_payments for revenue records and update_issue_status for issues. Requires websiteId or domain with a workspace token.
Inputs: name, endAt, domain, startAt, +3 more. Returns: result
delete_paymentsDelete PaymentsADestructiveIdempotent
Permanently delete analytics payment records, without issuing refunds or changing a payment provider. Deletes records matching every filter given (filters combine with AND): one transactionId, all payments of a visitorId, and/or a creation window. At least one of transactionId, visitorId, startAt, or endAt is required or the call fails before reaching the API; startAt and endAt are independent, so one bound alone is allowed. Without a date range, matches are deleted across the whole history. Returns the number of rows deleted. Cannot be undone and removes the revenue from every report and visitor profile, so restate website, filters, and range and get explicit confirmation first. To record a refund that already happened, use track_payment with isRefund instead. Requires websiteId or domain with a workspace token.
Inputs: endAt, domain, startAt, visitorId, +3 more. Returns: result
get_breakdownGet Breakdown by DimensionARead-onlyIdempotent
Group visitors by any one of 25 dimensions, ranked by visitors descending, for a date range. Generic form of the named get_* breakdown tools: use it for dimensions without one (entry_page, exit_link, browser_version, os_version, utm_source, utm_medium, utm_term, utm_content, ref, source, via, all_params); for page, referrer, country, region, city, device, browser, os, campaign, hostname, channel, or goal the dedicated tool returns the same rows. Combine dimension with filter_* to drill in: dimension page plus filter_utm_campaign shows where one campaign landed. Rows carry value, visitors, revenue, and percentage with pagination.total. Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
Inputs: dimension (required), endAt, limit, domain, +25 more. Returns: result
get_browsersGet Visitors by BrowserARead-onlyIdempotent
Get visitors grouped by browser name (Chrome, Safari, Firefox, Edge, and others), ranked by visitors descending, for a date range. Names only: use get_breakdown with dimension browser_version for versions, get_operating_systems for the OS split, and get_devices for desktop versus mobile. Pass filter_browser to other tools to scope them to one browser. Rows carry value, visitors, revenue, and percentage with pagination.total. Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
Inputs: endAt, limit, domain, offset, +24 more. Returns: result
get_campaignsGet Campaign PerformanceARead-onlyIdempotent
Get UTM campaigns (utm_campaign values) ranked by visitors descending for a date range. Only visits tagged with utm_campaign appear, so untagged traffic is absent; use get_referrers or get_channels for the full source picture. Use get_breakdown with dimension utm_source, utm_medium, utm_term, utm_content, or all_params for the other tracking parameters. Rows carry value, visitors, revenue, and percentage with pagination.total. Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
Inputs: endAt, limit, domain, offset, +24 more. Returns: result
get_channelsGet Traffic by ChannelARead-onlyIdempotent
Get visitors grouped into GA4-aligned marketing channels (Organic Search, Paid Search, Organic Social, Paid Social, Email, Display, Referral, Direct, Affiliate, Video, SMS, Audio), ranked by visitors descending, for a date range. Channels are classified from the referrer domain and utm_medium or utm_source. Use this first for the traffic mix, then get_referrers for the domains behind Referral and Organic Social, or get_campaigns for tagged campaigns. Rows carry value, visitors, revenue, and percentage with pagination.total. Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
Inputs: endAt, limit, domain, offset, +24 more. Returns: result
get_citiesGet Visitors by CityARead-onlyIdempotent
Get visitors grouped by city, ranked by visitors descending, for a date range. Finest geographic tool and the longest tail: pass filter_country or filter_region first so the top rows are meaningful, and raise limit when you need more rows. Use get_countries or get_regions for a coarser view. Rows carry value, visitors, revenue, and percentage with pagination.total. Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
Inputs: endAt, limit, domain, offset, +24 more. Returns: result
get_countriesGet Visitors by CountryARead-onlyIdempotent
Get visitors grouped by country, ranked by visitors descending, for a date range. Coarsest of the three geographic tools: use get_regions for states or provinces and get_cities for cities, and add filter_country to either to drill into one country. Use get_realtime_map for where visitors are right now instead of over a range. Rows carry value, visitors, revenue, and percentage with pagination.total. Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
Inputs: endAt, limit, domain, offset, +24 more. Returns: result
get_devicesGet Visitors by DeviceARead-onlyIdempotent
Get visitors split by device type (Desktop, Mobile, Tablet), ranked by visitors descending, for a date range. Use this for the mobile-versus-desktop question; use get_browsers or get_operating_systems for the software split. Pass filter_device to any other tool to restrict it to one device type instead. Three rows at most, so pagination rarely matters. Rows carry value, visitors, revenue, and percentage. Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
Inputs: endAt, limit, domain, offset, +24 more. Returns: result
get_goalsGet Goal CompletionsARead-onlyIdempotent
Get every configured goal (custom events plus the auto-created payment and free_trial goals) with how many visitors completed it in the date range. Use this to compare conversions across goals; use get_overview for conversion_rate against the site's KPI goal, get_breakdown with dimension goal for the same list with revenue and percentage, and get_visitor for one person's completions. Dates default to the last 30 days; filter_* narrows the visitors counted and limit/offset page the goal list. Goals are created by track_goal. Requires websiteId or domain with a workspace token.
Inputs: endAt, limit, domain, offset, +24 more. Returns: result
get_hostnamesGet Visitors by HostnameARead-onlyIdempotent
Get visitors grouped by hostname, ranked by visitors descending, for a date range. Useful when one website tracks several domains or subdomains (www, app, docs); a single-domain site returns one row. Use get_pages for paths within a host, and pass filter_hostname to any other tool to scope it to one host. Rows carry value, visitors, revenue, and percentage with pagination.total. Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
Inputs: endAt, limit, domain, offset, +24 more. Returns: result
get_issueGet Issue DetailARead-onlyIdempotent
Get full detail for one AI-detected issue: every occurrence with timestamps, the sessions behind it, steps to replicate, comments, and any linked Linear or Jira ticket. Get issueId from list_issues; use this only when you need the evidence behind one issue. An unknown id, or one from another website, fails with 'Issue not found'; on a free trial only the first 10 issues are available, and later ones fail as not included in the current plan. Each session lists its recording id, the anonymous visitorUid, start URL and page title, timing and event counts; no names, emails or locations are returned, so surface only what answers the question. Requires websiteId or domain with a workspace token.
Inputs: issueId (required), domain, websiteId, workspaceId. Returns: result
get_metadataGet Website SettingsARead-onlyIdempotent
Get one website's settings: domain, timezone, currency, KPI goal name, logo, and color scheme. Read-only; nothing is changed. Call it after list_websites to learn the timezone and currency before running date-range reports, then pass that timezone to the report tools. With a workspace token pass websiteId or domain; with neither it returns the same website list as list_websites, so prefer list_websites for discovery. A website key needs no selector.
Inputs: domain, websiteId, workspaceId. Returns: result
get_operating_systemsGet Visitors by Operating SystemARead-onlyIdempotent
Get visitors grouped by operating system (Mac OS, Windows, iOS, Android, Linux, and others), ranked by visitors descending, for a date range. Names only: use get_breakdown with dimension os_version for versions, get_browsers for the browser split, and get_devices for desktop versus mobile. Pass filter_os to other tools to scope them to one OS. Rows carry value, visitors, revenue, and percentage with pagination.total. Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
Inputs: endAt, limit, domain, offset, +24 more. Returns: result
get_overviewGet Traffic OverviewARead-onlyIdempotent
Get headline totals for one website over a date range as a single row: visitors, sessions, bounce rate, average session duration, revenue, revenue per visitor, and conversion rate. Dates default to the last 30 days ending now; timezone defaults to the site setting. Every filter_* argument narrows the whole result, so filter_country plus filter_device answers 'mobile visitors from Germany' in one call. Use get_timeseries for the trend over time and a get_* breakdown tool for the split by page, source, or geography. Requires websiteId or domain with a workspace token.
Inputs: endAt, domain, startAt, timezone, +22 more. Returns: result
get_pagesGet Top PagesARead-onlyIdempotent
Get page paths ranked by visitors, descending, for a date range: which pages get the most traffic. Use get_breakdown with dimension entry_page for landing pages or exit_link for outbound clicks, and get_hostnames when the site serves several domains. Add filter_utm_campaign or filter_referrer to see where one source's traffic landed. Rows carry value, visitors, revenue, and percentage with pagination.total. Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
Inputs: endAt, limit, domain, offset, +24 more. Returns: result
get_realtimeGet Active Visitor CountARead-onlyIdempotent
Count the visitors active on the site within the last 5 minutes. A point-in-time number with no history: it takes no date, filter, or pagination arguments. Use get_timeseries with interval hour for recent trends and get_realtime_map when you need where those visitors are. Returns data[0].visitors. Poll no more than once every 5 seconds. Requires websiteId or domain with a workspace token.
Inputs: domain, websiteId, workspaceId. Returns: result
get_realtime_mapGet Live Visitor MapARead-onlyIdempotent
Get the visitors active on the user's own website in the last 5 minutes with their approximate city-level location, for a live map view. Coordinates are rounded to 0.1 degrees, and no IP addresses or other identifying details are returned. Use get_realtime when only the count matters, and get_countries or get_cities for geography over a historical date range. Takes only the website selector: no dates, filters, or pagination. Poll no more than once every 5 seconds. Requires websiteId or domain with a workspace token.
Inputs: domain, websiteId, workspaceId. Returns: result
get_referrersGet Top ReferrersARead-onlyIdempotent
Get referrers ranked by visitors, descending: which external sites sent traffic in the date range. Recognized sites appear under a source name (Google, ChatGPT, Reddit), others under their domain. Use get_channels when you want traffic grouped into GA4-style channels (Direct, Organic Search, Paid Social) instead of individual domains, and get_campaigns or get_breakdown with dimension utm_source for traffic identified by UTM tags rather than referrer. Rows carry value, visitors, revenue, and percentage with pagination.total. Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
Inputs: endAt, limit, domain, offset, +24 more. Returns: result
get_regionsGet Visitors by RegionARead-onlyIdempotent
Get visitors grouped by region or state name (such as California or Bavaria), ranked by visitors descending, for a date range. Sits between get_countries (coarser) and get_cities (finer); combine with filter_country to list the regions of one country. Pass filter_region to other tools to scope them to one region. Rows carry value, visitors, revenue, and percentage with pagination.total. Dates default to the last 30 days; all filter_* arguments apply. Requires websiteId or domain with a workspace token.
Inputs: endAt, limit, domain, offset, +24 more. Returns: result
get_timeseriesGet Analytics Time SeriesARead-onlyIdempotent
Get the same metrics as get_overview bucketed by hour, day, week, or month, plus totals across the whole window. Returns one point per bucket with timestamp, name, visitors, sessions, revenue split into newRevenue, renewalRevenue and refundedRevenue, conversionRate, and kpiValue. Use this for trends and charts; use get_overview for one total and a get_* breakdown tool for a split by dimension rather than time. Dates default to the last 30 days and interval to day. Match interval to range: hourly buckets across a year return thousands of points. Requires websiteId or domain with a workspace token.
Inputs: endAt, domain, startAt, interval, +23 more. Returns: result
get_visitorGet Visitor ProfileARead-onlyIdempotent
Get the analytics for one visitor to the user's own website: country and city, device and browser, acquisition source, activity (visit and pageview counts, visited pages, completed goals), revenue totals, whether the visitor is identified, and a timeline of pageviews, goals, and purchase amounts, newest first. Names, emails, user IDs, IP addresses, and card or billing details are never returned. Call it only when the user asks about a specific visitor, and share only what answers the question. profile is null for anonymous visitors; each list is capped at the 100 most recent items. Use the aggregate get_* tools for questions about many visitors. visitorId is the visitor record ID from get_realtime_map or the dashboard visitor view, not the _fs_vid cookie value; an unknown id, or one from another website, fails with 'Visitor not found'. Requires websiteId or domain with a workspace token.
Inputs: visitorId (required), domain, websiteId, workspaceId. Returns: result
list_issuesList Detected IssuesARead-onlyIdempotent
List issues the AI found while analyzing session recordings: bugs, broken flows, and UX problems, deduplicated across sessions and ranked by severity (or by last seen with sort recency). Each row has title, severity, status, sessions affected, and first/last seen; the response also carries site-wide open, in_progress, and resolved counts plus pagination.total. Start here for 'what is broken', then call get_issue with an id for occurrences, steps to replicate, and comments. Suspended issues are hidden unless status is suspended, so an issue that vanished was probably suspended, not deleted. On a free trial only the first 10 issues are listed and counted. Requires websiteId or domain with a workspace token.
Inputs: sort, limit, domain, offset, +5 more. Returns: result
list_websitesList WebsitesARead-onlyIdempotent
List the websites the current API token can read, with id, domain, timezone, currency, and KPI goal per site. A workspace token (flow_ws_) returns every website in the workspace; a website key (flow_) returns only its own. Call this first with a workspace token: every other tool then needs websiteId or domain from this list, and omitting both fails with 'Website ID or domain is required'. Takes no parameters. Use get_metadata instead when you already know the website and only need its settings.
Inputs: workspaceId. Returns: result
list_workspacesList WorkspacesARead-onlyIdempotent
List the workspaces this sign-in can act in, across every organization the user belongs to. Returns { status, data } with one entry per workspace: id, name, organization { id, name }, role { key, name }, permissions, isDefault and current. Call this when the user names a workspace, client or organization, or when data they expect is missing, then pass the matching id as workspaceId to every other tool. Without workspaceId, tools act in the workspace marked current. A workspace API token (flow_ws_) belongs to one workspace, so it lists only that one; a website key (flow_) belongs to one website and fails with a 400 here. Takes no arguments.
Inputs: no named parameters. Returns: result
track_goalTrack Goal EventA
Record one completion of a custom goal. The goal is created on first use, so no setup call is needed. Pass visitorUid (the anonymous visitor ID Flowsery assigned on the user's own website) so the completion attaches to that visitor's sessions and source; omit it for an anonymous completion. Each call appends a completion, so repeating it counts the goal twice. Use track_payment for revenue, which records a payment goal on its own. Undo with delete_goals. Requires websiteId or domain with a workspace token.
Inputs: name (required), domain, metadata, timezone, +4 more. Returns: result
track_paymentTrack PaymentADestructive
Record an analytics payment; this never charges a customer, moves money, or issues a refund. Revenue appears in get_overview, get_timeseries, every breakdown's revenue column, and the visitor profile. Skip it when the site's provider (Stripe, LemonSqueezy, Polar, and other connected providers) is tracked automatically, or the revenue is counted twice; use track_goal for conversions without revenue. transactionId must be unique: a repeated id is rejected, not deduplicated. A new payment also records a payment goal completion (free_trial when amount is 0); isRenewal skips that. isRefund with an existing transactionId overwrites that payment's recorded refund amount and any supplied customer attribution instead of adding a row. Attribution looks up a known visitor by visitorUid, customerId, or email; with no match the revenue is kept but its source shows as Unknown. Send email and name only when the user supplied them and wants the payment attributed. Undo with delete_payments. Requires websiteId or domain with a workspace token.
Inputs: amount (required), currency (required), transactionId (required), name, +13 more. Returns: result
update_issue_statusUpdate Issue StatusADestructiveIdempotent
Set an issue's status to open, in_progress, resolved, or suspended and return the updated issue. Only the status changes; title, severity, occurrences, and comments stay, and any status can be set again later, so this is reversible. Confirm which state the user means before calling: resolved asserts the bug is fixed, suspended hides a known non-problem from the default list_issues result. Not a delete: issues cannot be removed through this server. Get issueId from list_issues; an unknown id fails with 'Issue not found', and on a free trial issues beyond the first 10 fail as not included in the current plan. Requires websiteId or domain with a workspace token.
Inputs: status (required), issueId (required), domain, websiteId, +1 more. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 28 tools
The reporting tools are cleanly separated in intent (overview vs timeseries vs realtime, and the geographic/device/browser breakdowns are explicitly ranked coarse-to-fine with cross-references). The main overlap is get_breakdown, which duplicates roughly a dozen named breakdown tools and partially overlaps get_metadata/list_websites, but descriptions explicitly say the dedicated tools return identical rows and steer usage, so misselection risk is low rather than absent.
Every name is snake_case verb_noun with a predictable verb set: get_* for reads, list_* for enumerations, track_* for writes, delete_* for removals, update_issue_status for mutation. The noun matches the returned resource in all cases, so an agent can guess a name from intent.
28 tools exceeds a comfortable scope, and a large share of them (pages, referrers, countries, regions, cities, devices, browsers, OSes, campaigns, hostnames, channels, goals) are thin conveniences over the generic get_breakdown. Each is individually justified by the dimension it names, but the surface is heavier than the domain strictly requires.
Analytics coverage is broad: traffic, trends, realtime, geography, tech, acquisition, goals, revenue, visitor-level detail, plus AI issues with status transitions and goal/payment deletion for undo. Notable gaps remain around session/recording retrieval (sessions are exposed ids inside get_issue but no tool fetches one) and website/workspace management beyond listing.
Maintenance
Related MCP Connectors
Cookieless analytics for agents: visitors, pages, sources, AI crawlers, funnels and revenue.
Web analytics for AI agents: realtime visitors, revenue, funnels and AI-detected site issues
Real-time web analytics for AI agents: query traffic, funnels, revenue, and manage your sites.
Analytics your AI agent can actually use. Track, experiment, and optimize via MCP.
Related MCP Servers
- AlicenseCqualityBmaintenanceFull-coverage MCP server for Umami Analytics API v2 — 66 tools for website analytics, stats, events, and team management13368 npm8MIT
- AlicenseAqualityDmaintenancePrivacy friendly, cookieless web analytics built MCP-first. "Add analytics to my Next.js app" → an AI agent runs the setup_analytics_for_site tool, picks the right install snippet, edits your layout file, and verifies the script is loading. OAuth onboarding, no API keys to paste.281MIT
- AlicenseAqualityDmaintenanceEnables AI agents to access website analytics, including visitor sessions, UX friction, conversion funnels, and anomaly alerts.632 PyPIMIT
- AlicenseAqualityBmaintenanceMCP server for Plausible Analytics that enables querying traffic, conversions, and comparing time periods from any AI tool supporting MCP.452MIT