← Plugin catalog
Developer Tools

Flowlines

Flowlines v0.4.1

Understand your MCP servers

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Read
  • Write

Not specified in the available declarations: limitations, pricing & account requirements.

Onboarding example

What changed in my Flowlines namespace this week?
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 20, 2026. Package observed Nov 19, 2026.

View package source →

Description

From the marketplace listing

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.

Language: English · Automatically detected from descriptions.

What changed

· 7 observations

Capabilities & instructions

Full description changed from “when the user asks what changed, wants a weekly or monthly review, or asks for a status report on their agents.” to “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...”. Skill...

View comparison →
Capabilities & instructions

Full description changed from “a release of an agent changed its outcomes in Flowlines - compare sessions, success rates, intents, cost, and signals before and after a deploy over the...” to “an MCP server release changed session outcomes in Flowlines - compare sessions, success rates, intents, cost, and signals...

View comparison →
Pricing references

Full description: added “Do not use for periodic reviews (flowlines-weekly-review), release comparisons (flowlines-release-check), user segments (flowlines-cohort-builder), or data...”. Skill instructions changed from “--- # Flowlines session investigation Go from a symptom to a verifiable cause with the smallest...

View comparison →
Capabilities & instructions

Full description: added “Do not use for one user's activity (flowlines-investigate-session) or for a namespace review (flowlines-weekly-review).”. Skill instructions changed from “--- # Flowlines cohort builder A cohort is a saved rule set over a user aggregate that Flowlines keeps up to date and can compare against...

View comparison →
Capabilities & instructions

Is template instance added: “false”. App-6aa11dfaeb20819187226d4810e1d94a updated; open the comparison for details. Flowlines updated; open the comparison for details. Full description changed from “Connect your Flowlines account to review AI agent activity, compare outcomes across time periods, investigate...

View comparison →
Capabilities & instructions

Is template instance added: “false”. App-6aa11dfaeb20819187226d4810e1d94a updated; open the comparison for details. Flowlines updated; open the comparison for details. Full description changed from “Connect your Flowlines account to review AI agent activity, compare outcomes across time periods, investigate...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package16 files · 19.3 KBBrowse files →
Skill instructions
flowlines-cohort-builder6.79 KB

View saved version →

---
name: flowlines-cohort-builder
description: 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 cohort builder

A cohort is a saved rule set over a user aggregate that Flowlines keeps up to date and can compare against other cohorts. This skill sizes a candidate group with the MCP tools, writes the definition in the exact rule vocabulary, and verifies it once it exists.

## Tool discipline

- The Flowlines MCP server is the only data source for this skill. Do not open the Flowlines app, drive a browser, use computer-use, or search the web to find data, unless the user explicitly asks you to.
- When the server cannot answer part of the question, say so in the answer and list it in `unmet_needs` of `report_outcome`. If the information lives in the Flowlines app, tell the user where to look; do not go there yourself.
- Match the effort to the question. For a plain question, make the minimum calls (`get_workspace`, `get_context`, then the one or two tools that answer it), answer, and `report_outcome`. Run the full procedure below only when the user asks for a cohort definition or a cohort comparison, and skip `save_note` and evidence sessions unless the procedure runs in full or the user asks for them.
- If authentication is required, or a generic MCP error (such as `-32603`) repeats on one read-only check, use `flowlines-doctor` when available for connection recovery before further data calls. Client diagnostics and native sign-in are allowed for this repair. After verification, resume the original request with the same namespace, range, and `user_intent`.
- If `flowlines-doctor` is unavailable, use only the failing client's connection status and native reconnect action. Reconnect once only when that client reports an authentication problem; leave browser consent to the user, then verify with one read-only call. If the action is unavailable, give the user the reconnect step in their client and wait for completion. For an unexplained generic error or failed verification, stop data calls, give the user the error and a pointer to Flowlines support. Do not access Flowlines infrastructure or present unavailable data as empty.

## Conventions for every Flowlines tool call

- Every tool takes `reason` and `user_intent`. Keep `user_intent` identical across the conversation, for example "Identify users who churned after a frustrated session".
- Start with `get_workspace` once, then `get_context`. Pinned notes may already describe the population the user is asking about.
- Cohorts are about people. Report them in aggregate; open individual users only to validate a rule, and mask identifiers.
- End with `report_outcome` as the last tool call.

## What the MCP server can and cannot do

The MCP server reads cohorts and compares them: `list_cohorts`, `get_cohort`, `compare_cohorts`, plus `list_users`, `get_user_population_map`, and `aggregate_sessions` with `cohort_ids` and `group_by: ["cohort"]`. Creating or editing a cohort happens in the Flowlines app, in the cohort builder on the Users view, or through the REST API with a signed-in user session. Namespace API keys only authenticate ingestion, so this skill produces a definition ready to paste into the builder and verifies the result afterwards. Do not open the app to create the cohort yourself unless the user explicitly asks; hand the definition over and wait.

## Steps

1. Restate the question as a rule. Every cohort rule has a `kind`; the vocabulary and operators are in [references/cohort-rules.md](references/cohort-rules.md). Examples:
   - "users

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.

flowlines-investigate-session6.24 KB

View saved version →

---
name: flowlines-investigate-session
description: 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 session investigation

Go from a symptom to a verifiable cause with the smallest exposure of end-user content. Aggregates first, then the session, then only the turns that matter.

## Tool discipline

- The Flowlines MCP server is the only data source for this skill. Do not open the Flowlines app, drive a browser, use computer-use, or search the web to find data, unless the user explicitly asks you to.
- When the server cannot answer part of the question, say so in the answer and list it in `unmet_needs` of `report_outcome`. If the information lives in the Flowlines app, tell the user where to look; do not go there yourself.
- Match the effort to the question. For a plain question, make the minimum calls (`get_workspace`, `get_context`, then the one or two tools that answer it), answer, and `report_outcome`. Run the full procedure below only when the user asks for an investigation or evidence for a report, and skip `save_note` and evidence sessions unless the procedure runs in full or the user asks for them.
- If authentication is required, or a generic MCP error (such as `-32603`) repeats on one read-only check, use `flowlines-doctor` when available for connection recovery before further data calls. Client diagnostics and native sign-in are allowed for this repair. After verification, resume the original request with the same namespace, range, and `user_intent`.
- If `flowlines-doctor` is unavailable, use only the failing client's connection status and native reconnect action. Reconnect once only when that client reports an authentication problem; leave browser consent to the user, then verify with one read-only call. If the action is unavailable, give the user the reconnect step in their client and wait for completion. For an unexplained generic error or failed verification, stop data calls, give the user the error and a pointer to Flowlines support. Do not access Flowlines infrastructure or present unavailable data as empty.

## Conventions for every Flowlines tool call

- Every tool takes `reason` and `user_intent`. Keep `user_intent` identical across the conversation, for example "Find out why the billing MCP server fails on refund requests".
- Start with `get_workspace` once, then `get_context` for the namespace. Read pinned notes first: the problem may already be a known artifact.
- Flowlines data is real production conversations. Quote the minimum, mask names, emails, phone numbers, addresses, identifiers, and payment details, and never copy a transcript into a note, ticket, or report.
- End with `report_outcome` as the last tool call.

## Starting points

Pick the entry that matches what the user has:

- **A signal.** `list_signals` to find it, then `get_signal` for evidence and affected sessions and users.
- **A user.** `get_user_activity` for the timeline, outcomes, MCP servers, intents, signals, and representative sessions. Prefer this over listing that user's sessions.
- **A session id.** `get_session` directly.
- **A description.** `search` with `types` narrowed to `session` or `turn`, a time window, and the MCP server, then `fetch` the locators worth opening.
- **A pattern.** `aggregate_sessions` grouped by `intent`, `agent`, or `day` with `failure_rate` and `failure_count`, ordered by the metric, to find where the problem concentrates before opening anything.

## Steps

1. Scope the proble

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

flowlines-mcp-observability11.2 KB

View saved version →

---
name: flowlines-mcp-observability
description: Integrate, repair, review, or verify Flowlines observability in an MCP server repository. Use when a server must emit canonical Flowlines MCP tool-call telemetry through AGNTCY Observe or vanilla OpenTelemetry; do not use for Claude Code or Codex CLI telemetry.
---

# Flowlines MCP Observability

Instrument an MCP server so complete tool executions arrive in Flowlines as canonical MCP calls. Modify the target server; do not add a Flowlines runtime SDK or assume ownership of unrelated telemetry.

## Consent and secrets

Before changing code or deployment configuration:

1. Explain that supported MCP spans export validated tool arguments, final client-visible results, and user identity metadata to Flowlines. Identity metadata includes a stable user ID and, when available, name and email; these fields and payloads may contain personal data, customer data, source code, file content, or other sensitive values.
2. Obtain explicit consent for payload export. Do not infer it from a generic request to "add telemetry."
3. Confirm the user has a Flowlines namespace API key before touching the deployment. If they do not, tell them to create one in the Flowlines app under Settings, API keys, at `https://app.flowlines.ai/settings` for the namespace that should receive the data, and offer to open that page for them (`open` on macOS, `xdg-open` on Linux). The key is shown once at creation. Ask the user to place it in the target deployment's secret manager. Never request the key in chat, write it into source or examples, interpolate it into a command, or print an existing value.
4. Treat the integration request as permission to edit and test the target repository, not to deploy it, call production tools, or mutate any production database.

Read [references/contract.md](references/contract.md) before implementing or reviewing an integration.

## Inspect the target first

Read the repository instructions, architecture documentation, and testing strategy. Then identify:

- language, runtime, MCP SDK and transport;
- package manager, lockfile, dependency policies, and supported runtime versions;
- the central tool-registration or dispatch boundary;
- existing MCP-level middleware or interceptors;
- existing OpenTelemetry provider, exporter, collector, propagation, and shutdown handling;
- where validated arguments, request ID, request `_meta`, authenticated user ID/profile, final MCP result, and error mapping are available;
- how deployment secrets and environment variables are declared without values.

Preserve the target's package manager and telemetry ownership. Reuse an existing tracer provider and collector when present; never register a competing global provider or replace unrelated exporters.

## Choose the integration path

- For a compatible Python server using the official `mcp` package, prefer AGNTCY Observe. Read [references/python-agntcy.md](references/python-agntcy.md).
- For TypeScript or any other language with an OpenTelemetry SDK, use vanilla OpenTelemetry. Read [references/vanilla-opentelemetry.md](references/vanilla-opentelemetry.md).
- On the vanilla path, prefer the framework's existing MCP-level middleware or interceptor at `tools/call` as the default span boundary. Typical hooks: Go `AddReceivingMiddleware`, FastMCP `on_call_tool`, official Python `server.middleware` filtered to `tools/call`, or the equivalent TypeScript hook. Do not use HTTP, transport, or sending middleware as the Flowlines MCP span boundary; resolve identity from those layers when needed, then emit the span at MCP `tools/call`.
- If automatic instrumentation or that middleware hook cannot observe the final client-visible result, validated arguments, or request metadata, keep a single wrapper around the central tool execution boundary and capture the missing fields there. Do not scatter nearly identical span code across every handler unless the framework provides no shared boundary. Do not emit Flowlines 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 4 — file references are metadata, not package contents.

flowlines-release-check8.15 KB

View saved version →

---
name: flowlines-release-check
description: 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 release check

Answer "did the last release change anything?" with numbers that have the right denominators, evidence from real sessions, and an honest statement of what cannot be known yet.

## Tool discipline

- Answer from the Flowlines MCP server first. It holds the data this skill works on, and every step below is written for its tools.
- Use the Flowlines app, a browser, or web search only when the server cannot provide something the question needs, or when the user asks for it. Say that you are doing so and why. Never use them for data the server exposes, and never as a first move.
- When part of the question stays unanswered, say so in the answer and list it in `unmet_needs` of `report_outcome`, with a pointer to where the user can look.
- Match the effort to the question. For a plain question, make the minimum calls (`get_workspace`, `get_context`, then the one or two tools that answer it), answer, and `report_outcome`. Run the full procedure below only when the user asks for a release check or a go/no-go, and skip `save_note` and evidence sessions unless the procedure runs in full or the user asks for them.
- If authentication is required, or a generic MCP error (such as `-32603`) repeats on one read-only check, use `flowlines-doctor` when available for connection recovery before further data calls. Client diagnostics and native sign-in are allowed for this repair. After verification, resume the original request with the same namespace, range, and `user_intent`.
- If `flowlines-doctor` is unavailable, use only the failing client's connection status and native reconnect action. Reconnect once only when that client reports an authentication problem; leave browser consent to the user, then verify with one read-only call. If the action is unavailable, give the user the reconnect step in their client and wait for completion. For an unexplained generic error or failed verification, stop data calls, give the user the error and a pointer to Flowlines support. Do not access Flowlines infrastructure or present unavailable data as empty.

## Conventions for every Flowlines tool call

- Every tool takes `reason` and `user_intent`. Keep `user_intent` identical across the conversation, for example "Check whether the 2026-09-01 release of the support MCP server regressed session outcomes".
- Start with `get_workspace` once, then `get_context` for the namespace. Read pinned notes: a known evaluator artifact or ingestion gap changes how a comparison reads.
- Quote the minimum from sessions and mask identifiers. Prefer aggregates.
- End with `report_outcome` as the last tool call.

## Inputs

1. The MCP server. `list_agents` shows the service names Flowlines observes; use the exact name in `agent_name` filters.
2. The release boundary as an ISO 8601 timestamp. Take it from the user or the deploy log. If neither gives it, the release list in the Flowlines app under Versions has it and the MCP server does not; read it there or ask the user. Flowlines records a release either from a reported version or from a detected prompt change; the app's release receipt shows which.
3. The comparison window. Default to the same number of days on each side of the boundary, at least 3 and at most 14, so both sides have comparable traffic. Say when the after-window is still short.

## Steps

1. `get_changes_since` with `since` set to the release boundary. This gives the after-side activity, outcomes, s

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

flowlines-weekly-review7.89 KB

View saved version →

---
name: flowlines-weekly-review
description: 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.
---

# Flowlines weekly review

Turn the Flowlines MCP tools into one repeatable review with a fixed shape, so successive reviews are comparable and nothing already known is re-derived.

## Tool discipline

- The Flowlines MCP server is the only data source for this skill. Do not open the Flowlines app, drive a browser, use computer-use, or search the web to find data, unless the user explicitly asks you to.
- When the server cannot answer part of the question, say so in the answer and list it in `unmet_needs` of `report_outcome`. If the information lives in the Flowlines app, tell the user where to look; do not go there yourself.
- Match the effort to the question. For a plain question, make the minimum calls (`get_workspace`, `get_context`, then the one or two tools that answer it), answer, and `report_outcome`. Run the full procedure below only when the user asks for a review or a status report, and skip `save_note` and evidence sessions unless the procedure runs in full or the user asks for them.
- If authentication is required, or a generic MCP error (such as `-32603`) repeats on one read-only check, use `flowlines-doctor` when available for connection recovery before further data calls. Client diagnostics and native sign-in are allowed for this repair. After verification, resume the original request with the same namespace, range, and `user_intent`.
- If `flowlines-doctor` is unavailable, use only the failing client's connection status and native reconnect action. Reconnect once only when that client reports an authentication problem; leave browser consent to the user, then verify with one read-only call. If the action is unavailable, give the user the reconnect step in their client and wait for completion. For an unexplained generic error or failed verification, stop data calls, give the user the error and a pointer to Flowlines support. Do not access Flowlines infrastructure or present unavailable data as empty.

## Conventions for every Flowlines tool call

- Every tool takes `reason` (why this call) and `user_intent` (the user's goal, identical across the conversation). Set `user_intent` once, for example "Weekly review of the <namespace> namespace".
- Start with `get_workspace` once, pick the namespace, then `get_context` for that namespace. Read its pinned notes and glossary before analysing: notes record known caveats and confirmed findings.
- Prefer aggregates over transcripts. Open a session only as evidence for a claim, quote the minimum, and mask names, emails, and other identifiers.
- End with `report_outcome` as the last tool call, before the final answer, with `unmet_needs` for anything the server could not provide.

## Inputs

Ask for, or infer, three things:

1. The namespace. If `get_workspace` shows exactly one, use it silently.
2. The review window. Default to the last 7 days. `get_changes_since` needs an ISO 8601 `since` timestamp and clamps to the trailing 90 days; take `since` from the previous review's pinned note when one exists, otherwise from the window.
3. Focus MCP servers, if the user names any. Otherwise cover every MCP server with activity.

## Steps

1. `get_context` with `overview_range` matching the window (`7d` for a weekly review, `30d` for a monthly one). Record the context status; if it is `not_configured`, `gathering`, or `failed`, say so and continue without it.
2. `list_notes`. Find the most recent note whose title starts with `Weekly review` and 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package license
MIT
Package author
Flowlines
Keywords
See keywords

Declared capabilities

  • Read
  • Write

Package observed Nov 19, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 20, 2026 · 00:00 UTC
Latest observed change
Oct 24, 2026 · 13:14 UTC
Collection status
Collected

plugin_asdk_app_6aa11dfaeb20819187226d4810e1d94a

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.