Shortcut MCP server

What the model can do

Shortcut work tracking: search stories with Shortcut's search syntax, read a story with its comments and tasks, epics and iterations with their progress, teams, workflows and members. Can create, update, move and delete stories, comment on stories and epics, add and tick tasks, link stories, create and update epics, and create iterations, labels and docs when you ask.

Reads

• shortcut_membersMembers of the Shortcut workspace: name, mention name (what owner: and the create-story owners take), email, role (owner, admin, member…
• shortcut_workflowsWorkflows and their states in order: state id, name and type (unstarted, started, done) with the number of stories in each.
• shortcut_teamsTeams (Shortcut groups): name, mention name, members, workflows, and counts of backlog, started and total stories and started epics.
• shortcut_projectsProjects, where the workspace still uses them (newer workspaces organise by team and epic instead and get an empty list): name, abbreviation…
• shortcut_epicsEpics with their state, owners, teams, deadline and progress (stories total/done/started, points).
• shortcut_iterationsIterations (sprints) with status (unstarted, started, done), dates, teams and progress stats.
• shortcut_search_storiesSearch stories with Shortcut's search syntax: free words match the title; operators include state:"In Progress", owner:mention_name…
• shortcut_storyOne story by id: description, state, owners, requester, team, epic, iteration, labels, estimate, deadline, comments (with authors), tasks…

Acts, when you ask

These change something in Shortcut. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• shortcut_create_storyCreates a Shortcut story.
• shortcut_update_storyChanges an existing Shortcut story: move it to a workflow state, set its owners, rename it, change its type, estimate, deadline, epic, iteration…
• shortcut_delete_storyPermanently deletes one Shortcut story with its comments and tasks.
• shortcut_comment_storyAdds a comment to a Shortcut story as the connected member, or a threaded reply with reply_to.
• shortcut_edit_story_commentReplaces the text of a comment on a Shortcut story.
• shortcut_delete_story_commentPermanently deletes one comment from a Shortcut story.
• shortcut_add_story_taskAdds a task to a Shortcut story's checklist, optionally with owners (who are notified).
• shortcut_update_story_taskTicks off or reopens a task on a Shortcut story, or changes its text or owners (owners replace the task's whole list).
• shortcut_link_storiesLinks two Shortcut stories: "blocks" (the first blocks the second), "duplicates" (the first duplicates the second) or "relates to".
• shortcut_create_epicCreates a Shortcut epic, requested by the connected member.
• shortcut_update_epicChanges an existing Shortcut epic: rename, new description, move to an epic state, set owners or teams (each replaces the whole list)…
• shortcut_comment_epicAdds a comment to a Shortcut epic as the connected member.
• shortcut_create_iterationCreates a Shortcut iteration (sprint) with a name and start and end dates, optionally for a team (Shortcut takes one).
• shortcut_create_labelCreates a label in the Shortcut workspace, with an optional hex colour and description.
• shortcut_create_docCreates a Shortcut Doc with a title and Markdown content, visible in the workspace's Docs.

Connect it

First connect Shortcut on Dashboard → Connections, then add Memtro to your client once. The Shortcut tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Shortcut connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Which of Priya's stories are still not done?
• › What is left in the current iteration for the platform team?
• › How far along is the Checkout v2 epic, and who owns it?
• › Create a chore for the platform team called 'Rotate the staging certificates' and assign it to Sam
• › Move story 4127 to Ready for Review and comment that the fix is on staging

Questions

Is this an official Shortcut MCP server?

No. It is Memtro's MCP server with Memtro's Shortcut connector behind it: the connector reads Shortcut through its API with the credentials you connect on Dashboard → Connections, and Shortcut publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Shortcut?

Only when you ask, and only what it has been granted: create a story with a type, state, owners, epic and labels; update a story: move it to a state, reassign it, rename, re-estimate, change epic, iteration or labels, or archive it; delete a story permanently; comment on a story, or reply to a comment; edit a story comment; delete a story comment permanently; add a task to a story's checklist; tick off, reopen, edit or reassign a story's task; link two stories (blocks, duplicates, relates to); create an epic; update an epic: rename, change state, owners, teams or dates, or archive it; comment on an epic; create an iteration; create a label; create a Doc. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server