detect_workflows — Unseen Workflow Compiler MCP Tool
detect_workflows
(detect workflows) is one of 9 tools on the
Unseen Workflow Compiler
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call detect_workflows from your client
- Claude Code Unseen Workflow Compiler detect_workflows run in your project directory
- Claude Desktop Unseen Workflow Compiler detect_workflows ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Unseen Workflow Compiler detect_workflows ~/.cursor/mcp.json
- VS Code Unseen Workflow Compiler detect_workflows .vscode/mcp.json
- Zed Unseen Workflow Compiler detect_workflows ~/.config/zed/settings.json
- Windsurf Unseen Workflow Compiler detect_workflows ~/.codeium/windsurf/mcp_config.json
- Cline Unseen Workflow Compiler detect_workflows ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Unseen Workflow Compiler detect_workflows ~/.gemini/settings.json
- Grok Unseen Workflow Compiler detect_workflows .mcp.json (in your project root)
- ChatGPT Unseen Workflow Compiler detect_workflows Settings → Connectors → Advanced → Developer mode
- Claude.ai Unseen Workflow Compiler detect_workflows Settings → Connectors → Add custom connector
- LangChain Unseen Workflow Compiler detect_workflows pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http unseen-workflow-compiler https://unseendocs.in/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 22 October 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.