Flowlines MCP server
ai.flowlines · Updated
MCP observability: analyse MCP server usage, investigate sessions, and instrument MCP servers.
At a glance
Flowlines is an MCP server in the Other category. It is hosted remotely and connects over HTTP, and declares no required credentials. It scores B (68/100) on the MCP Skills Hub health score as of Oct 28, 2026.
One-click install
Opens your editor and pre-fills the config. Your editor will ask before adding it.
How to install Flowlines in your AI client
Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.
How to install Flowlines in Claude CodeAnthropic's agentic CLI
Add the server
bashclaude mcp add --transport http flowlines https://api.flowlines.ai/mcpVerify it's connected
bashclaude mcp listSharing it with your team?
Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).
Use it in a session
Ask Claude to use the tools this server exposes. It discovers them automatically.
How to install Flowlines in Claude DesktopDesktop app (MCP config)
Open your MCP config
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
Add this server
json{ "mcpServers": { "flowlines": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.flowlines.ai/mcp" ] } } }Why the wrapper?
This is a remote (HTTP) server and Claude Desktop only launches local processes, so mcp-remote proxies the connection. It will open a browser window if the server needs OAuth.
Restart Claude Desktop
The tools appear under the 🔌 menu once the app reloads.
How to install Flowlines in CursorAI-first code editor
Create / edit .cursor/mcp.json in your project
json{ "mcpServers": { "flowlines": { "url": "https://api.flowlines.ai/mcp" } } }Enable it
Cursor Settings → MCP → toggle the server on. Tools become available to the Composer/Agent.
How to install Flowlines in Codex CLIOpenAI coding agent
Add to ~/.codex/config.toml
toml[mcp_servers.flowlines] command = "npx" args = ["-y", "mcp-remote", "https://api.flowlines.ai/mcp"]Why the wrapper?
Codex runs MCP servers as local processes, so mcp-remote bridges this HTTP endpoint to stdio.
Run Codex
Codex loads MCP servers from config.toml on startup and exposes their tools to the agent.
How to install Flowlines in WindsurfCodeium's agentic IDE
Edit ~/.codeium/windsurf/mcp_config.json
json{ "mcpServers": { "flowlines": { "serverUrl": "https://api.flowlines.ai/mcp" } } }Reload
Windsurf → Cascade → refresh MCP servers. Cascade can now call the tools.
How to install Flowlines in ClineVS Code autonomous agent
Open Cline → MCP Servers → Configure
Adds to cline_mcp_settings.json.
Add the server
json{ "mcpServers": { "flowlines": { "type": "streamableHttp", "url": "https://api.flowlines.ai/mcp" } } }
How to install Flowlines in VS CodeCopilot / MCP support
Create .vscode/mcp.json
json{ "servers": { "flowlines": { "type": "http", "url": "https://api.flowlines.ai/mcp" } } }Start it
VS Code shows a ▶ Start action above the server entry. Agent mode (Copilot Chat) can then use the tools.
What tools does Flowlines expose?
This server requires credentials before it will list its tools, so we cannot enumerate them here. Connect it in your client to see what it offers.
What the code can do
This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.
Before you install
Signals gathered from the source repo and package registry — not a safety verdict.
What it can reach
- Third-party hosted service — Your requests and any data in them are sent to api.flowlines.ai.
- No local execution — Nothing is installed or run on your machine.
- Last commit today — Actively maintained.
- Repository created 1 month ago — Very new project with little track record yet.
- 0 GitHub stars — Very little community usage so far.
Client compatibility
Health score
B · 68Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated
- Maintenance30%100%
Last commit 0 days ago.
- Adoption20%0%
0 stars.
- Transparency20%75%
3/4: ✓ public source repo, ✓ declared license, ✓ documentation, ✗ discoverable tool list.
- Provenance15%75%
Links to its own repository; package linkage unverified.
- Packaging15%75%
Remote endpoint; authentication requirements not declared.
Documentation
Full READMEFlowlines plugins
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. |
Privacy notice
- The Flowlines MCP server reads production MCP sessions, tool calls, and user activity. Treat everything it returns as confidential; it never writes to your namespace except through the explicit
save_noteandreport_outcometools. - An MCP server instrumented from the
onboardingplan 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.
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.
Install
ChatGPT and Codex public plugin
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 Code
claude plugin marketplace add flowlines-ai/plugins && claude plugin install flowlines@flowlinesThen 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.
Local desktop testing
Excerpt — the full document is on GitHub.
Alternatives to Flowlines
Maintain Flowlines? Add a badge to your README
Shows its health grade, and links readers to install steps for every client.
[](https://mcp-skills-hub.vercel.app/mcps/ai-flowlines-flowlines)Catalog data refreshed . Something wrong? Report it.