@anyforge/mcp-server 3.15.0 → 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.
- package/README.md +15 -4
- package/dist/index.js +10 -8
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -183,6 +183,7 @@ complete capability and local/remote workspace boundary.
|
|
|
183
183
|
| `anyforge_get_program_intake_definition` | read | Read a program's intake definition (the typed form its intake agent interviews against), the checklist that applies, and its version history; `version` reads one version in full |
|
|
184
184
|
| `anyforge_set_program_intake_definition` | write | Edit a program's intake definition; every change is a new version, and a change that strands answers open requests hold needs `acknowledgeImpact` (use `dryRun` to preview) |
|
|
185
185
|
| `anyforge_restore_program_intake_version` | write | Republish an earlier intake definition version as a new version |
|
|
186
|
+
| `anyforge_set_program_intake_routing` | write | Replace a program's intake routing rules (where completed requests are sent on, by the reporter's answers); program lead or owner only |
|
|
186
187
|
| `anyforge_get_intake_request_details` | read | Read one program intake request's answers against its program's intake definition: each field's state, answer, who gave it, and whether it can be edited |
|
|
187
188
|
| `anyforge_edit_intake_request_details` | write | Set, confirm or clear a program intake request's answers by hand (validated against the definition; audited; no re-approval, no follower notice) |
|
|
188
189
|
| `anyforge_update_program` | write | Update a program's name / status / owner / lead / long-lived flag / target date / coverage goal / tags / change freezes |
|
|
@@ -201,7 +202,8 @@ complete capability and local/remote workspace boundary.
|
|
|
201
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` |
|
|
202
203
|
| `anyforge_get_initiative` | read | Initiative + crew and work-item rows + burn-down; long text is excerpted unless `shape: "full"` |
|
|
203
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 |
|
|
204
|
-
| `anyforge_propose_initiative_spec` | write | Submit an ICE spec for human review; it becomes active only when a person
|
|
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` |
|
|
205
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 |
|
|
206
208
|
| `anyforge_delete_initiative` | write | Delete a DRAFT initiative (archive via update once it's past DRAFT) |
|
|
207
209
|
| `anyforge_list_initiative_comments` | read | List an initiative's Discussion comments — the same threaded comments the console shows |
|
|
@@ -243,6 +245,8 @@ complete capability and local/remote workspace boundary.
|
|
|
243
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` |
|
|
244
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) |
|
|
245
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` |
|
|
246
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 |
|
|
247
251
|
| `anyforge_create_work_item` | write | Create a work item with routing, migration, incident, intake, estimate, and evidence fields |
|
|
248
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) |
|
|
@@ -329,6 +333,8 @@ complete capability and local/remote workspace boundary.
|
|
|
329
333
|
| `anyforge_create_risk` | write | Record an accepted risk on a program, initiative or work item: owner (defaults to you), `reviewBy` date or `acceptedUntilMilestoneId`, trigger, mitigation. A risk never blocks dispatch, `Depends on` or the critical path |
|
|
330
334
|
| `anyforge_list_risks` | read | List accepted risks for a program (`programId`) or one subject (`subjectKind` + `subjectId`); closed risks only with `includeClosed` |
|
|
331
335
|
| `anyforge_update_risk` | write | Change a risk's status (for example `MATERIALISED` or `CLOSED`), owner, review date, mitigation or follow-up work items; only the fields passed change |
|
|
336
|
+
| `anyforge_list_skills` | read | The company skill library: id, name, category, one-line description, length and source, without the text (`q` narrows) |
|
|
337
|
+
| `anyforge_create_skill` | write | Add one skill (`name`, `category`, `content`, optional `description`, `languages`, `force`) through the Skills page's create path: unique name, content scan, similar-intent check. Never exposed to the Oracle from here. Needs an Owner, Operator or Editor |
|
|
332
338
|
| `anyforge_list_connected_tools` | read | The company MCP servers an owner opened to local agents, and the tools on them you may use (`access` read or write, `needsApproval`, `actsAs` company or you). Pass `server` for input schemas. Needs an Owner, Operator or Editor on a personal key |
|
|
333
339
|
| `anyforge_call_connected_tool` | read | Call one listed tool (`server`, `tool`, `arguments`). A read runs with the stored credential and returns its result; a write, or a tool marked `needsApproval`, is raised for a person's approval and returns `pending_approval` with a `callId`. Writes need an Owner or Operator and the `write` scope. Every call is audited without its arguments or result |
|
|
334
340
|
| `anyforge_get_connected_tool_call` | read | Where your approval-gated call stands (`pending_approval`, `approved`, `executed`, `failed`, `rejected`, `expired`) and, once settled, what happened |
|
|
@@ -361,8 +367,8 @@ item's labels and `classificationRevision` after the write.
|
|
|
361
367
|
`link-external`, `verification`, `add-evidence`, `remove-evidence`,
|
|
362
368
|
`share-evidence`, `undefer`, `set-cycle`, `link-pull-request`,
|
|
363
369
|
`unlink-pull-request`, `link-work-item`, `unlink-work-item`, `keep-listed`,
|
|
364
|
-
`set-review`, `set-latest-status`, `set-
|
|
365
|
-
`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
|
|
366
372
|
to the Control API's (`app/lib/control/patchFields.ts`).
|
|
367
373
|
|
|
368
374
|
`status` with no `action` is the Console status menu's plain move: BACKLOG,
|
|
@@ -379,7 +385,12 @@ write would refuse now, with the refusal's code), `restore` (`reopen` or
|
|
|
379
385
|
`finished` or `dropped`). `set-review` takes `inReview`, and `begin` takes it
|
|
380
386
|
too to start an item already in review. `set-type` and `set-due-date` change
|
|
381
387
|
one field at any status. `set-latest-status` takes `latestStatus` (up to 1000
|
|
382
|
-
characters, client-visible on shared reports; null clears it).
|
|
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`
|
|
383
394
|
keeps an unarchived DONE or DROPPED item off the automatic archive.
|
|
384
395
|
`checklist` applies `checklistOps` with `ifChecklistRevision` (the item's
|
|
385
396
|
`checklistRevision`, 0 when absent), and `checklist-promote` turns the step
|