Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Shortcut to Claude Code

Let Claude create stories and move them across workflow states in Shortcut. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Shortcut to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Shortcut, you add a Shortcut MCP server: a small hosted service that exposes Shortcut's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Shortcut account. No API keys pasted into config files.

claude mcp add --transport http shortcut https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Shortcut once connected?

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

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Shortcut access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Shortcut API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Shortcut changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Shortcut connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Shortcut connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Shortcut account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Shortcut's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Shortcut?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Shortcut account it signs in with. Revoking access is one click in Shortcut.

More on the Shortcut connector

Shortcut connector for claude.aiTodoist + Claude CodeTeamwork + Claude CodeProductboard + Claude Code

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.

Build my connectorTalk to us