MCP observability: analyse MCP server usage, investigate sessions, and instrument MCP servers.
MCPpedia last refreshed this data
ai.flowlines/flowlines is an MCP server that MCP observability: analyse MCP server usage, investigate sessions, and instrument MCP servers. Its tool list has not been published yet over http, requires no API key, and scores 70/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
https://api.flowlines.ai/mcpRemote servers are added as connectors, not in claude_desktop_config.json, which is for local servers.
Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
MCP observability: analyse MCP server usage, investigate sessions, and instrument MCP servers.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in analytics
Ask your agent about your own Apple Health data: 194 metrics, 21 tools, local, 0 deps.
MCP server for Dynatrace Managed to access logs, events, and metrics.
Official PostHog MCP Server for product analytics, feature flags, experiments, and more.
Read and manage Churnkey cancel flows, retention metrics, and payment recovery
MCP Security Weekly
Get CVE alerts and security updates for ai.flowlines/flowlines and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Official Flowlines plugins for MCP observability. This repository ships the portable flowlines plugin, marketplaces for Claude Code and Codex, and a Cursor plugin manifest (plugins/flowlines/.cursor-plugin/plugin.json) for cursor.directory:
| Component | What it does |
|---|---|
flowlines MCP server | Connects your MCP client to your Flowlines workspace at https://api.flowlines.ai/mcp. Inspect how people use your MCP servers, what changed since a release, and where sessions go wrong. Record findings as notes. Its onboarding tool returns an instrumentation plan; check_onboarding checks the telemetry that arrives. |
flowlines-weekly-review skill | A periodic review over the MCP server: what changed since the last review, signals, outcome movements, and what to pin for next time. |
flowlines-release-check skill | Before-and-after comparison of an MCP server release: outcomes, intents, cost, signals, and evidence sessions, with the right denominators. |
flowlines-investigate-session skill | From a signal, a user, or a complaint to the failing turn, with minimal exposure of end-user content. |
flowlines-cohort-builder skill | Sizes a user segment, writes it in the Flowlines cohort rule vocabulary, and compares it against a baseline. |
flowlines-doctor skill | Diagnoses missing or incomplete data across every source: instrumented MCP servers, LangSmith and Langfuse connectors, and OTLP applications. |
save_note and report_outcome tools.onboarding plan exports validated tool arguments, client-visible results, and user identity metadata to Flowlines. That data can contain personal data, customer data, source code, or other sensitive content. You choose what it records on the Flowlines get-started page.reason and user_intent are short sentences that the calling model writes, and they do not need to identify anyone. If your privacy rules do not allow user_intent, keep it and remove the identity instead: send no user.name or user.email, and send an HMAC-SHA-256 of your user ID as user.id. The hash stays the same for one user, so Flowlines still groups the calls into sessions. Without user_intent, only clients that send a session ID get sessions.onboarding and check_onboarding are read-only: they return an instrumentation plan and check the calls that arrive. The namespace API key is created on the Flowlines get-started page and shown once there; never paste it into chat.
The public distribution target is one Flowlines plugin with the hosted MCP server and four shared analysis skills in OpenAI's Plugins Directory. This repository prepares its submission; merging changes does not publish it or install it for users. A public listing and installation reuse across products still require review and verification.
See the shared plugin guide for the build and verification steps, and the submission worksheet for listing assets and review cases. The existing desktop marketplace installs below continue to work. Personal ChatGPT accounts can test the server separately through Developer mode while the public submission is being prepared.
claude plugin marketplace add flowlines-ai/plugins && claude plugin install flowlines@flowlines
Then run /mcp inside Claude Code and sign in to flowlines. Skills are available as /flowlines:<skill-name>, for example /flowlines:flowlines-weekly-review or /flowlines:flowlines-doctor. Add --scope project to the install command to enable the plugin for one repository only.