@anyforge/mcp-server 3.8.0 → 3.9.0

package/README.md

@@ -13,6 +13,12 @@ Firebase login.
 > (`apps/www/content/docs/mcp-server.md`). This README is the in-repo
 > developer reference; the docs page is the canonical install walkthrough.
 
+> **No key needed for OAuth-capable clients.** This package needs an
+> `sk_anyforge_…` key. Claude (via the AnyForge listing in its connectors
+> directory), Claude Code, VS Code, Cursor and any other client that supports
+> MCP authorization can instead connect to the hosted endpoint
+> `https://crew.anyforge.ai/api/mcp` and sign in with OAuth.
+
 ## Platform guide for connected agents
 
 The server advertises a static `anyforge-platform` guide without tenant data or
@@ -155,7 +161,8 @@ complete capability and local/remote workspace boundary.
 | `anyforge_restore_program_intake_version` | write | Republish an earlier intake definition version as a new version |
 | `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 |
 | `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) |
-| `anyforge_update_program` | write | Update a program's name / status / owner / lead / long-lived flag / target date / coverage goal / tags |
+| `anyforge_update_program` | write | Update a program's name / status / owner / lead / long-lived flag / target date / coverage goal / tags / change freezes |
+| `anyforge_set_program_status_line` | write | Write or clear a program's status line, shown on a report's program status board |
 | `anyforge_set_program_request_intake` | write | Turn a program's incoming requests on (creates its Incoming Requests initiative) or off |
 | `anyforge_delete_program` | write | Delete a program; `deleteChildren: true` also deletes child initiatives + work items (else they're detached) |
 | `anyforge_set_program_milestones` | write | Set a program's milestones/waves and the initiatives assigned to each (whole-array replace; an initiative sits in at most one wave) |
@@ -295,12 +302,27 @@ complete capability and local/remote workspace boundary.
 | `anyforge_get_triage_evidence_snapshot` | read | Read a saved company snapshot; Owner/Operator only |
 | `anyforge_get_triage_eval_run` | read | Poll a queued triage eval run by id and read its completed result |
 
+Work item labels (the Console's Labels field) are `tags`.
+`anyforge_create_work_item` takes `tags`. On `anyforge_update_work_item` with
+`action: "update"`, `addTags` and `removeTags` change some labels against the
+labels stored at write time and need no revision, so a script can relabel many
+items without reading each first. `tags` replaces the whole list and needs
+`ifClassificationRevision`, the `classificationRevision` that
+`anyforge_get_work_item` returns. A labels-only update works at any status,
+`DONE`, `DROPPED` and archived items included, and its result carries the
+item's labels and `classificationRevision` after the write.
+
 `anyforge_update_work_item` advertises the complete action enum: `advance`,
-`approve_refinement`, `dispatch`, `complete`, `update`, `reorder`, `archive`,
-`unarchive`, `close-as-fixed`, `reopen`, `mark-incident`, `drop`,
-`confirm-repo`, `assign`, `begin`, `dismiss-automation-suggestion`,
-`expedite`, `link-external`, `verification`, `add-evidence`,
-`remove-evidence`, `share-evidence`, and `undefer`. `undefer` returns an item
+`approve_refinement`, `approve-and-route`, `move-initiative`, `dispatch`,
+`complete`, `update`, `reorder`, `archive`, `unarchive`, `close-as-fixed`,
+`reopen`, `mark-incident`, `drop`, `confirm-repo`, `assign`, `begin`,
+`dismiss-automation-suggestion`, `expedite`, `block`, `unblock`,
+`link-external`, `verification`, `add-evidence`, `remove-evidence`,
+`share-evidence`, `undefer`, `set-cycle`, `link-pull-request`,
+`unlink-pull-request`, `link-work-item`, and `unlink-work-item`.
+`link-work-item` with `linkedWorkItemId` and `linkType` (`relates_to` or
+`duplicates`) connects two work items at any status, done and dropped
+included; `unlink-work-item` with the same fields removes the link. `undefer` returns an item
 deferred at plan
 approval to the ordinary backlog flow. Use `drop` for an obsolete
 unfinished item and pass `droppedReason` when the reconciliation needs an audit