workhorse-ai-mcp 0.7.2

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Planado
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,65 @@
+# workhorse-ai-mcp
+
+A delegation journal for orchestrator/worker AI workflows: an append-only
+event log over SQLite (tasks, reports, artifacts, incidents, full-text
+search) exposed as an MCP server. Zero dependencies — only Node.js >= 22.5
+with the built-in `node:sqlite`.
+
+The journal enforces a simple discipline: `DRAFT → DELEGATED → REPORTED →
+ACCEPTED | REWORK | FAILED`, where *reported* (the worker thinks it is done)
+is never the same as *accepted* (the orchestrator verified it).
+
+## Install
+
+The npm package is not published yet — the final name is pending a rebrand.
+Once published, add the server to your `.mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "workhorse": {
+      "command": "npx",
+      "args": ["-y", "workhorse-ai-mcp"]
+    }
+  }
+}
+```
+
+Until then, run it straight from the monorepo:
+
+```json
+{
+  "mcpServers": {
+    "workhorse": {
+      "command": "node",
+      "args": ["apps/workhorse/mcp/server.mjs"]
+    }
+  }
+}
+```
+
+Data lives in `~/.workhorse/workhorse.db` (override with `WORKHORSE_DB`).
+On first start the server creates the directory and the database itself.
+
+## Connect to the cloud (optional)
+
+The journal works fully offline. To sync it with a Planado workspace, issue
+an MCP token on the workspace's MCP page and ask your agent to call the
+`connect` tool:
+
+```json
+connect {
+  "url": "https://<your-workspace>/api/mcp/journal-sync",
+  "token": "<mcp token>"
+}
+```
+
+`connect` verifies the connection first and only then writes `sync.json`
+next to the database — no manual configuration. The journal id defaults to
+a normalized `<username>-<hostname>`. After that, every journal write is
+auto-pushed; `sync` forces a push, and `inbox`/`take` pull task intents
+from the cloud.
+
+## License
+
+MIT