step_reorder — Pipefork Management MCP MCP Tool
step_reorder
(step reorder) is one of 27 tools on the
Pipefork Management MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call step_reorder from your client
- Claude Code Pipefork Management MCP step_reorder run in your project directory
- Claude Desktop Pipefork Management MCP step_reorder ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Pipefork Management MCP step_reorder ~/.cursor/mcp.json
- VS Code Pipefork Management MCP step_reorder .vscode/mcp.json
- Zed Pipefork Management MCP step_reorder ~/.config/zed/settings.json
- Windsurf Pipefork Management MCP step_reorder ~/.codeium/windsurf/mcp_config.json
- Cline Pipefork Management MCP step_reorder ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Pipefork Management MCP step_reorder ~/.gemini/settings.json
- Grok Pipefork Management MCP step_reorder .mcp.json (in your project root)
- ChatGPT Pipefork Management MCP step_reorder Settings → Connectors → Advanced → Developer mode
- Claude.ai Pipefork Management MCP step_reorder Settings → Connectors → Add custom connector
- LangChain Pipefork Management MCP step_reorder pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http management https://www.pipefork.com/mcp
Other tools on this server
- api_list
- api_get
- api_create
- draft_get
- draft_validate
- endpoint_create
- endpoint_update
- endpoint_delete
- step_create
- step_update
- step_delete
- secret_list
- secret_create
- secret_rotate
- secret_deactivate
- connection_list
- connection_get
- connection_create
- connection_update
- deployment_list
- deployment_get_state
- deployment_deploy
- deployment_promote
- deployment_rollback
- deployment_undeploy
- deployment_history
This list was read from the server itself, by connecting to it and calling tools/list on 17 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.