mcp s

This MCP server package provides a ready-to-run server for the Shortcut MCP workflow. After building the monorepo, the shortcut-mcp-server package exposes an MCP server you can run to accept requests from clients like the Shortcut app and other MCP clients. The included CLI and server tooling are designed to streamline the installation and provisioning of the Shortcut MCP server within your environment. Once running, clients can connect to the MCP server to request installation scripts, manage configurations, and orchestrate the Shortcut integration workflow through the server's endpoints exposed by the dist/index.js entry point.

Prerequisites:

• Your environment should have a modern Node.js toolchain or Bun installed. This project uses Bun for builds and running packages.
• Access to the repository (or a published version of the packages).

Install and set up locally:

1. Install Bun (if not already installed).

curl -fsSL https://bun.sh/install | bash
export BUN_INSTALL="$HOME/.bun"
export PATH="$BUN_INSTALL/bin:$PATH"

2. Install dependencies for the monorepo:

bun install

3. Build all packages (this will create dist folders for the server you want to run):

bun run build

4. Run the Shortcut MCP server (example path to the built server):

bun run packages/shortcut-mcp-server/dist/index.js

Alternatively, if you publish the server package, you can install and run it directly via your package manager:

npm i @madisonbullard/shortcut-mcp-server
node node_modules/@madisonbullard/shortcut-mcp-server/dist/index.js

Tips:

• The server is built per-package; ensure you’ve built the desired server (e.g., shortcut-mcp-server) before attempting to run the dist/index.js entry.
• If you modify code, run bun run build to refresh the dist folder.
• The CLI for installers and the TUI help manage installation of MCP servers for various clients; use the TUI to discover and install additional servers included in this monorepo.
• For CI or production, consider publishing the server package and running it via your preferred process manager (pm2, systemd, etc.).
• If you encounter path issues, verify that the dist/index.js path matches your installed package structure after the build step.