Web UI: Runtime health and stale MCP detection #430

Closed
opened 2026-07-07 12:21:01 -05:00 by jcwalker3 · 1 comment
Owner

Problem statement

Operators cannot quickly see which MCP profile/runtime is active, whether it matches merged safety gates, or when a restart is required.

Scope

Show MCP runtime/version/profile health in the web UI:

  • active server identity and profile
  • workflow/schema hash when available
  • server code SHA or package version
  • stale-runtime warnings after safety-gate merges
  • links to restart/reload instructions

Acceptance criteria

  • Displays active MCP server/runtime identity (host, repo root, profile name)
  • Displays active profile and role kind
  • Displays workflow hash/schema hash when available from runtime context tools
  • Displays server code SHA or installed version when available
  • Warns when runtime appears stale relative to merged safety-gate changes
  • Provides links or embedded instructions for restart/reload (#420)

Non-goals

  • Performing MCP restart from the UI in MVP
  • Exposing tokens or auth headers
  • Replacing gitea_get_runtime_context / gitea_whoami proofs in final reports

Relation to tracker

Child of tracker #425. Implements one slice of the MCP Control Plane internal web UI. Does not duplicate backend policy already enforced by MCP tools/workflows.

Dependencies

Depends on #426 ( /runtime route). Related: #420 MCP hot reload.

Notes

Surface read-only data from existing MCP diagnostics (gitea_get_runtime_context, gitea_whoami, shell health).

## Problem statement Operators cannot quickly see which MCP profile/runtime is active, whether it matches merged safety gates, or when a restart is required. ## Scope Show MCP runtime/version/profile health in the web UI: - active server identity and profile - workflow/schema hash when available - server code SHA or package version - stale-runtime warnings after safety-gate merges - links to restart/reload instructions ## Acceptance criteria - Displays active MCP server/runtime identity (host, repo root, profile name) - Displays active profile and role kind - Displays workflow hash/schema hash when available from runtime context tools - Displays server code SHA or installed version when available - Warns when runtime appears stale relative to merged safety-gate changes - Provides links or embedded instructions for restart/reload (#420) ## Non-goals - Performing MCP restart from the UI in MVP - Exposing tokens or auth headers - Replacing `gitea_get_runtime_context` / `gitea_whoami` proofs in final reports ## Relation to tracker Child of tracker #425. Implements one slice of the MCP Control Plane internal web UI. Does not duplicate backend policy already enforced by MCP tools/workflows. ## Dependencies Depends on #426 ( `/runtime` route). Related: #420 MCP hot reload. ## Notes Surface read-only data from existing MCP diagnostics (`gitea_get_runtime_context`, `gitea_whoami`, shell health).
jcwalker3 added the status:in-progress label 2026-07-07 13:23:25 -05:00
Author
Owner

Issue claim heartbeat

<!-- gitea-issue-claim-heartbeat:v1 --> **Issue claim heartbeat** - kind: claim - issue: #430 - branch: feat/issue-430-runtime-health - phase: claimed - profile: prgs-author - pr: none - blocker: none - next_action: create worktree and begin implementation
sysadmin removed the status:in-progress label 2026-07-09 07:25:49 -05:00
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#430