Shortcut▌
by useshortcut
Automate sprint planning and task management with Shortcut—supports story management, epics, teams, and more for agile d
Integrates with Shortcut's project management platform to provide story management, epic and iteration operations, team workflows, objective tracking, and comprehensive search capabilities for development teams automating sprint planning and task management.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Development teams using Shortcut for project management
- / Engineering managers automating sprint planning
- / Teams wanting to integrate Shortcut data into development workflows
capabilities
- / Manage stories and epics in Shortcut
- / Track iterations and sprint planning
- / Search across projects and tasks
- / Monitor team objectives and workflows
- / Automate sprint planning tasks
- / Access project management data via OAuth
what it does
Provides integration with Shortcut project management platform for managing stories, epics, iterations, and team workflows. Offers hosted remote connection with OAuth authentication for zero-setup use.
about
Shortcut is an official MCP server published by useshortcut that provides AI assistants with tools and capabilities via the Model Context Protocol. Automate sprint planning and task management with Shortcut—supports story management, epics, teams, and more for agile d It is categorized under productivity.
how to install
You can install Shortcut in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
Shortcut is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
@shortcut/mcp
<img height="125" src="https://github.com/user-attachments/assets/7c3d3b8e-6252-4790-81cd-6640cd46a2d6" alt="Shortcut's logo" align="right">MCP Server for Shortcut users.
Links: Local Installations | Server Developers
Usage
Cursor
The fastest way to get started is to connect to Shortcut's hosted MCP server. No API token or local setup required — authentication is handled via OAuth.
- Open (or create) the
mcp.jsonfile (it should be in~/.cursor/mcp.jsonor<project-root>/.cursor/mcp.json, but see Cursor docs for more details). - Add the following details and save the file:
{
"mcpServers": {
"shortcut": {
"url": "https://mcp.shortcut.com/mcp"
}
}
}
- Restart Cursor. You will be prompted to authorize with your Shortcut account on first use.
VS Code
If all you need need the configuration for the mcp.json file use this. You will be prompted to authorize with your Shortcut account on first use.
{
"servers": {
"github-mcp": {
"type": "http",
"url": "https://mcp.shortcut.com/mcp"
}
}
}
For more detail on installing MCP services in VSCode see the official VS Code MCP docs for more information.
Claude Desktop
Download the package from this repo
Then, either double-click the icon to install or drag the package onto the client window. It should trigger the installation.
Other IDEs / Running Locally
If your IDE doesn't support HTTP-based MCP servers, or you'd prefer to run the server locally, see the Local Server Setup guide. This covers setup for Windsurf, Zed, Claude Code, and any IDE that supports stdio-based MCP servers.
Available Tools
Stories
| Tool | Description |
|---|---|
stories-get-by-id | Get a single Shortcut story by ID |
stories-get-history | Get the change history for a story |
stories-search | Find Shortcut stories with filtering and search options |
stories-get-branch-name | Get the recommended branch name (based on workspace settings) for a specific story |
stories-create | Create a new Shortcut story |
stories-update | Update an existing Shortcut story |
stories-upload-file | Upload a file and link it to a story |
stories-assign-current-user | Assign the current user as the owner of a story |
stories-unassign-current-user | Unassign the current user as the owner of a story |
stories-create-comment | Create a comment on a story |
stories-create-subtask | Add a new sub-task to a story |
stories-add-subtask | Add an existing story as a sub-task |
stories-remove-subtask | Remove a sub-task from a story |
stories-add-task | Add a task to a story |
stories-update-task | Update a task in a story |
stories-add-relation | Add a story relationship (relates to, blocks, duplicates, etc.) |
stories-add-external-link | Add an external link to a Shortcut story |
stories-remove-external-link | Remove an external link from a Shortcut story |
stories-set-external-links | Replace all external links on a story with a new set of links |
stories-get-by-external-link | Find all stories that contain a specific external link |
Labels
| Tool | Description |
|---|---|
labels-list | List all labels in the Shortcut workspace |
labels-get-stories | Get all stories with a specific label |
labels-create | Create a new label in Shortcut |
Custom Fields
| Tool | Description |
|---|---|
custom-fields-list | List all custom fields in the workspace with their possible values |
Epics
| Tool | Description |
|---|---|
epics-get-by-id | Get a Shortcut epic by ID |
epics-search | Find Shortcut epics with filtering and search options |
epics-create | Create a new Shortcut epic |
epics-update | Update an existing Shortcut epic |
epics-delete | Delete a Shortcut epic |
Iterations
| Tool | Description |
|---|---|
iterations-get-stories | Get stories in a specific iteration by iteration ID |
iterations-get-by-id | Get a Shortcut iteration by ID |
iterations-search | Find Shortcut iterations with filtering and search options |
iterations-create | Create a new Shortcut iteration with start/end dates |
iterations-update | Update an existing Shortcut iteration |
iterations-delete | Delete a Shortcut iteration |
iterations-get-active | Get active iterations for the current user based on team memberships |
iterations-get-upcoming | Get upcoming iterations for the current user based on team memberships |
Objectives
| Tool | Description |
|---|---|
objectives-get-by-id | Get a Shortcut objective by ID |
objectives-search | Find Shortcut objectives with filtering and search options |
Teams
| Tool | Description |
|---|---|
teams-get-by-id | Get a Shortcut team by ID |
teams-list | List all Shortcut teams |
Projects
| Tool | Description |
|---|---|
projects-list | List all projects in the Shortcut workspace |
projects-get-by-id | Get a Shortcut project by public ID |
projects-get-stories | Get all stories in a specific project |
Workflows
| Tool | Description |
|---|---|
workflows-get-default | Get the default workflow for a specific team or the workspace default |
workflows-get-by-id | Get a Shortcut workflow by ID |
workflows-list | List all Shortcut workflows |
Users
| Tool | Description |
|---|---|
users-get-current | Get the current user information |
users-get-current-teams | Get a list of teams where the current user is a member |
users-list | Get all workspace users |
Documents
| Tool | Description |
|---|---|
documents-create | Create a new document in Shortcut with Markdown content |
documents-update | Update content of an existing document by its ID |
documents-list | List all documents in Shortcut |
documents-search | Search for documents |
documents-get-by-id | Retrieve a specific document in markdown format by its ID |
Limit tools
You can limit the tools available to the LLM by setting the SHORTCUT_TOOLS environment variable to a comma-separated list.
- Tools can be limited by entity type by just adding the entity, eg
storiesorepics. - Individual tools can also be limitied by their full name, eg
stories-get-by-idorepics-search.
By default, all tools are enabled.
Example (when running locally):
{
"mcpServers": {
"shortcut": {
"command": "npx",
"args": [
"-y",
"@shortcut/mcp@latest"
],
"env": {
"SHORTCUT_API_TOKEN": "<YOUR_SHORTCUT_API_TOKEN>",
"SHORTCUT_TOOLS": "stories,epics,iterations-create"
}
}
}
}
The following values are accepted in addition to the full tool names listed above under Available Tools:
usersstoriesepicsiterationslabelscustom-fieldsobjectivesteamsprojectsworkflowsdocuments
Read-only mode
You can run the MCP server in read-only mode by setting the SHORTCUT_READONLY environment variable to true. This will disable all tools that modify data in Shortcut.
Example (when running locally):
{
"mcpServers": {
"shortcut": {
"command": "npx",
"args": [
"-y",
"@shortcut/mcp@latest"
],
"env": {
"SHORTCUT_API_TOKEN": "<YOUR_SHORTCUT_API_TOKEN>",
"SHORTCUT_READONLY": "true"
}
}
}
}
Issues and Troubleshooting
Before doing anything else, please make sure you are running the latest version!
If you run into problems using this MCP server, you have a couple of options:
FAQ
- What is the Shortcut MCP server?
- Shortcut is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Shortcut?
- This profile displays 67 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.5★★★★★67 reviews- ★★★★★Ganesh Mohane· Dec 28, 2024
I recommend Shortcut for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Anika Li· Dec 12, 2024
According to our notes, Shortcut benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Isabella Abbas· Dec 12, 2024
Shortcut is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Isabella Anderson· Dec 12, 2024
Shortcut has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Daniel Ndlovu· Dec 12, 2024
Shortcut reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Sakshi Patil· Nov 19, 2024
According to our notes, Shortcut benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Isabella Jackson· Nov 3, 2024
I recommend Shortcut for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Isabella Thomas· Nov 3, 2024
We wired Shortcut into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Anika Gill· Nov 3, 2024
Shortcut reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Anika Ghosh· Nov 3, 2024
Shortcut has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 67