Problem
The Epiq MCP exposes epiq_swimlane_list and lets callers target an existing swimlane through epiq_issue_create and epiq_issue_move, but it exposes no operations to create, rename, reorder, or otherwise manage swimlanes.
This prevents an MCP client from setting up or restructuring a board. For example, an agent can inspect the default Todo / In progress / Done lanes and populate them, but it cannot create workstream lanes requested by the user.
Suggested API
epiq_swimlane_createepiq_swimlane_title_editepiq_swimlane_move or another explicit reorder operationepiq_swimlane_delete or archive, with clear behavior for contained issues
The operations should accept repoRoot consistently with the existing Epiq MCP tools and return the created or updated swimlane.
Why this matters
Board setup currently requires leaving MCP for the TUI or another interface. That makes the MCP surface incomplete for agents asked to create a board structure before populating it.
Problem
The Epiq MCP exposes
epiq_swimlane_listand lets callers target an existing swimlane throughepiq_issue_createandepiq_issue_move, but it exposes no operations to create, rename, reorder, or otherwise manage swimlanes.This prevents an MCP client from setting up or restructuring a board. For example, an agent can inspect the default Todo / In progress / Done lanes and populate them, but it cannot create workstream lanes requested by the user.
Suggested API
epiq_swimlane_createepiq_swimlane_title_editepiq_swimlane_moveor another explicit reorder operationepiq_swimlane_deleteor archive, with clear behavior for contained issuesThe operations should accept
repoRootconsistently with the existing Epiq MCP tools and return the created or updated swimlane.Why this matters
Board setup currently requires leaving MCP for the TUI or another interface. That makes the MCP surface incomplete for agents asked to create a board structure before populating it.