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