plaiiin-hq/plaiiin-workflows
Work with plaiiin Workflows tickets through the Mac app or a Workflows server.
Use when working with plaiiin Workflows tickets in a repository checked out on THIS Mac, through the Workflows app's local MCP server (tools named mcp__workflows__* or mcp__plugin_plaiiin-workflows_workflows__*) — listing and reading tickets, creating one, moving it between states, patching fields, commenting, editing a type's fields, or syncing a signed workspace. Covers that the app must be running, that every tool takes the tracking folder as workflow_root, which tools change the repository and which only move the app's selection, and why ticket files are never edited by hand in a signed workspace. With no checkout or no app — only a server URL and a key — use workflows-server instead.
Use when working with tickets on a plaiiin Workflows SERVER over its REST API — listing what is open, reading a ticket and its history, creating one, moving it to another state, commenting, or reading the progress and board views — from any machine, with no checkout of the repository. Covers X-API-Key auth and where the key lives (~/.plaiiin/workflows/env — read that before asking anyone for one), the /api boundary, the version number every write carries, and why a 404 on a workspace usually means "no access" rather than "no such thing". For a repository checked out on this Mac with the Workflows app running, use workflows-app instead.