jellycuts
Model Context Protocol (MCP) server for JellyCuts iOS Shortcuts automation. Provides comprehensive API access to Jelly programming language functions, syntax validation, and iOS Shortcuts generation.
claude mcp add --transport stdio chromewillow-jellycuts-mcp-server node server.js \ --env PORT="Port to run the MCP server on" \ --env JELLYCUTS_API_KEY="API key for JellyCuts service (if required)" \ --env JELLYCUTS_BASE_URL="Base URL for JellyCuts API (if required)"
How to use
This MCP server exposes a programmatic interface to JellyCuts functionality, offering access to Jelly language functions, syntax validation, and iOS Shortcuts generation. Clients can query the server to validate Jelly syntax, execute API-like calls to Jelly programs, or generate optimized Shortcuts configurations that wire Jelly functions to iOS Shortcuts actions. Typical usage involves sending requests to the server's endpoints to validate code snippets, list available Jelly functions, or request generated Shortcuts payloads that can be imported into the Shortcuts app.
You can leverage the server’s capabilities to: (1) validate Jelly syntax and provide detailed error messages with location info, (2) call Jelly language functions remotely to transform or evaluate code, and (3) generate iOS Shortcuts configurations that automate common JellyCuts tasks. The exact endpoints may include /validate, /functions, and /generate-shortcuts, each returning structured results that you can consume in your tooling or automation pipelines.
How to install
Prerequisites:
- Node.js (version 14 or later)
- npm (comes with Node.js)
Install steps:
-
Clone the repository: git clone https://github.com/your-org/jellycuts-mcp-server.git cd jellycuts-mcp-server
-
Install dependencies: npm install
-
Configure environment variables:
- Create a .env file or set environment variables: PORT=3000 JELLYCUTS_API_KEY=your_api_key_here JELLYCUTS_BASE_URL=https://api.jellycuts.example
-
Start the server: npm start OR node server.js
-
Verify the server is running by hitting the health endpoint (e.g., http://localhost:3000/health) and ensure responses are as expected.
Additional notes
Environment variables are commonly required for API integrations (JELLYCUTS_API_KEY, JELLYCUTS_BASE_URL). If you run into port conflicts, change PORT in your environment. If the server fails to start due to missing modules, ensure npm install completed successfully and that your Node.js version is supported. For production deployments, consider running behind a process manager (e.g., PM2) and configuring proper TLS termination. If you need to regenerate Shortcuts payloads for different JellyCuts workflows, use the /generate-shortcuts endpoint with the appropriate parameters. Ensure your JellyCuts API key has the necessary permissions for the requested operations.