@anyforge/mcp-server 3.12.0 → 3.14.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.
- package/README.md +45 -10
- package/dist/index.js +9 -7
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -201,14 +201,14 @@ complete capability and local/remote workspace boundary.
|
|
|
201
201
|
| `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` |
|
|
202
202
|
| `anyforge_get_initiative` | read | Initiative + crew and work-item rows + burn-down; long text is excerpted unless `shape: "full"` |
|
|
203
203
|
| `anyforge_get_initiative_spec` | read | Read the active ICE spec, its readiness, what backlog approval will decide (`approvalGate`), and any submission awaiting human review |
|
|
204
|
-
| `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 |
|
|
204
|
+
| `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
205
|
| `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 |
|
|
206
206
|
| `anyforge_delete_initiative` | write | Delete a DRAFT initiative (archive via update once it's past DRAFT) |
|
|
207
207
|
| `anyforge_list_initiative_comments` | read | List an initiative's Discussion comments — the same threaded comments the console shows |
|
|
208
208
|
| `anyforge_post_initiative_comment` | write | Post a Discussion comment on an initiative (reply with `parentId`), into the thread the console renders |
|
|
209
209
|
| `anyforge_list_opportunities` | read | List opportunities in the Discovery (product-planning) layer |
|
|
210
|
-
| `anyforge_create_opportunity` | write | Create an opportunity (bridges raw signals to themed roadmap work) |
|
|
211
|
-
| `anyforge_update_opportunity` | write | Edit an opportunity's RICE inputs, stage, theme assignment, or program link (`programId`; `null` unlinks) |
|
|
210
|
+
| `anyforge_create_opportunity` | write | Create an opportunity (bridges raw signals to themed roadmap work). Send `rice` (`reach`, `impact`, `confidence`, `operatorLoad`, `rationale`) in the same call; optional `evidence` is stored on the record |
|
|
211
|
+
| `anyforge_update_opportunity` | write | Edit an opportunity's RICE inputs, `evidence`, stage, theme assignment, or program link (`programId`; `null` unlinks) |
|
|
212
212
|
| `anyforge_delete_opportunity` | write | Hard-delete an opportunity (prefer archiving via `anyforge_update_opportunity`) |
|
|
213
213
|
| `anyforge_promote_opportunity` | write | Promote a prioritized opportunity into a Program + Initiative |
|
|
214
214
|
| `anyforge_list_signals` | read | List signals in the Discovery (product-planning) layer |
|
|
@@ -242,17 +242,18 @@ complete capability and local/remote workspace boundary.
|
|
|
242
242
|
| `anyforge_list_work_items` | read | List backlog items + crew state. Use `itemId` for a full work-item id or queue code, `search` for partial code/title matches, and `includeArchived: true` to include archived items. Also supports status, owner, assignee, program, initiative, team (a team slug, including the teams beneath it), priority, type and `label` (one exact label, such as a stage of a label group) filters. Returns ONE PAGE (50 default, 200 max) — continue with `nextCursor`. Unknown arguments are rejected; the page echoes `appliedFilters` |
|
|
243
243
|
| `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` |
|
|
244
244
|
| `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) |
|
|
245
|
-
| `
|
|
245
|
+
| `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`), 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` |
|
|
246
|
+
| `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 |
|
|
246
247
|
| `anyforge_create_work_item` | write | Create a work item with routing, migration, incident, intake, estimate, and evidence fields |
|
|
247
|
-
| `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.
|
|
248
|
+
| `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) |
|
|
248
249
|
| `anyforge_retry_work_item` | write | Terminate a work item's crew and dispatch a fresh one on the same branch; recovers missing/phantom crew records from work-item + initiative defaults |
|
|
249
|
-
| `anyforge_list_work_item_comments` | read | List the work item's discussion thread, separate from crew transcripts; every comment carries a boolean `clientVisible` |
|
|
250
|
+
| `anyforge_list_work_item_comments` | read | List the work item's discussion thread, separate from crew transcripts; every comment carries a boolean `clientVisible`. `since` (ISO 8601 with a time zone, a date, or epoch ms) returns only comments created after it |
|
|
250
251
|
| `anyforge_post_work_item_comment` | write | Add a discussion comment to a work item; internal unless `clientVisible: true` shares it with the client as it is written |
|
|
251
252
|
| `anyforge_share_work_item_comment` | write | Share an existing work-item comment with the client (`clientVisible: true`) or take it back to internal (`false`) |
|
|
252
253
|
| `anyforge_list_work_item_files` | read | List the files attached to a work item (`GET /work/{id}/files`), one page at a time |
|
|
253
|
-
| `anyforge_add_work_item_files` | write | Attach up to 5 files to a work item (`text`, `contentBase64`, or a local `path` on the stdio server); added internal, Console types and limits, all or nothing, about 7 MB of files per call; optional `idempotencyKey` for safe retries |
|
|
254
|
+
| `anyforge_add_work_item_files` | write | Attach up to 5 files to a work item (`text`, `contentBase64`, or a local `path` on the stdio server); added internal, Console types and limits, all or nothing, about 7 MB of files per call; optional `idempotencyKey` for safe retries, per-file `originalCreatedAt`, and `onNameConflict` |
|
|
254
255
|
| `anyforge_upload_local_file` | write | stdio only: read a file from this machine and direct-upload it (≤ 1 GB) to a work item, initiative or program; refused on the hosted transport (`local_files_unavailable`) |
|
|
255
|
-
| `anyforge_start_file_upload` | write | Start a direct upload (`POST …/files/uploads`); returns the resumable Storage `uploadUrl` and a `curl` command |
|
|
256
|
+
| `anyforge_start_file_upload` | write | Start a direct upload (`POST …/files/uploads`); returns the resumable Storage `uploadUrl` and a `curl` command, or `{ alreadyAttached: true, file }` with nothing to send when the same file is already there; optional `originalCreatedAt` and `onNameConflict` |
|
|
256
257
|
| `anyforge_complete_file_upload` | write | Complete it (`POST …/files/uploads/{uploadId}`); the file is attached only now |
|
|
257
258
|
| `anyforge_list_initiative_files` | read | An initiative's Files tab (`GET /initiatives/{id}/files`) |
|
|
258
259
|
| `anyforge_list_program_files` | read | A program's Files tab (`GET /programs/{id}/files`) |
|
|
@@ -355,12 +356,40 @@ item's labels and `classificationRevision` after the write.
|
|
|
355
356
|
`dismiss-automation-suggestion`, `expedite`, `block`, `unblock`,
|
|
356
357
|
`link-external`, `verification`, `add-evidence`, `remove-evidence`,
|
|
357
358
|
`share-evidence`, `undefer`, `set-cycle`, `link-pull-request`,
|
|
358
|
-
`unlink-pull-request`, `link-work-item`,
|
|
359
|
+
`unlink-pull-request`, `link-work-item`, `unlink-work-item`, `keep-listed`,
|
|
360
|
+
`set-review`, `set-latest-status`, `set-type`, `set-due-date`, `checklist`, and
|
|
361
|
+
`checklist-promote`. A root test holds this list and each action's fields equal
|
|
362
|
+
to the Control API's (`app/lib/control/patchFields.ts`).
|
|
363
|
+
|
|
364
|
+
`status` with no `action` is the Console status menu's plain move: BACKLOG,
|
|
365
|
+
REFINED or READY, from one of those or from work a person began (IN_PROGRESS,
|
|
366
|
+
no crew). It is how an item moves back, it is limited to the same people as the
|
|
367
|
+
menu (the initiative's stewards and Owners), and the item's history records who
|
|
368
|
+
moved it. Any other move answers 409 `raw_status_not_allowed` with
|
|
369
|
+
`allowedStatuses` and `useAction` (`reopen`, `undrop`, `begin`, `complete`,
|
|
370
|
+
`dispatch` or `drop`). `status` beside an action is refused locally.
|
|
371
|
+
`anyforge_get_work_item` returns `nextActions`: `statusMoves` (`{ to, send }`,
|
|
372
|
+
where `send` is the exact arguments for the move), `withheld` (menu moves the
|
|
373
|
+
write would refuse now, with the refusal's code), `restore` (`reopen` or
|
|
374
|
+
`undrop`) and `unavailable` (`read_only`, `not_steward`, `crew_carries`,
|
|
375
|
+
`finished` or `dropped`). `set-review` takes `inReview`, and `begin` takes it
|
|
376
|
+
too to start an item already in review. `set-type` and `set-due-date` change
|
|
377
|
+
one field at any status. `set-latest-status` takes `latestStatus` (up to 1000
|
|
378
|
+
characters, client-visible on shared reports; null clears it). `keep-listed`
|
|
379
|
+
keeps an unarchived DONE or DROPPED item off the automatic archive.
|
|
380
|
+
`checklist` applies `checklistOps` with `ifChecklistRevision` (the item's
|
|
381
|
+
`checklistRevision`, 0 when absent), and `checklist-promote` turns the step
|
|
382
|
+
`checklistItemId` into a sibling work item.
|
|
359
383
|
`link-work-item` with `linkedWorkItemId` and `linkType` (`relates_to` or
|
|
360
384
|
`duplicates`) connects two work items at any status, done and dropped
|
|
361
385
|
included; `unlink-work-item` with the same fields removes the link. `undefer` returns an item
|
|
362
386
|
deferred at plan
|
|
363
|
-
approval to the ordinary backlog flow.
|
|
387
|
+
approval to the ordinary backlog flow. `move-initiative` with
|
|
388
|
+
`targetInitiativeId` moves an item to another initiative at any status,
|
|
389
|
+
`IN_PROGRESS`, `DONE` and `DROPPED` included, keeping its status, pull
|
|
390
|
+
requests and history; it is refused with `move_initiative_crew_running` (409,
|
|
391
|
+
naming the crew) while the item's crew is still running, so halt the crew or
|
|
392
|
+
let it finish first. Use `drop` for an obsolete
|
|
364
393
|
unfinished item and pass `droppedReason` when the reconciliation needs an audit
|
|
365
394
|
explanation. `archive` requires `DONE` or `DROPPED`; if it returns
|
|
366
395
|
`archive_requires_terminal`, drop the item first. `close-as-fixed` instead
|
|
@@ -397,6 +426,12 @@ through a resumable session the API opens, never through the API.
|
|
|
397
426
|
`anyforge_upload_local_file` reads a local path and is refused when
|
|
398
427
|
`isHostedTransport()` is true, because the hosted endpoint runs the same
|
|
399
428
|
handlers on the server, where a path would name the server's own disk.
|
|
429
|
+
Every upload tool passes `originalCreatedAt` (kept beside the upload time) and
|
|
430
|
+
`onNameConflict` through. The API never attaches the same name and size twice
|
|
431
|
+
to one record: it answers `alreadyAttached` instead, and the start of a direct
|
|
432
|
+
upload then carries no `uploadUrl`, so `anyforge_start_file_upload` returns no
|
|
433
|
+
`curl` and `anyforge_upload_local_file` sends nothing. A same-name file of
|
|
434
|
+
another size is `file_name_exists` unless `onNameConflict` is `keep_both`.
|
|
400
435
|
|
|
401
436
|
The structured Program Genesis writes are program-scoped. Brief saves are full
|
|
402
437
|
versioned replacements through `anyforge_save_program_brief_version`. Initiative
|