shortcut-mcp
Allows AI agents to manage stories, epics, objectives, and teams in Shortcut (formerly Clubhouse) with advanced search, creation, and listing capabilities.
Click on "Deploy 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 show my open stories"
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
A Model Context Protocol (MCP) server for interacting with Shortcut (formerly Clubhouse) directly from Claude.
Acknowledgments
This project is based on the original work by Antonio Lorusso. Mark Madsen's fork extends the original implementation with additional features including advanced search capabilities, improved CLI tools, and enhanced user experience.
Related MCP server: JIRA MCP Tools
Features
View stories, epics, objectives, and teams
Search through stories with advanced filtering options
Create new stories, epics, and objectives
Safe operations only (no updates or deletions)
Archived stories management (excluded by default, with option to include)
What's New in 0.2.3
Project Deprecation: Updated to use teams instead of projects, as projects have been deprecated by Shortcut
Improved ID Handling: Better support for both numeric IDs and UUID strings for teams and epics
Enhanced Team Support: Improved team assignment when creating and updating stories
What's New in 0.2.2
Enhanced Search Functionality: Improved search capabilities with support for Shortcut's native query syntax
Advanced Query Operators: Support for operators like
type:,state:,owner:,label:, and moreBetter Error Handling: More detailed error messages and improved fallback mechanisms
Robust Story ID Handling: Better handling of non-numeric characters in story IDs
What's New in 0.2.1
Team Management: Added support for assigning teams to stories using
team_idandteam_nameparametersNew Tool: Use the
list-teamstool to see all available teams in your Shortcut workspaceImproved Reliability: Better handling of parameters and error conditions
Enhanced Epic Support: Improved support for linking stories to epics
Installation
Standard Installation
pip install shortcut-mcpMacOS Installation with Homebrew and pipx
For MacOS users, we recommend using Homebrew and pipx for a cleaner installation:
# Install pipx if you don't have it already
brew install pipx
pipx ensurepath
# Install shortcut-mcp
pipx install shortcut-mcpThis method installs shortcut-mcp in an isolated environment, preventing dependency conflicts with other Python packages.
Upgrading
To upgrade to the latest version:
# Standard upgrade
pip install --upgrade shortcut-mcp
# If installed with pipx
pipx upgrade shortcut-mcpQuick Start
1. Set up with Claude Desktop
# Install and set up in one step
shortcut-mcp setupYou'll be prompted for your Shortcut API token, which you can find in your Shortcut settings.
Security Note: Your API token grants access to your Shortcut account. Never share it publicly or commit it to version control. The
.envfile is included in.gitignoreto help prevent accidental exposure.
2. Using in Claude
After setup, you can now use the Shortcut tools directly in Claude Desktop. Try these commands:
list-workflows- See all workflow stateslist-my-stories- View stories assigned to youlist-stories-by-state-name- View stories in a specific stateadvanced-search-stories- Find stories with multiple filterslist-teams- View all teams in your Shortcut workspacesearch-stories- Find stories by keywordslist-archived-stories- View archived storieslist-my-archived-stories- View your archived stories
Note: Projects have been deprecated by Shortcut. The
list-projectstool will now inform you to use teams instead. When creating or updating stories, please useteam_idorteam_nameparameters instead of project-related parameters.
Manual Usage
If you want to run the server manually:
# Set your API token
export SHORTCUT_API_TOKEN=your_token_here
# Start the server
shortcut-mcp startDevelopment Setup
Clone the repository:
git clone https://github.com/idyll/shortcut-mcp.git
cd shortcut-mcpInstall Python with asdf:
asdf installCreate virtual environment and install dependencies:
uv venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
uv pip install -e . # Install package in editable modeSet up your environment:
cp .env.example .env
# Edit .env and add your Shortcut API tokenRun the server:
python -m shortcut_mcpProject Structure
shortcut-mcp/
├── src/
│ └── shortcut_mcp/ # Main package directory
│ ├── __init__.py # Package initialization
│ ├── __main__.py # Entry point
│ ├── cli.py # CLI implementation
│ └── server.py # Server implementation
├── pyproject.toml # Project configuration
├── .tool-versions # ASDF version configuration
└── README.mdUsing with Claude Desktop
The shortcut-mcp setup command will automatically configure Claude Desktop for you. If you want to do it manually, add this to your Claude Desktop config:
On MacOS (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"shortcut": {
"command": "shortcut-mcp",
"args": ["start"],
"env": {
"SHORTCUT_API_TOKEN": "your_token_here"
}
}
}
}On Windows (%AppData%\Claude\claude_desktop_config.json):
{
"mcpServers": {
"shortcut": {
"command": "shortcut-mcp",
"args": ["start"],
"env": {
"SHORTCUT_API_TOKEN": "your_token_here"
}
}
}
}Testing
You can test the server using the MCP Inspector:
npx @modelcontextprotocol/inspector shortcut-mcp startSafety Features
This server implements read-only operations with safe creation capabilities:
Only allows GET (read) and POST (create) operations
No modification or deletion of existing data
All operations are attributed to the API token owner
Development
Python Version Management
This project uses asdf for Python version management. The required Python version is specified in .tool-versions.
# Install Python with asdf
asdf install python
# The correct version will be automatically selected based on .tool-versionsCode Quality
We use pylint for code quality checks. Run it with:
pylint src/shortcut_mcpBuilding and Publishing
Once your code is ready:
# Install build tools
pip install build twine
# Build the package
python -m build
# Upload to PyPI
python -m twine upload dist/*Advanced Search Features
The Shortcut MCP server provides powerful search capabilities through the advanced-search-stories tool:
Search Parameters
Owner vs. Requestor: Distinguish between the person assigned to a story (owner) and the person who requested it
Workflow State: Filter by specific workflow states like "In Development" or "Ready for Review"
Time-based Filtering: Find stories based on when they were created or updated
created_after/created_before: Filter by creation dateupdated_after/updated_before: Filter by last update date
Archived Stories: All search tools exclude archived stories by default
Use
include_archived: trueparameter to include archived storiesDedicated tools for working with archived stories:
list-archived-storiesandlist-my-archived-stories
Example Queries
In Claude, you can use commands like:
"Find stories requested by John but owned by Sarah"
"Show me stories in the Ready for Review state created in the last month"
"Search for stories updated after 2023-01-01 in the In Development state"
"List archived stories in the Done state"
"Show my archived stories from the last quarter"
This makes it easy to find exactly the stories you're looking for, even in large projects with many tickets.
Available Tools
18 toolscreate-epicC
Create a new epic in Shortcut
Inputs: name (required), description (required), milestone_id.
create-objectiveB
Create a new objective in Shortcut
Inputs: name (required), description (required), status (required).
create-storyB
Create a new story in Shortcut
Inputs: name (required), description (required), story_type (required), team_id, +4 more.
get-storyA
Get detailed information about a specific story by ID (fastest way to look up a story)
Inputs: story_id (required).
health-checkA
Check the health and connectivity of the Shortcut MCP server
Inputs: no named parameters.
list-archived-storiesC
List only archived stories
Inputs: owner_name, state_name.
list-epicsC
List epics in Shortcut
Inputs: status.
list-my-archived-storiesB
List only archived stories assigned to you
Inputs: state_name.
list-my-storiesC
List stories assigned to you
Inputs: state, include_archived.
list-objectivesC
List objectives in Shortcut
Inputs: status.
list-projectsA
[DEPRECATED] List all projects in Shortcut. Projects have been deprecated by Shortcut, please use teams instead.
Inputs: no named parameters.
list-stories-by-state-nameC
List stories by workflow state name
Inputs: state_name (required), owner_name, include_archived.
list-stories-by-statusC
List stories by workflow state ID
Inputs: workflow_state_id (required), owner_name, include_archived.
list-teamsA
List all teams in Shortcut
Inputs: no named parameters.
list-workflowsB
List all workflows and their states
Inputs: no named parameters.
search-storiesB
Search for stories in Shortcut using powerful search operators
Inputs: query, owner_name, requestor_name, state_name, +2 more.
update-storyC
Update an existing story in Shortcut
Inputs: story_id (required), name, description, story_type, +5 more.
update-story-statusC
Update a story's status in Shortcut
Inputs: story_id (required), status (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 18 tools
All tools have clearly distinct purposes. Create tools target different resources, and list tools are well-differentiated by filters (archived, assigned to me, by state, etc.). No two tools appear to do the same thing.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create-epic, list-stories-by-state-name). Even the deprecated tool uses the same pattern, ensuring predictable naming.
With 18 tools, the server covers the core Shortcut entities (epics, objectives, stories, workflows, teams) without being overwhelming. Each tool earns its place for standard project management operations.
The tool set lacks update operations for epics and objectives, and there are no delete capabilities for any resource. This leaves significant gaps in CRUD coverage, forcing agents to work around missing lifecycle support.
Maintenance
Related MCP Connectors
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Official Fibery MCP server: query and update your workspace from any AI client via OAuth.
MCP server for generating rough-draft project plans from natural-language prompts.
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceA Model Context Protocol server that enables interaction with Shortcut (formerly Clubhouse) project management tool, allowing users to view and search projects, stories, epics, and objectives, as well as create new items through natural language.5-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables interaction with JIRA APIs through Claude Desktop, allowing users to search, create, update, and manage JIRA issues using natural language commands.1-
- FlicenseNot gradedqualityDmaintenanceAn implementation of a Model Context Protocol server that allows Claude and other AI assistants to interact with Shortcut.com's ticket management system for searching, viewing, creating, and updating stories.-

Shortcut MCP Serverofficial
AlicenseBqualityFmaintenanceA Model Context Protocol (MCP) server that integrates Shortcut project management with AI tools like Cursor, Windsurf, and Claude Code, allowing direct access to Shortcut data via API token.569,994 npm96MIT