FlowMind MCP server
Commit Nov 4, 2026Turns common developer operations into reusable skills that learn from user corrections and local knowledge.
Also known as Eleven-M/flowmind
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 4, 2026
- License
- MIT
What is FlowMind MCP?
FlowMind turns common developer operations into reusable skills that learn from user corrections and local knowledge.
Summary generated from the project's README
About FlowMind MCP server
FlowMind acts as a reusable workflow layer that transforms standard developer tasks into specialized skills. It allows users to load local knowledge, query logs, review code, and check design rules. The system is designed to learn from user corrections and local context, storing these preferences as reusable state in a local directory. This makes it useful for developers who want their AI tools to remember specific formatting preferences or preferred analysis routes.
Users can deploy this as an MCP server for Claude or WorkBuddy, or use the JSON-friendly wrapper for Codex. Setup involves importing a Markdown configuration package to generate local JSON files for AI, resources, components, and skills. While it can run without an AI provider for offline analysis and demos, real-world tasks like database or deployment skills require configured MCP resources or adapters. The system also supports decision-provider routing, allowing specific models like jev to handle skill selection tasks.
What you can do with it
- 1Audit system logsAsk the AI to query specific trace IDs or log chains using the log-audit skill.
- 2Perform code reviewsRequest a review of staged changes based on established design rules.
- 3Analyze local architectureSummarize the design and implementation flow of a project while working offline.
- 4Validate data consistencyUse a specific skill to check if order data remains consistent across the system.
Written from the project's README. Every use case is checked against a quote from it.
How to install FlowMind MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall FlowMind MCP in Claude Code
$ claude mcp add flowmind -- npx -y flowmindInstall FlowMind MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"flowmind": {
"command": "npx",
"args": [
"-y",
"flowmind"
]
}
}
}Install FlowMind MCP in VS Code
.vscode/mcp.json
{
"servers": {
"flowmind": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"flowmind"
]
}
}
}Install FlowMind MCP in VS Code CLI
$ code --add-mcp '{"name":"flowmind","type":"stdio","command":"npx","args":["-y","flowmind"]}'Install FlowMind MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"flowmind": {
"command": "npx",
"args": [
"-y",
"flowmind"
]
}
}
}Install FlowMind MCP in Codex
$ codex mcp add flowmind -- npx -y flowmindInstall FlowMind MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.flowmind] command = "npx" args = ["-y", "flowmind"]
Install FlowMind MCP in Gemini CLI
$ gemini mcp add -s user flowmind npx -- -y flowmindInstall FlowMind MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"flowmind": {
"command": "npx",
"args": [
"-y",
"flowmind"
]
}
}
}Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableeleven-m/flowmind is public and reachablegithub.com/eleven-m/flowmind ↗Pass
- Package names this repository as its sourceflowmind names eleven-m/flowmind as sourcenpmjs.com/package/flowmind ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-04github.com/eleven-m/flowmind ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from flowmindPass
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubFlowMind
A reusable workflow layer for Codex, Claude, WorkBuddy, and MCP tools
FlowMind turns common developer operations into skills: load local knowledge, query logs, review code, check design rules, and reuse what it learns from your corrections.
中文 | Integration | Skills | Security | Changelog
Where development happens: FlowMind is developed in the open on GitHub — this repository is the single source of truth. The npm
flowmindpackage is a frozen snapshot (v2.3.1); new releases are published here first.
Install
From GitHub (primary, always current):
git clone https://github.com/Eleven-M/flowmind.git
cd flowmind && npm install && npm run build
./bin/flowmind.js doctor
From npm (frozen snapshot v2.3.1):
npm install -g flowmind
flowmind doctor
Try it without any provider or MCP configuration:
flowmind demo log-audit
flowmind demo code-review
flowmind skills
Runtime supports Node.js 18 and newer.
One-Step Setup
Initialize FlowMind's AI, resource, component, and skill config from a portable Markdown package:
flowmind config --import config/flowmind-config-package.example.md --dry-run --json
flowmind config --import config/flowmind-config-package.example.md
This creates the local files FlowMind reads at runtime:
~/.flowmind/config.json
~/.flowmind/ai-config.json
~/.flowmind/resource-config.json
~/.flowmind/component-config.json
~/.flowmind/skill-config.json
Use your own package by copying config/flowmind-config-package.example.md and replacing MCP server names, project IDs, namespaces, and provider settings.
Use From Model Tools
Codex
Use the JSON-friendly wrapper:
flowmind-codex skills
flowmind-codex --skill log-audit "query traceId abc123"
flowmind-codex doctor
By default, Codex mode shares learning and resource state with MCP and the regular CLI under ~/.flowmind/.
Set FLOWMIND_SHARED_HOME=/path/to/home to choose the shared parent directory. Set
FLOWMIND_CODEX_HOME=/path/to/state only when an isolated Codex store is required.
Claude
Install FlowMind as a Claude MCP server:
flowmind install claude
Install Claude and initialize FlowMind config in one command:
flowmind install claude \
--flowmind-home /absolute/path/to/flowmind-home \
--flowmind-config config/flowmind-config-package.example.md
Restart Claude after changing MCP configuration.
WorkBuddy
Install FlowMind as a WorkBuddy MCP server:
flowmind install workbuddy
Install WorkBuddy and initialize FlowMind config in one command:
flowmind install workbuddy \
--flowmind-home /absolute/path/to/flowmind-home \
--flowmind-config config/flowmind-config-package.example.md
If WorkBuddy uses a custom MCP config path:
flowmind install workbuddy --config /absolute/path/to/workbuddy-mcp.json
Manual config example: config/workbuddy-mcp-config.example.json.
Common Workflows
| Goal | Command |
|---|---|
| Load local knowledge and inspect learned assets | flowmind learn --assets --json |
| Query logs or trace chains | flowmind process --skill log-audit "query traceId abc123" |
| Review code with fixed rules | flowmind process --skill code-review "review the staged changes" |
| Analyze design and implementation flow locally | flowmind analyze "summarize local design and code flow" --offline |
| Validate data logic | flowmind process --skill data-logic-validation "check order data consistency" |
| Run guarded workflows | flowmind workflow --chain follow-up-chain.json |
FlowMind can run without an AI provider for deterministic local analysis and demos. Real log, database, document, and deployment skills need the matching MCP resources or adapters configured.
Decision Provider Routing
FlowMind 2.3.1 adds explicit decision-provider routing for skill selection. Decision providers such as jev answer typed choice questions and never take over chat or completion calls. They remain dormant until you enable them and provide credentials:
{
"ai": {
"providers": {
"jev": {
"enabled": true,
"apiKey": "${JEV_API_KEY}",
"model": "jev-latest"
}
},
"featureProviders": {
"skillSelection": "jev"
}
}
}
If the decision provider is disabled, fails, or has low confidence, FlowMind falls back to the default LLM provider. See the provider adapter guide.
Automatic Learning
FlowMind stores explicit corrections as local reusable state:
flowmind process --skill log-audit "query traceId abc123"
flowmind "next time use a table"
The next similar request can reuse that formatting preference. Skill choices are learned too:
flowmind process --skill offline-design-analysis "analyze the contract limit validation flow"
Later similar analysis requests prefer the learned route.
Local State
FlowMind reads and writes local state under:
FLOWMIND_HOME/.flowmind
If FLOWMIND_HOME is not set, it uses your user home directory. Files that may contain credentials or workflow state are written with private permissions on POSIX systems.
More
- Full integration guide: docs/integration-guide.md
- Skill catalog: docs/skills-catalog.md
- Provider adapter guide: docs/provider-adapter-guide.md
- Security model: docs/security-model.md
- Release history: CHANGELOG.md
License
MIT. See LICENSE.
FlowMind MCP questions
How do I add FlowMind MCP to Claude Code?
Run claude mcp add flowmind -- npx -y flowmind in your terminal. Add --scope user to make it available in every project.
How do I add FlowMind MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can FlowMind work without an AI provider?
Yes, it can run without an AI provider for deterministic local analysis and demonstrations.