Flowlines
ChatGPT pluginUnderstand your MCP servers
Connect your Flowlines account to review MCP server activity, compare outcomes before and after a release, investigate unsuccessful sessions, and analyse user cohorts. Use aggregate metrics and focused session evidence to explain findings. Save verified findings as workspace notes when requested. Requires a Flowlines account with access to a workspace containing MCP telemetry.
- Featured
- No
not on the featured shelf
Movement
From our daily snapshots over the last 30 days.
Rank by placement
Rank in Developer tools
6 listing changes logged · latest Oct 22: Capabilities, Description, Skills and 3 more. See what changed
In its category
How this plugin compares with others in the same category. Positions are counted within the category, not across the whole directory.
Developer tools257th of 900 by placement
| # | Plugin | Position | 7d |
|---|---|---|---|
| 255 | #3616 | 49places up | |
| 256 | #3658 | 66places up | |
| 257 | #3679 | 38places up | |
| 258 | #3680 | 52places down | |
| 259 | #3708 | 53places up |
Example prompts
- “What changed in my Flowlines namespace this week?”
- “Compare MCP session outcomes before and after my latest server release.”
- “Investigate unsuccessful sessions in my Flowlines workspace.”
Skills
flowlines-cohort-builder
Turn a question about a group of users ("which users do X", "who is at risk", "how do power users differ") into a Flowlines cohort - size it, express it in Flowlines cohort rules, hand the definition to the app, and compare it against a baseline over the Flowlines MCP server. Use when the user asks about segments, populations, or comparing groups of users. Do not use for one user's activity (flowlines-investigate-session) or for a namespace review (flowlines-weekly-review).
flowlines-investigate-session
Investigate a specific problem in Flowlines - a signal, a user complaint, a failed session, or a suspicious pattern - from the aggregate down to the exact turn, over the Flowlines MCP server, while handling end-user data with care. Use when the user asks why something went wrong, wants to look into a signal or a user's sessions, or needs evidence for a bug report. Do not use for periodic reviews (flowlines-weekly-review), release comparisons (flowlines-release-check), user segments (flowlines-cohort-builder), or data that is not arriving (flowlines-doctor).
flowlines-release-check
Check whether an MCP server release changed session outcomes in Flowlines - compare sessions, success rates, intents, cost, and signals before and after a deploy over the Flowlines MCP server. Use when the user asks whether a deploy, prompt change, or new version regressed or improved anything, or wants a go/no-go after shipping. Do not use for a general review of the namespace (flowlines-weekly-review), one failing session (flowlines-investigate-session), or missing data (flowlines-doctor).
flowlines-weekly-review
Produce a periodic review of a Flowlines namespace over the Flowlines MCP server - what changed since the last review, which signals fired, where outcomes moved, and what to pin for next time. Use only when the user explicitly asks for a weekly, monthly, or periodic review, a status report, or what changed over a period. Do not use for a single question about a metric, a session, a user, a release, or missing data; answer those directly with the MCP tools or use the matching Flowlines skill.
- Categories
- Sign-in
- On Install
- Capabilities
- Read, Write
- Availability
- Available
- Version
- 0.4.1
- Keywords
- flowlines, observability, mcp, telemetry, opentelemetry, analytics
- Created
- September 9, 2026
- More info
- Sponsorship
- Promote this plugin