@anyforge/mcp-server 3.15.1 → 3.16.0

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 +12 -4
  2. package/dist/index.js +10 -8
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -202,7 +202,8 @@ complete capability and local/remote workspace boundary.
202
202
  | `anyforge_list_initiatives` | read | List initiatives with progress + budget. Returns ONE PAGE (50 default, 100 max) — continue with `meta.nextCursor`, or narrow with `programId`, `status`, `priority`, `owner`, `tag`, `search`. Unknown arguments are rejected; the page echoes `appliedFilters` |
203
203
  | `anyforge_get_initiative` | read | Initiative + crew and work-item rows + burn-down; long text is excerpted unless `shape: "full"` |
204
204
  | `anyforge_get_initiative_spec` | read | Read the active ICE spec, its readiness, what backlog approval will decide (`approvalGate`), and any submission awaiting human review |
205
- | `anyforge_propose_initiative_spec` | write | Submit an ICE spec for human review; it becomes active only when a person reviews and publishes it in the Console. The receipt carries `reviewUrl`, the absolute Console link to the review page, beside `reviewPath` |
205
+ | `anyforge_propose_initiative_spec` | write | Submit an ICE spec for human review; it becomes active only when a person publishes it, in the Console or with `anyforge_publish_initiative_spec`. The receipt carries `reviewUrl`, the absolute Console link to the review page, beside `reviewPath` |
206
+ | `anyforge_publish_initiative_spec` | approve | Publish a pending submission (`submissionId`) as the active spec, exactly as submitted, once the person has read it and asked for it. Only over the hosted MCP (OAuth): a Control API key is refused with `spec_publish_requires_person` |
206
207
  | `anyforge_update_initiative` | write | Update a (non-system) initiative — only the fields you pass change, including its owning team (`teamId`); an argument the tool does not declare is refused and nothing is changed |
207
208
  | `anyforge_delete_initiative` | write | Delete a DRAFT initiative (archive via update once it's past DRAFT) |
208
209
  | `anyforge_list_initiative_comments` | read | List an initiative's Discussion comments — the same threaded comments the console shows |
@@ -244,6 +245,8 @@ complete capability and local/remote workspace boundary.
244
245
  | `anyforge_list_label_groups` | read | List the company label groups (id, name, ordered labels, `appliesTo`). A group's name is not a label: pass one of its labels to `anyforge_list_work_items` as `label` |
245
246
  | `anyforge_list_work_boards` | read | List the saved Work boards; a board that follows a label group carries `labelColumns` and `columnLabels` (the stage labels in column order) |
246
247
  | `anyforge_list_cycles` | read | List a team's delivery cycles on its own cadence (`team`, a slug; left out, the workspace cadence): number, dates, `state` (ended / active / future), `isCurrent`, `locked` and `lockReason` (`started` or `signed_off`), `openReason` (`not_signed_off` for a started cycle of a team that locks only at sign-off), committed counts (initiatives, work items, demand days) and capacity per cycle, plus `currentCycleNumber`. `past` (0–12, default 2) and `ahead` (0–6, default 3) set the range. Use it to pick a cycle for `anyforge_update_work_item` `set-cycle` |
248
+ | `anyforge_get_timesheet_week` | read | Your own timesheet week (`date`, any day in it; `today`, your local date), as the Timesheets grid shows it: `days`, bookable `rows` and `categories` with each day's `bookable` and refusal `reason`, `addable`, `blocked`, and `entries` (`initiativeId` or category key, `date`, `minutes`, `note`, `source` `manual`/`auto`). Always the key holder's own time |
249
+ | `anyforge_book_time` | write | Book, change or clear up to 100 cells of your own timesheet (`entries`: `initiativeId` or a category key such as `@meetings`, `date`, `minutes`, optional `note` and `mode` `set`/`add`; `today`), ALL OR NOTHING: a refused cell (`not_bookable` with its `reason`, `day_over_limit`, `initiative_not_found`, `duplicate_entry`) is named by `index` and nothing is written. Cells not sent are left as they are; an empty list returns `written: 0` |
247
250
  | `anyforge_get_work_item` | read | Get one work item by its returned id, with `assigneeName`, `blockerOwnerName` and `createdByName` beside the uids (null when nobody visible is named; list items carry them too), and `nextActions`: the status moves this key can make now, each with the exact arguments to send |
248
251
  | `anyforge_create_work_item` | write | Create a work item with routing, migration, incident, intake, estimate, and evidence fields |
249
252
  | `anyforge_update_work_item` | write | Edit, assign, begin, expedite, dispatch, confirm, drop (with optional `droppedReason`), archive, close, or reopen a work item. Each action takes only its own fields: one it does not read is refused (`unsupported_fields`) and nothing is changed. `status` with no action is the plain move to BACKLOG, REFINED or READY (how an item moves back) |
@@ -364,8 +367,8 @@ item's labels and `classificationRevision` after the write.
364
367
  `link-external`, `verification`, `add-evidence`, `remove-evidence`,
365
368
  `share-evidence`, `undefer`, `set-cycle`, `link-pull-request`,
366
369
  `unlink-pull-request`, `link-work-item`, `unlink-work-item`, `keep-listed`,
367
- `set-review`, `set-latest-status`, `set-type`, `set-due-date`, `checklist`, and
368
- `checklist-promote`. A root test holds this list and each action's fields equal
370
+ `set-review`, `set-latest-status`, `set-request-review`, `set-type`,
371
+ `set-due-date`, `checklist`, and `checklist-promote`. A root test holds this list and each action's fields equal
369
372
  to the Control API's (`app/lib/control/patchFields.ts`).
370
373
 
371
374
  `status` with no `action` is the Console status menu's plain move: BACKLOG,
@@ -382,7 +385,12 @@ write would refuse now, with the refusal's code), `restore` (`reopen` or
382
385
  `finished` or `dropped`). `set-review` takes `inReview`, and `begin` takes it
383
386
  too to start an item already in review. `set-type` and `set-due-date` change
384
387
  one field at any status. `set-latest-status` takes `latestStatus` (up to 1000
385
- characters, client-visible on shared reports; null clears it). `keep-listed`
388
+ characters, client-visible on shared reports; null clears it).
389
+ `set-request-review` takes `requestReview` (`under_review` or
390
+ `waiting_on_requester`, null clears it) on a request in a program's Incoming
391
+ Requests; it changes no status, is refused with 409
392
+ `request_review_requires_intake_bucket` elsewhere, and routing the request
393
+ clears it. `keep-listed`
386
394
  keeps an unarchived DONE or DROPPED item off the automatic archive.
387
395
  `checklist` applies `checklistOps` with `ifChecklistRevision` (the item's
388
396
  `checklistRevision`, 0 when absent), and `checklist-promote` turns the step