Flowmind
Memory and workflow automation for MCP, Codex, and Claude Code. Reuse repeatable developer operations through skills and explicit feedback.
Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability
Work: Infrastructure and deployment
Who it is for: DevOps / SRE
Install (Claude Code):
claude mcp add flowmind -- npx -y flowmind- tashan score: 57.0
- Adoption: 66/wk
- Upkeep: 73.0
- Freshness: 100.0
- Evidence coverage: 100% of the inputs this score can use
- Health: active
- License: MIT
Security audit
scanned 2026-08-10Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.
What changed recently
- 2026-08-10 flowmind now reaches filesystem Its declared dependencies reach further into your machine than they did before.
You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.
You searched for one. Check the rest of your stack:
npx tashan-cli doctorReads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.
We recorded 1 change to Flowmind in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.
- Every score since we started measuring, for any capability
- The named replacement when something you run is dying — not just that it is
tashan doctorover the config you already have, on your machine
Start a 7-day trial › Everything measured on this page stays free.
npm ↗ · source ↗ · pkg:flowmind
Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›
Measured 2026-08-15 · scorer s5 · how · something wrong here?