auto_route_next_step — agent workflow engine MCP Tool
auto_route_next_step
(auto route next step) is one of 5 tools on the
agent workflow engine
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call auto_route_next_step from your client
- Claude Code agent workflow engine auto_route_next_step run in your project directory
- Claude Desktop agent workflow engine auto_route_next_step ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor agent workflow engine auto_route_next_step ~/.cursor/mcp.json
- VS Code agent workflow engine auto_route_next_step .vscode/mcp.json
- Zed agent workflow engine auto_route_next_step ~/.config/zed/settings.json
- Windsurf agent workflow engine auto_route_next_step ~/.codeium/windsurf/mcp_config.json
- Cline agent workflow engine auto_route_next_step ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI agent workflow engine auto_route_next_step ~/.gemini/settings.json
- Grok agent workflow engine auto_route_next_step .mcp.json (in your project root)
- ChatGPT agent workflow engine auto_route_next_step Settings → Connectors → Advanced → Developer mode
- Claude.ai agent workflow engine auto_route_next_step Settings → Connectors → Add custom connector
- LangChain agent workflow engine auto_route_next_step pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-workflow-engine https://api.lazy-mac.com/agent-workflow-engine/mcpOther tools on this server
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.