@anyforge/mcp-server 3.11.0 → 3.13.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 +75 -9
  2. package/dist/index.js +37 -8
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -19,6 +19,30 @@ Firebase login.
19
19
  > MCP authorization can instead connect to the hosted endpoint
20
20
  > `https://crew.anyforge.ai/api/mcp` and sign in with OAuth.
21
21
 
22
+ ### Hosted OAuth workspace selection
23
+
24
+ The hosted endpoint supports an opt-in explicit workspace mode after the
25
+ corresponding application release. One connection can authorize up to 20
26
+ workspaces, selected on the consent screen with their own roles and effective
27
+ scopes. Existing single-workspace connections keep their behavior; reauthorize
28
+ to opt in or to add a workspace.
29
+
30
+ In explicit mode, call `anyforge_list_workspaces` for the currently authorized,
31
+ consented workspace IDs, names, roles and effective scopes, then pass
32
+ `workspaceId` on every tenant tool call. There is no mutable active workspace.
33
+ Ask the user when a target is ambiguous. Missing, unconsented or revoked targets
34
+ are denied. Switching workspace in the Console does not change a call's target.
35
+
36
+ **Settings → API keys → Connected clients** shows only the current workspace's
37
+ grant. Revoking a row withdraws that workspace; client token revocation and
38
+ refresh-token reuse detection revoke the whole connection.
39
+
40
+ This is specific to OAuth for the exact hosted `/api/mcp` resource. The stdio
41
+ package continues to use a single-workspace API key and does not add workspace
42
+ discovery or `workspaceId` arguments. API keys and vendor proxy endpoints also
43
+ retain their existing workspace boundary. Building or publishing this package
44
+ does not deploy hosted workspace selection.
45
+
22
46
  ## Platform guide for connected agents
23
47
 
24
48
  The server advertises a static `anyforge-platform` guide without tenant data or
@@ -177,7 +201,7 @@ complete capability and local/remote workspace boundary.
177
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` |
178
202
  | `anyforge_get_initiative` | read | Initiative + crew and work-item rows + burn-down; long text is excerpted unless `shape: "full"` |
179
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 |
180
- | `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` |
181
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 |
182
206
  | `anyforge_delete_initiative` | write | Delete a DRAFT initiative (archive via update once it's past DRAFT) |
183
207
  | `anyforge_list_initiative_comments` | read | List an initiative's Discussion comments — the same threaded comments the console shows |
@@ -218,13 +242,21 @@ complete capability and local/remote workspace boundary.
218
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` |
219
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` |
220
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) |
221
- | `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) |
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 |
222
247
  | `anyforge_create_work_item` | write | Create a work item with routing, migration, incident, intake, estimate, and evidence fields |
223
- | `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. There is no `status` argument |
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) |
224
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 |
225
- | `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 |
226
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 |
227
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`) |
253
+ | `anyforge_list_work_item_files` | read | List the files attached to a work item (`GET /work/{id}/files`), one page at a time |
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 |
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`) |
256
+ | `anyforge_start_file_upload` | write | Start a direct upload (`POST …/files/uploads`); returns the resumable Storage `uploadUrl` and a `curl` command |
257
+ | `anyforge_complete_file_upload` | write | Complete it (`POST …/files/uploads/{uploadId}`); the file is attached only now |
258
+ | `anyforge_list_initiative_files` | read | An initiative's Files tab (`GET /initiatives/{id}/files`) |
259
+ | `anyforge_list_program_files` | read | A program's Files tab (`GET /programs/{id}/files`) |
228
260
  | `anyforge_split_work_item` | write | Replace one unstarted work item with multiple children |
229
261
  | `anyforge_merge_work_items` | write | Replace multiple unstarted work items with one merged item |
230
262
  | `anyforge_list_crews` | read | Discover crews by status, active state, and limit |
@@ -242,7 +274,7 @@ complete capability and local/remote workspace boundary.
242
274
  | `anyforge_dispatch_architect` | write | Decompose an initiative into a backlog (→ HIL #1) |
243
275
  | `anyforge_list_repo_index` | read | List the org repo index (activity, coverage, analyzed) — discover codebases to scope |
244
276
  | `anyforge_get_repo_analysis` | read | One repo's coverage / architecture / gap summary |
245
- | `anyforge_check_dispatch_readiness` | read | Check the repository's Phase 1 + Phase 2 analysis gate before dispatch; does not launch a crew |
277
+ | `anyforge_check_dispatch_readiness` | read | With `workItemId`, list every blocker that would stop a crew starting on that item; with only `repoFullName`, check the repository's analysis gate. Does not launch a crew |
246
278
  | `anyforge_analyze_repos` | write | Start Phase-1 analysis for one or more repos; Phase 2 follows automatically when Phase 1 completes |
247
279
  | `anyforge_start_coverage_sweep` | write | Paced Phase 1→2 analysis sweep over a program/repo set |
248
280
  | `anyforge_refresh_repo_index` | write | Refresh the repo index + committed-coverage detection now |
@@ -324,12 +356,40 @@ item's labels and `classificationRevision` after the write.
324
356
  `dismiss-automation-suggestion`, `expedite`, `block`, `unblock`,
325
357
  `link-external`, `verification`, `add-evidence`, `remove-evidence`,
326
358
  `share-evidence`, `undefer`, `set-cycle`, `link-pull-request`,
327
- `unlink-pull-request`, `link-work-item`, and `unlink-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.
328
383
  `link-work-item` with `linkedWorkItemId` and `linkType` (`relates_to` or
329
384
  `duplicates`) connects two work items at any status, done and dropped
330
385
  included; `unlink-work-item` with the same fields removes the link. `undefer` returns an item
331
386
  deferred at plan
332
- approval to the ordinary backlog flow. Use `drop` for an obsolete
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
333
393
  unfinished item and pass `droppedReason` when the reconciliation needs an audit
334
394
  explanation. `archive` requires `DONE` or `DROPPED`; if it returns
335
395
  `archive_requires_terminal`, drop the item first. `close-as-fixed` instead
@@ -358,8 +418,14 @@ is internal unless `clientVisible: true`; `anyforge_share_work_item_comment`
358
418
  (`itemId`, `commentId`, `clientVisible`) changes an existing comment. The gate is
359
419
  the Console's: `write` scope and a key owner who is currently an Editor or
360
420
  above, so a key with no user gets `key_not_attributable`. A reply can be shared
361
- only while its parent is shared (`parent_not_shared`). Replies and attachments
362
- stay Console-only.
421
+ only while its parent is shared (`parent_not_shared`). Replies and comment
422
+ attachments stay Console-only. Item files go through `anyforge_add_work_item_files`
423
+ (same gate; bytes as `contentBase64`). Larger files, and initiative and program
424
+ files, go through a direct upload (`tools/files.ts`): the bytes go to Storage
425
+ through a resumable session the API opens, never through the API.
426
+ `anyforge_upload_local_file` reads a local path and is refused when
427
+ `isHostedTransport()` is true, because the hosted endpoint runs the same
428
+ handlers on the server, where a path would name the server's own disk.
363
429
 
364
430
  The structured Program Genesis writes are program-scoped. Brief saves are full
365
431
  versioned replacements through `anyforge_save_program_brief_version`. Initiative