@loopable/mcp 0.4.0 → 0.4.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +7 -7
  2. package/lib/tools.mjs +23 -39
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -15,7 +15,7 @@ for Claude Code; any other MCP host runs it the same way:
15
15
 
16
16
  Any studio member mints their own in Loopable, from the account menu under
17
17
  **My agent tokens**: it acts as them, and whatever their role, as a developer —
18
- it works the backlog and reports up to `in_review`, and it can never approve,
18
+ it works the backlog and moves any item to any status, and it can never approve,
19
19
  change settings or decide what a client sees — unless they tick **Let it act
20
20
  as my role** when minting it, which lends it their own studio role (still never
21
21
  a client seat, a client conversation, a new token, or the approval of a draft a
@@ -76,7 +76,7 @@ gets this server, and most of them do not have a token.
76
76
  | `revise` | correct an item's title or body |
77
77
  | `link_items` | say one item blocks another |
78
78
  | `write_brief` | the spec of one item — the ask, the acceptance criteria, what is out of scope. Written directly on a studio token, proposed on any other |
79
- | `report_progress` | move an item to todo / in_progress / in_review / blocked / awaiting_input. ready / verifying / done are a person's words: only a token its owner minted with the grant may set them, and only when that person asks and names the items |
79
+ | `report_progress` | move an item to any status — todo / ready / in_progress / in_review / verifying / done / blocked / awaiting_input / dropped — on your own judgement; the trail names you and the token. `ready_blockers` reports what is missing; it never refuses a move |
80
80
  | `open_session` | say you have started on an item — opens the live record of this piece of work |
81
81
  | `post_activity` | one line into an open session: thought, action, question, result or error |
82
82
  | `close_session` | end it — `error` takes a summary; `complete` is a claim and carries its evidence (brief revision, HEAD sha, verdict, every criterion, screenshots, cost, and optionally the pull request url — open it first, because a closed session is never updated again), and moves the item to `in_review` |
@@ -142,11 +142,11 @@ open the session — and until it lands, doing it by hand in that order is the
142
142
  same thing.
143
143
 
144
144
  `ready_blockers` is the one field to read before anything else. A non-empty
145
- list means nobody has groomed the item — no brief has been written, there is
146
- no criterion carrying a verify method, or the project has no registered
147
- environment — and it is not work to pick up yet. It is judged when you read a
148
- `todo` or `ready` item, not only when the clock last groomed it, and while it
149
- is not empty no agent token may move the item to `ready`.
145
+ list is a report on the item — no brief has been written, there is no
146
+ criterion carrying a verify method, or a browser or http criterion has no
147
+ registered environment. It is judged when you read a `todo` or `ready` item,
148
+ not only when the clock last groomed it. Nothing refuses a state edge or a
149
+ start because of it: say what is missing, and start anyway if you decide to.
150
150
 
151
151
  ## Which kind
152
152
 
package/lib/tools.mjs CHANGED
@@ -623,7 +623,9 @@ export const TOOLS = [
623
623
  'criteria with how each will be checked, what is around it in the graph ' +
624
624
  'BY TITLE, the standing decisions that govern it, the registered ' +
625
625
  'environments to point at, and `ready_blockers` — which, if it is not ' +
626
- 'empty, means the item is not groomed and is not work to pick up yet. ' +
626
+ 'empty, says what is missing from it (no brief, no criterion with a ' +
627
+ 'verify method, no environment for a browser or http criterion) — a ' +
628
+ 'report, never a bar: nothing refuses a start for it. ' +
627
629
  'Prefer this over get_item plus neighbourhood plus list_decisions: it is ' +
628
630
  'the same reads, assembled once and capped. `truncated` with `trimmed` ' +
629
631
  'says what was cut to make it fit — the neighbourhood goes first, the ' +
@@ -651,9 +653,8 @@ export const TOOLS = [
651
653
  description:
652
654
  'What to pick up next: the oldest `ready` item nobody has an open ' +
653
655
  'session on, as the same pack pull_item returns. `ready` means a person ' +
654
- 'or a grooming pass judged it startable — criteria somebody can act on, ' +
655
- 'and somewhere to run them — so an item this hands back needs no ' +
656
- 'further check before starting. `null` is an ordinary answer and not an ' +
656
+ 'or a grooming pass said it was startable; read its `ready_blockers` ' +
657
+ 'all the same. `null` is an ordinary answer and not an ' +
657
658
  'error: it means everything is either not ready or already being ' +
658
659
  'worked. IT DOES NOT CLAIM THE ITEM. Two harnesses asking at the same ' +
659
660
  'moment are told the same thing; claiming is open_session, and ' +
@@ -1119,43 +1120,25 @@ export const TOOLS = [
1119
1120
  {
1120
1121
  name: 'report_progress',
1121
1122
  /*
1122
- * THE ENUM IS THE AGENT'S HALF OF THE TRANSITION TABLE, plus the three
1123
- * edges a person may hand their own token (342). `ready`, `verifying` and
1124
- * `done` are a person's words — grooming, deploying and accepting are
1125
- * seats a person sits in — and the API refuses them from a token whose
1126
- * holder did not mint it with the grant, whatever this file offers. They
1127
- * are offered because a token minted with it may take them, for its
1128
- * holder, when the holder asks; the description says so, and says that
1129
- * without the grant the answer is a 403 — except todo → ready on an item
1130
- * this token filed itself, once readiness has no blockers (364), and
1131
- * in_review → verifying at the merge (365).
1132
- * `dropped` is never offered: no token takes it.
1123
+ * EVERY STATUS IS OFFERED (410). A studio token takes any edge a studio
1124
+ * person takes, `done` and `dropped` included, and the trail names the
1125
+ * person and the token for each move. Readiness is no condition (411):
1126
+ * `ready_blockers` is read on the item, never enforced.
1133
1127
  */
1134
1128
  description:
1135
- 'Move a work item to todo, in_progress, in_review, blocked or ' +
1136
- 'awaiting_input. This is how the backlog stays true — report it as part ' +
1137
- 'of doing the work, not as a chore afterwards, and say WHAT happened in ' +
1138
- 'the note ("opened PR 475, tests green"): that sentence exists only ' +
1139
- 'right now, and the studio feed is a delivery log exactly as far as ' +
1140
- 'people write it. in_review is as far as you go: a person reads the ' +
1141
- 'diff, merges, and accepts the work as done. Say blocked when something ' +
1142
- 'outside the item is stopping you and awaiting_input when you need an ' +
1143
- 'answer — both beat leaving the item claiming work is happening. ' +
1144
- 'ready, verifying and done are the person’s, not yours: the API ' +
1145
- 'refuses them unless the person who owns your token minted it with the ' +
1146
- 'grant to set them, and even then you set one ONLY when that person asks ' +
1147
- 'for it in the session and names the items — never on your own judgement ' +
1148
- 'that the work is ready or finished. Such a move is recorded as theirs, ' +
1149
- 'made through your token. The one exception without the grant: you may ' +
1150
- 'set ready only on an item you filed yourself, through this same token, ' +
1151
- 'from todo, once its readiness has no blockers (get_item shows ' +
1152
- 'ready_blockers) — anything a person or another token filed gets the ' +
1153
- '403. And verifying, at the merge: once the pull request of an item in ' +
1154
- 'in_review has merged, you may move it in_review → verifying while the ' +
1155
- 'deploy owes the checks its close left after_merge. It comes back to ' +
1156
- 'in_review only through close_session, with every criterion met — never ' +
1157
- 'through this tool. To change what an item SAYS rather than ' +
1158
- 'where it is, use revise.',
1129
+ 'Move a work item to any status: todo, ready, in_progress, in_review, ' +
1130
+ 'verifying, done, blocked, awaiting_input or dropped. This is how the ' +
1131
+ 'backlog stays true — report it as part of doing the work, not as a ' +
1132
+ 'chore afterwards, and say WHAT happened in the note ("opened PR 475, ' +
1133
+ 'tests green"): that sentence exists only right now, and the studio ' +
1134
+ 'feed is a delivery log exactly as far as people write it. You move an ' +
1135
+ 'item on your own judgement; the trail records the move under your ' +
1136
+ 'person and this token, and that record is the control. Say blocked ' +
1137
+ 'when something outside the item is stopping you and awaiting_input ' +
1138
+ 'when you need an answer — both beat leaving the item claiming work is ' +
1139
+ 'happening. ready is never refused for ready_blockers: they are what get_item ' +
1140
+ 'reports is missing, so say what you decided. To change what an item SAYS rather than where ' +
1141
+ 'it is, use revise.',
1159
1142
  input: {
1160
1143
  type: 'object',
1161
1144
  properties: {
@@ -1175,6 +1158,7 @@ export const TOOLS = [
1175
1158
  'ready',
1176
1159
  'verifying',
1177
1160
  'done',
1161
+ 'dropped',
1178
1162
  ],
1179
1163
  },
1180
1164
  note: {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@loopable/mcp",
3
- "version": "0.4.0",
3
+ "version": "0.4.2",
4
4
  "description": "The Loopable MCP server: an agent reads the backlog it is meant to build, proposes work, asks the studio a question, and says when it is done.",
5
5
  "license": "MIT",
6
6
  "homepage": "https://loopable.ai",