check_flow_done — NoBrainer Tech Flow MCP Tool Read-only
check_flow_done
(check flow done) is one of 6 tools on the
NoBrainer Tech Flow
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_flow_done from your client
- Claude Code NoBrainer Tech Flow check_flow_done run in your project directory
- Claude Desktop NoBrainer Tech Flow check_flow_done ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NoBrainer Tech Flow check_flow_done ~/.cursor/mcp.json
- VS Code NoBrainer Tech Flow check_flow_done .vscode/mcp.json
- Zed NoBrainer Tech Flow check_flow_done ~/.config/zed/settings.json
- Windsurf NoBrainer Tech Flow check_flow_done ~/.codeium/windsurf/mcp_config.json
- Cline NoBrainer Tech Flow check_flow_done ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NoBrainer Tech Flow check_flow_done ~/.gemini/settings.json
- Grok NoBrainer Tech Flow check_flow_done .mcp.json (in your project root)
- ChatGPT NoBrainer Tech Flow check_flow_done Settings → Connectors → Advanced → Developer mode
- Claude.ai NoBrainer Tech Flow check_flow_done Settings → Connectors → Add custom connector
- LangChain NoBrainer Tech Flow check_flow_done pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http nobrainer-tech-flow https://mcp.nobrainer.tech/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 10 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.