@anyforge/mcp-server 3.14.0 → 3.14.2

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 CHANGED
@@ -242,7 +242,7 @@ 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
- | `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` |
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`), `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` |
246
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 |
247
247
  | `anyforge_create_work_item` | write | Create a work item with routing, migration, incident, intake, estimate, and evidence fields |
248
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) |
@@ -585,6 +585,27 @@ git push origin refs/tags/mcp-server-vX.Y.Z
585
585
  > To publish manually instead: `npm login && npm publish` from this
586
586
  > directory (`prepublishOnly` rebuilds `dist/` first).
587
587
 
588
+ ### Official MCP Registry entry
589
+
590
+ The same workflow then publishes `server.json` to the
591
+ [official MCP Registry](https://registry.modelcontextprotocol.io) as
592
+ `ai.anyforge/anyforge`, listing both the hosted endpoint and this npm package.
593
+ Directories such as GitHub's MCP Registry, Glama and PulseMCP read from it.
594
+
595
+ - `server.json`'s `version`, its npm package `version` and `package.json`'s
596
+ `version` must be equal, and its `name` must equal `package.json`'s
597
+ `mcpName`. The workflow refuses the tag otherwise. `npm version` does not
598
+ update `server.json`, so bump both.
599
+ - The registry checks the published npm package's `mcpName`, so the registry
600
+ step runs only after npm has the version.
601
+ - Publishing proves the `ai.anyforge` namespace with HTTP authentication: the
602
+ public key is `public/.well-known/mcp-registry-auth`, served on
603
+ `https://anyforge.ai`, and the private key is the `MCP_REGISTRY_PRIVATE_KEY`
604
+ Actions secret. Rotating the key means replacing both, and the new file must
605
+ be live in production before the next tag.
606
+
607
+ Check the schema locally with `mcp-publisher validate`.
608
+
588
609
 
589
610
  ### Historical triage compatibility
590
611