Skip to content
Custom Connectors

Full read-write Claude connector for Shortcut

Let Claude create stories and move them across workflow states in Shortcut

Stop tab-switching to triage the backlog by hand. Claude creates stories with the right team, epic, and estimate, moves them across workflow states, assigns owners, and comments, all where your team's work already lives, with you approving the changes.

Shortcut is a project management tool built for software teams, organizing work into stories, epics, iterations, and workflow states. People want Claude to do more than read the backlog: to create stories, move them across states, comment, and keep iterations moving without leaving the conversation.

What is a Shortcut MCP server?

A Shortcut MCP server is a small hosted service that exposes Shortcut's data and actions to Claude over the Model Context Protocol, so Claude can tasks, projects, and docs inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can Shortcut's current connector do today?

Shortcut ships an official MCP server, so Claude can connect today and work with stories out of the box. That native connector exposes a fixed, standard tool set, the same generic slice for everyone, rather than the actions, scoping, and review your team runs on. A custom connector builds on the API to deliver the full create, update, assign, comment, and grouping workflow, shaped to how you work and gated by your confirmation.

What does full read-write Shortcut access unlock?

Full read-write Shortcut access lets Claude create stories with the right team, epic, labels, and estimate, move them across workflow states, assign owners, comment on threads, and link related work into epics or iterations. The triage and status updates that used to mean tab-switching happen where your team's work already lives, with you approving the changes.

  • Create a new story with team, epic, labels, and estimate set
  • Move a story across workflow states as work progresses
  • Assign or reassign a story owner to a team member
  • Add a comment to a story to capture context or decisions
  • Add a story to an epic or iteration to group related work
  • Search stories by query and propose batched status updates

Can Claude create and update stories in Shortcut?

Yes. Shortcut ships an official MCP server with a standard tool set, but a custom connector delivers the full capability, setting the team, epic, labels, and estimate, then moving each story across workflow states as work progresses. It is shaped to your workflow, so create and update flow once you approve.

Can Claude assign owners and comment on stories in Shortcut?

Claude can assign or reassign a story owner to a team member and add comments that capture context or decisions on a thread. Reassigning owners is gated behind your confirmation, so Claude prepares the change and shows you exactly what it will do before anything commits to Shortcut.

Can Claude batch status updates across Shortcut stories?

Claude can search stories by query and propose batched status updates, grouping related work into epics or iterations. Bulk status changes wait for your approval before they run, and the connector inherits the API token's existing permissions, so it never gets more access to Shortcut than your own account already has.

How a Shortcut connector works

We build a small MCP server that authenticates to Shortcut with a scoped API token and asks for only the access the work needs. Read tools (search, read story) and write tools (create, update state, assign, comment) are separated, and actions like reassigning or bulk updates require your confirmation. If your Shortcut instance sits behind network controls, we can run the server inside an IP allowlist. Claude only ever has the access the token's own account already has.

Frequently asked questions

Can Claude create and update stories in Shortcut, not just read them?
Yes. Shortcut's official MCP server gives Claude a standard set of story tools, but it is a fixed, generic slice. A custom connector exposes the full write surface, so Claude can create a story with the right team, epic, labels, and estimate, then move it across workflow states, shaped to your workflow and gated by your confirmation.
Will Claude change Shortcut stories without my approval?
No. Write actions are separated from read actions, and steps like reassigning owners or applying bulk status updates are gated behind your confirmation. Claude can prepare the change and show you exactly what it will do, but it only commits once you approve. You decide which actions run automatically.
Does the Shortcut connector get more access than I have?
No. The connector authenticates with a scoped Shortcut API token and inherits that account's existing permissions and team memberships. It never grants Claude more access to your Shortcut workspace than the token's own account already has, and it respects the same boundaries that account does.

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.