Kiwi for Shortcut
Have the agent on a Kiwi step read its Shortcut story, update its Sub-tasks and comment its result, through Shortcut's MCP server.
- Your agent works in Shortcut through its own connection. Kiwi does not call Shortcut and never holds its credentials.
- A workflow skill can list Shortcut among the tools it requires. When you supply your agent's available tools to a skill check and Shortcut is not among them, the check reports
SK15-UNSUPPORTED-TOOL. - A project Admin can add links to Shortcut, with notes, under Connections and bind them to the steps that use them. The agent reads them with
list_connections. - The agent can report the tools and plugins it ran with, including its Shortcut connection, with
report_configuration. - The agent submits links to its work in Shortcut as the step's outputs. People review them, and sign-off stays with the people your workflow names.
What your agent can do in Shortcut
- Read, create and update Stories, including their comments and Sub-tasks.
- Create and read Epics and Iterations to group related work.
- Read, create and update Docs, for example to record a design note.
- Look up Teams, Members, Workflows and Objectives, which the server exposes read-only.
Set up
Connect your agent to Kiwi
Add Kiwi's hosted MCP server,
https://kiwiflow.io/mcp, to your coding agent.Connect your agent to Shortcut
Add the Shortcut MCP server to your agent with this URL. The credentials stay with your agent.
https://mcp.shortcut.com/mcpExample skill
Publish instructions like these as a workflow skill that lists Shortcut among its required tools.
Read the Shortcut story ID from the run's inputs and fetch the story. Work through its Sub-tasks and update each one as you finish it. Add a comment to the story that links the pull request. Submit the story URL and the pull request link as the step's outputs. Moving the story to Done stays with the story's owner. If the story cannot be read, call report_blocker with the story ID.