Skip to content

docs: list all eleven MCP servers in the enterprise governance registry guide - #23494

Merged
iamwhatever merged 1 commit into
kirodotdev:mainfrom
Mening-dotcom:docs/enterprise-mcp-governance-registry
Nov 4, 2026
Merged

iamwhatever merged 1 commit into
kirodotdev:mainfrom
Mening-dotcom:docs/enterprise-mcp-governance-registry

Conversation

@Mening-dotcom

Copy link
Copy Markdown
Contributor

Problem / Motivation

Goal: The enterprise MCP governance guide names every server a governed fleet actually needs, so an admin following it does not silently strip the conductor, dashboard and member-panel surfaces.

The guide's allow-list section says Kiro Crew "needs three servers" and its table and registry JSON example cover only kirocrew-core, kirocrew-cron and kirocrew-computer. The code ships six: kirocrew-work is mounted on every conductor (the work ledger its dispatches are recorded to, which the Dashboard's Workstreams board is minted from), kirocrew-dashboard is the control surface mounted beside it, and kirocrew-panel carries the member panel tools of member-scoped agents. The registry filter applies to all of them, so an admin who allow-lists exactly what the guide shows runs conductor fleets whose boards stay empty, with nothing explaining why. (#23488 reports this as part of a broader report on the registry example.)

Why it matters

This guide is written for the person with the least room to experiment — an enterprise admin configuring a governed fleet. A list that is complete for a chat-only install and silently half-complete for a conductor fleet fails exactly the reader it exists for.

Not a goal

What changed (motivation → approach → change)

Observed: the guide's table, its "needs three servers" framing and its JSON example cover three of the six server names the code mounts. Verified against the tree: agent_materialization/conductor_agents.py mounts kirocrew-work on every conductor and kirocrew-dashboard beside it, acp/kas_agents.py joins @kirocrew-dashboard / @kirocrew-panel into agent tools, and the CLI exposes the matching mcp-work / mcp-dashboard / mcp-panel subcommands. Change: the section now says six servers with which installs need which; the table gains the three missing rows with what is lost without each; the JSON example gains the three matching entries (same one-package/packageArguments shape as the existing three); and "all three Kiro Crew servers live behind one package" becomes "every Kiro Crew server". The example block still parses as JSON (checked) and lists all six names.

Backwards compatibility

Documentation only. An admin who already allow-listed three servers loses nothing; the guide now tells them what the other three are for before a conductor rollout surfaces it the hard way.

Tests

N/A — documentation; the registry JSON example was machine-checked to parse, with all six server names present.

Manual verification

Server names and subcommands cross-checked against the code (conductor_agents.py, kas_agents.py, the mcp-* CLI subcommands) rather than taken from the issue text.

Screenshots / video

N/A — documentation.

Related Issues

Addresses the incomplete server list reported in #23488 (the registry launch-route half of that issue is left open on purpose — see Not a goal).

Checklist

  • At most two commits (one is the norm), with a Conventional Commits title (feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)
  • Existing tests pass and new tests added for new functionality
  • Self-review completed; code follows project style guidelines
  • Documentation updated (if applicable)
  • No secrets, credentials, or internal references in the diff

Contribution License Agreement

Contributions accepted under the project's Apache-2.0 license per CONTRIBUTING.md.

@Mening-dotcom
Mening-dotcom requested review from a team and KiroCrewCaptain as code owners October 23, 2026 16:05
@github-actions github-actions Bot added fork Pull request from a fork (external contributor) readiness: action required A blocking check or review needs attention labels Oct 23, 2026
@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

UX Review (Opus 5.5, fork) — ⏭️ skipped

Revision b96ece4b2756a83a5b66fded81cd2e5dac387e47 touches no user-facing surface (no changes under website/ or committed screenshots), so the UX review was skipped. Does not block merge.

@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

First Principles Review (Opus 5.5, fork) — ⏭️ skipped

Revision b96ece4b2756a83a5b66fded81cd2e5dac387e47 ships no reviewable capability (docs, tests or generated files only), so there is nothing to inventory. Does not block merge.

@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Design Review (Opus 5.5, fork) — ✅ PASS

Design-level review of b96ece4b2756a83a5b66fded81cd2e5dac387e47 via the fork AI-review pipeline — updated in place on each push. A BLOCK verdict blocks PR readiness; PASS does not.

Design-Verdict: PASS

Docs only; all eleven server names and subcommands match _MANAGED_MCP_SERVERS and mcp_entry.py.

Notes

  • The diff and the description disagree. The description says the guide "now says six servers" and the example "lists all six names", but the diff documents eleven. The extra five are guide, mate, crew-log, debug and secrets. Update the What changed and Tests sections so they describe what ships (the Goal line can stay as is).
  • kirocrew-dashboard and kirocrew-panel are listed under "Assignable", yet they are mounted structurally (on every conductor and on member-scoped agents) rather than granted. Calling them "emitted for agents granted the set" may mislead an admin who is deciding whether a conductor fleet needs them.

[DESIGN-REVIEWED] b96ece4

Description read

[DESCRIPTION-READ] 492d0dc7a699257e9e40d178f84fa10d537f718d95bcd6413ad9ee39e4a01009

That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with .github/scripts/pr-description-capture.sh over the same inputs; if it differs, the description or that evidence changed after this verdict was formed and any finding drawn from either is unproven.

@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Opus 5.5 Review (fork) — ✅ no blocking findings

Reviewed b96ece4b2756a83a5b66fded81cd2e5dac387e47 via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.

[OPUS-REVIEWED] b96ece4

@github-actions

github-actions Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

GPT 6.1 Review (fork) — ✅ no blocking findings

Reviewed b96ece4b2756a83a5b66fded81cd2e5dac387e47 via the fork AI-review pipeline; updated in place on each push.

Review details

No findings.
[GPT-REVIEWED] b96ece4

@Mening-dotcom
Mening-dotcom force-pushed the docs/enterprise-mcp-governance-registry branch from 22482c6 to e382fad Compare October 26, 2026 12:36
@Mening-dotcom Mening-dotcom changed the title docs: list all six MCP servers in the enterprise governance registry guide docs: list all ten MCP servers in the enterprise governance registry guide Oct 26, 2026
@Mening-dotcom

Copy link
Copy Markdown
Contributor Author

Both blocking reviews are right: the authoritative map (_MANAGED_MCP_SERVERS, src/kiro_crew/agent.py) defines ten servers, not the six my first push counted — five always emitted (core, cron, computer, guide, mate) and five assignable (work, dashboard, panel, crew-log, debug). The new push corrects the section to all ten, split always-emitted vs assignable, with the table rows and registry JSON entries for each (subcommands verified against the map; the example still parses, ten names). The Problem/Motivation section's 'six' undercount is part of the frozen goal text, so it stays as written — this comment is the correction of record. Title updated to match.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: action required A blocking check or review needs attention and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Oct 26, 2026
@iamwhatever
iamwhatever force-pushed the docs/enterprise-mcp-governance-registry branch from e382fad to b96ece4 Compare November 1, 2026 12:05
@iamwhatever iamwhatever changed the title docs: list all ten MCP servers in the enterprise governance registry guide docs: list all eleven MCP servers in the enterprise governance registry guide Nov 1, 2026
@iamwhatever

Copy link
Copy Markdown
Contributor

Rebased onto latest main. Since this PR was opened, #23855 added an eleventh managed server, kirocrew-secrets (opt-in, mcp-secrets), to _MANAGED_MCP_SERVERS. The guide now lists all eleven: five always emitted and six assignable, with a matching table row and registry JSON entry (the example still parses and lists eleven names). I also tightened the kirocrew-debug row per the Opus note: only the wide debug views are limited to the owner's own dashboard tab. Title updated to match.

@github-actions github-actions Bot added readiness: checking Automated validation is still running readiness: passed Eligible automated validation passed for the current revision and removed readiness: action required A blocking check or review needs attention readiness: checking Automated validation is still running labels Nov 1, 2026
@iamwhatever iamwhatever self-assigned this Nov 2, 2026

@iamwhatever iamwhatever left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approve. Reviewed head b96ece4b2756a83a5b66fded81cd2e5dac387e47.

The guide now lists the eleven managed servers, split into the five always-emitted and six assignable sets, and each table row and registry JSON entry matches _MANAGED_MCP_SERVERS and its mcp-* subcommand on both this head and current main. The file has not moved on main, the merge is clean, and CI is green. The registry launch-route question stays out of scope and is tracked in #23488.

AI findings judged non-blocking

  • Design (Notes): the PR description still says six servers and six JSON names while the diff documents eleven. Does not block: it is PR prose, not the shipped guide, and the eleven-server correction is on record in the author and maintainer replies (#23494 (comment), #23494 (comment)).
  • Design (Notes): kirocrew-dashboard and kirocrew-panel are listed as assignable though conductors mount them structurally. Does not block: the code marks both opt_in: True (
    "kirocrew-dashboard": {
    ,
    "kirocrew-panel": {
    ) and the guide row says dashboard is mounted on every conductor (
    | `kirocrew-dashboard` | the dashboard control surface mounted on every conductor |
    ).
  • Own reading: kirocrew-computer sits under 'Always emitted, on every install', but its entry has a spec_gate and is emitted only when supported and enabled (
    "spec_gate": _computer_use_spec_gate,
    ). Does not block: the row itself says it is inert unless enabled (
    | `kirocrew-computer` | desktop automation on supported macOS and Windows hosts (inert unless separately enabled, but still filtered) |
    ), and an admin who allow-lists it loses nothing.

Optional: refresh the description's What changed and Tests sections to say eleven.

— crew-pr-reviewer (r141)

@bolichen97 bolichen97 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[operator: bolichen97] Approving at b96ece4.

Checked against _MANAGED_MCP_SERVERS in src/kiro_crew/agent.py on main: it has exactly these eleven servers, six of them opt_in (work, dashboard, panel, crew-log, debug, secrets), and each registry entry's subcommand matches the server's _kirocrew_mcp_invocation argument.

AI-assisted, approved by bolichen97

@iamwhatever
iamwhatever merged commit 9d9136b into kirodotdev:main Nov 4, 2026
97 of 105 checks passed
@github-actions github-actions Bot removed the readiness: passed Eligible automated validation passed for the current revision label Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fork Pull request from a fork (external contributor)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants