mcp -shortcut

This MCP server exposes Shortcut (Shortcut.com) tools via the MCP protocol. It consolidates access to a wide range of Shortcut data operations—such as creating and updating stories, fetching epics, managing iterations, labels, projects, teams, users, and documents—so your MCP-enabled client can interact with Shortcut without embedding API calls directly. The server is designed to be run locally or in a development environment and can be restricted to a subset of tools using the SHORTCUT_TOOLS environment variable.

To use it, run the server with the provided MCP configuration (for example via npx). Once running, connect your MCP client or editor (e.g., VS Code MCP integration, or your IDE’s MCP feature) to the Shortcut MCP endpoint. You’ll be able to enumerate available tools, invoke them with appropriate parameters, and receive structured responses that you can feed into your workflow automation or LLM prompts. Remember to supply your Shortcut API token if you want to operate on real data; for read-only experimentation you can omit it where permitted by permissions.

Prerequisites

• Node.js (latest LTS) and npm installed on your system
• Internet access to fetch the MCP package

Installation steps

1. Ensure Node.js and npm are installed. Verify with: node -v npm -v

2. Install and run the Shortcut MCP server via npx (as shown in the README): npx -y @shortcut/mcp@latest

3. Configure environment variables if you want to authorize with Shortcut or limit tools. Example: SHORTCUT_API_TOKEN=your_token_here SHORTCUT_TOOLS=stories,epics,iterations,projects

4. Save the configuration (mcp.json or equivalent per your environment) and start the MCP server. Consult the project docs for any project-specific startup flags or daemon setups.

Tips and notes:

• You can tailor the available tools using SHORTCUT_TOOLS to restrict what the MCP server exposes to clients.
• If you’re running locally, you may need to grant your app permissions in Shortcut to access the chosen tools.
• The README example uses npx to fetch @shortcut/mcp@latest; you can pin to a specific version if needed (e.g., @shortcut/mcp@1.2.3).
• For environments behind proxies, ensure npm/yarn proxy settings allow fetching the MCP package.
• When testing, start with a small subset of tools to confirm authorization and data retrieval before enabling the full suite.
• If you encounter token issues, regenerate your Shortcut API token and update SHORTCUT_API_TOKEN accordingly.