Shortcut MCP

Shortcut's MCP server connects an AI client to a Shortcut workspace so an agent can work with planning objects directly. It can search and read stories, create new ones with the right workflow state, owner, team, and labels, update or move existing stories between states, and navigate the structures around them: epics, iterations, milestones and objectives, workflows, and story comments. The obvious use is closing the gap between planning and code. An assistant can pull the story it is about to implement, read the description and comment thread for context, then create the branch and mark the story in progress without anyone retyping the ticket into the chat. Running the other direction, a conversation or a support thread can end as a properly filed story attached to the correct epic and iteration, with the details preserved instead of summarized away. It is built for software teams already running Shortcut who work through MCP capable clients such as advanced AI code assistants, or IDEs. Connection uses a Shortcut API token, so the agent sees the workspace with the permissions of the account that issued it. Starting read only is a reasonable posture while a team calibrates how much writing they want an assistant doing in their backlog.