-
Notifications
You must be signed in to change notification settings - Fork 41
Open
Description
Summary
The MCP server supports epics-get-by-id, epics-search, and epics-create, but there is currently no way to update an existing epic.
Problem
Agents can create and read epics, but cannot perform common follow-up actions like:
- rename an epic
- update description
- change owner(s)
- change state (e.g. unstarted/started/done)
- set or clear deadline/team/objective fields (as supported by Shortcut API)
This causes workflows to fail when an agent needs to "update epic" after discovery/planning.
Repro
- Configure MCP server with write access (not
SHORTCUT_READONLY, write-capable API token). - Ask agent to update an existing epic.
- Agent cannot find a write tool for epics other than
epics-create.
Expected
A write tool exists for modifying existing epics, e.g.:
epics-update
with behavior similar to stories-update:
- requires
epicPublicId - accepts only fields to change
- supports nullable/unset where relevant
Notes
As of 2026-02-10, @shortcut/mcp latest on npm is 0.19.0, and this gap appears to be feature coverage rather than an outdated local install.
Thanks for considering this — happy to test if/when implemented.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels