Shortcut MCP Server
Provides 73 tools for interacting with Shortcut's project management API, enabling management of stories, epics, iterations, milestones, projects, labels, workflows, members, linked files, and more, with read, write, delete, and archive operations.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Shortcut MCP Serversearch stories with query 'bug' in project 'API'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Shortcut MCP Server
MCP server for connecting Claude, Codex, or any MCP client to the Shortcut project management API. Provides 73 tools covering the full Shortcut API v3 surface.
How it works
This project implements the Model Context Protocol (MCP) — an open standard that lets AI assistants call external tools.
┌──────────────────┐ stdio ┌──────────────────┐ HTTPS ┌──────────────────┐
│ MCP Client │◄──────────────────►│ MCP Server │◄────────────────►│ Shortcut API │
│ (Claude Desktop, │ JSON-RPC over │ (this project) │ REST API v3 │ api.app. │
│ Claude Code, │ stdin/stdout │ │ with API token │ shortcut.com │
│ VS Code, etc.) │ │ src/index.ts │ │ │
└──────────────────┘ └──────────────────┘ └──────────────────┘Server (src/index.ts): Registers 73 tools with the MCP SDK. When a client calls a tool, the server validates the input (via Zod schemas), makes the corresponding REST request to the Shortcut API, and returns the result. All write operations are protected by confirmation guards.
Client (src/client.ts): A standalone test client for development. It spawns the server as a child process, connects over stdio, and lets you call any tool from the command line:
# List available tools
npm run client
# Call a specific tool
npm run client -- list_epics
npm run client -- get_story '{"story_id": 123}'
npm run client -- create_story '{"name": "Test", "project_id": 101, "dry_run": true}'In production, you don't use the test client — your MCP-compatible AI assistant (Claude Desktop, Claude Code, VS Code, etc.) acts as the client and calls tools automatically.
Related MCP server: Shortcut MCP Server
Setup
Install dependencies:
npm installSet your API token:
cp .env.example .env
# then edit .env and set SHORTCUT_API_TOKEN to your Shortcut API tokenOr export directly:
export SHORTCUT_API_TOKEN="<your-token>"You can generate a Shortcut API token at Settings → API Tokens in your Shortcut workspace.
Build:
npm run buildRun
npm startIntegration
Claude Desktop
Add the following to your Claude Desktop config file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
{
"mcpServers": {
"shortcut": {
"command": "node",
"args": ["/absolute/path/to/shortcut-mcp-server/dist/index.js"],
"env": {
"SHORTCUT_API_TOKEN": "<your-shortcut-token>"
}
}
}
}Restart Claude Desktop after saving.
Claude Code (CLI)
Add to ~/.claude/settings.json:
{
"mcpServers": {
"shortcut": {
"command": "node",
"args": ["/absolute/path/to/shortcut-mcp-server/dist/index.js"],
"env": {
"SHORTCUT_API_TOKEN": "<your-shortcut-token>"
}
}
}
}VS Code (Claude Extension)
Add to your project's .vscode/mcp.json or workspace settings:
{
"mcpServers": {
"shortcut": {
"command": "node",
"args": ["/absolute/path/to/shortcut-mcp-server/dist/index.js"],
"env": {
"SHORTCUT_API_TOKEN": "<your-shortcut-token>"
}
}
}
}Note: In all configs above, replace
/absolute/path/to/shortcut-mcp-serverwith the actual path where you cloned this repo, and<your-shortcut-token>with your Shortcut API token.
Guardrails for write tools
All mutating tools support safety guardrails:
confirm="CONFIRM_WRITE"is required to execute any write/update/create.dry_run=truereturns the exact request payload without changing Shortcut data.confirm_archive=trueis required when archiving.confirm_delete=trueis required for delete operations (in addition toconfirm).Read tools do not support
dry_run; passing it returns a validation error.
Recommended flow for writes:
Run with
dry_run=trueand validate the payload.Re-run with
confirm="CONFIRM_WRITE"(andconfirm_archive=true/confirm_delete=trueif applicable).
Tools (73)
# | Tool | Description | Type |
Stories | |||
1 |
| Search stories with Shortcut query syntax | Read |
2 |
| Get a story by ID | Read |
3 |
| Create a story in a project | Write |
4 |
| Update fields on an existing story | Write |
5 |
| Permanently delete a story | Delete |
6 |
| Archive a story | Archive |
7 |
| Move a story to a workflow state by ID or name | Write |
8 |
| Get change history of a story | Read |
9 |
| Update multiple stories at once | Write |
10 |
| Move multiple stories to a different project/state | Write |
11 |
| Permanently delete multiple stories | Delete |
Story Comments | |||
12 |
| List comments for a story | Read |
13 |
| Add a comment to a story | Write |
14 |
| Update a comment on a story | Write |
15 |
| Delete a comment | Delete |
Story Tasks (Checklists) | |||
16 |
| List checklist tasks on a story | Read |
17 |
| Add a checklist task | Write |
18 |
| Update a checklist task (e.g. mark complete) | Write |
19 |
| Delete a checklist task | Delete |
Story Links | |||
20 |
| Link two stories (blocks, relates to, duplicates) | Write |
21 |
| Delete a story link | Delete |
Story Labels | |||
22 |
| Add a label to a story | Write |
23 |
| Remove a label from a story | Write |
Story VCS Integration | |||
24 |
| List Git branches associated with a story | Read |
25 |
| List Git commits associated with a story | Read |
26 |
| List pull requests associated with a story | Read |
27 |
| List external links on a story | Read |
Epics | |||
28 |
| List epics | Read |
29 |
| Get an epic by ID | Read |
30 |
| Create an epic | Write |
31 |
| Update an epic | Write |
32 |
| Permanently delete an epic | Delete |
33 |
| Archive an epic | Archive |
34 |
| Search epics with query syntax | Read |
35 |
| List stories in an epic | Read |
36 |
| Add a label to an epic | Write |
Epic Comments | |||
37 |
| List comments on an epic | Read |
38 |
| Add a comment to an epic | Write |
Iterations (Sprints) | |||
39 |
| List iterations | Read |
40 |
| Get an iteration by ID | Read |
41 |
| Create an iteration | Write |
42 |
| Update an iteration | Write |
43 |
| Permanently delete an iteration | Delete |
44 |
| List stories in an iteration | Read |
Milestones | |||
45 |
| List milestones | Read |
46 |
| Get a milestone by ID | Read |
47 |
| Create a milestone | Write |
48 |
| Update a milestone | Write |
49 |
| Permanently delete a milestone | Delete |
50 |
| List epics in a milestone | Read |
Projects | |||
51 |
| List projects | Read |
52 |
| Get a project by ID | Read |
53 |
| Create a project | Write |
54 |
| Update a project | Write |
55 |
| Permanently delete a project | Delete |
Labels | |||
56 |
| List all labels | Read |
57 |
| Get a label by ID | Read |
58 |
| Create a label | Write |
59 |
| Update a label | Write |
60 |
| Permanently delete a label | Delete |
Workflows | |||
61 |
| List all workflows and their states | Read |
Members & Groups | |||
62 |
| List workspace members | Read |
63 |
| Get a member by UUID | Read |
64 |
| List teams/groups | Read |
65 |
| Get a team/group by UUID | Read |
Linked Files | |||
66 |
| List all linked files | Read |
67 |
| Get a linked file by ID | Read |
68 |
| Create a linked file reference (e.g. Google Doc, Figma) | Write |
69 |
| Update a linked file | Write |
70 |
| Permanently delete a linked file | Delete |
Other | |||
71 |
| List all custom fields and their values | Read |
72 |
| List all story/epic templates | Read |
73 |
| List linked Git repositories | Read |
Type legend: Read = no confirmation needed | Write = requires confirm="CONFIRM_WRITE" | Delete = requires confirm_delete=true + confirm="CONFIRM_WRITE" | Archive = requires confirm_archive=true + confirm="CONFIRM_WRITE"
Example tool calls
Create a story (dry run first)
{
"name": "MCP integration test story",
"project_id": 101,
"story_type": "feature",
"description": "Created from Shortcut MCP server",
"dry_run": true
}Create a story (execute)
{
"name": "MCP integration test story",
"project_id": 101,
"story_type": "feature",
"description": "Created from Shortcut MCP server",
"confirm": "CONFIRM_WRITE"
}Transition a story to a new state
{
"story_id": 12345,
"workflow_state_name": "In Progress",
"workflow_name": "Engineering Workflow",
"confirm": "CONFIRM_WRITE"
}Update an epic
{
"epic_id": 14,
"state": "in progress",
"confirm": "CONFIRM_WRITE"
}Archive a story
{
"story_id": 12345,
"confirm_archive": true,
"confirm": "CONFIRM_WRITE"
}Delete a story (double confirmation)
{
"story_id": 12345,
"confirm_delete": true,
"confirm": "CONFIRM_WRITE"
}Bulk move stories
{
"story_ids": [123, 456, 789],
"project_id": 202,
"workflow_state_id": 500000010,
"confirm": "CONFIRM_WRITE"
}Search stories
{
"query": "owner:johndoe state:\"In Progress\" type:bug"
}Create an iteration
{
"name": "Sprint 42",
"start_date": "2025-03-10",
"end_date": "2025-03-24",
"confirm": "CONFIRM_WRITE"
}Link two stories
{
"subject_id": 123,
"object_id": 456,
"verb": "blocks",
"confirm": "CONFIRM_WRITE"
}Add a comment to a story
{
"story_id": 12345,
"text": "Looks good, moving to review.",
"confirm": "CONFIRM_WRITE"
}Using the test client
The included test client (src/client.ts) lets you test tools from the command line without an AI assistant:
# Build first
npm run build
# List all available tools
npm run client
# Read operations (no confirmation needed)
npm run client -- list_epics
npm run client -- get_story '{"story_id": 123}'
npm run client -- search_stories '{"query": "state:\"In Progress\""}'
npm run client -- list_workflows
# Write operations (need confirmation)
npm run client -- create_story '{"name": "Test", "project_id": 101, "dry_run": true}'
npm run client -- create_story '{"name": "Test", "project_id": 101, "confirm": "CONFIRM_WRITE"}'Project structure
shortcut-mcp-server/
├── src/
│ ├── index.ts # MCP server — all 73 tool registrations and Shortcut API logic
│ └── client.ts # Standalone test client for development
├── dist/ # Compiled JavaScript (generated by npm run build)
├── package.json
├── tsconfig.json
├── .env.example # Template for API token
└── .gitignoreLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ptamb3/shortcut-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server