Update operator runbooks and roadmap docs for Jenkins/GlitchTip MCP status #154

New Issue

2026-07-05T01:57:49-05:00

jcwalker3 commented

2026-07-05 01:57:49 -05:00

Context

Child implementation issue from the accepted Jenkins/GlitchTip MCP audit decision.

The accepted audit status is the working source of truth:

jenkins-readonly and glitchtip-readonly do not exist as registered server names; current names are jenkins-mcp and glitchtip-mcp.
Jenkins mutating trigger behavior exists even though the docs describe the server boundary as read-only.
GlitchTip filing/dedup is partial: filing uses mocked GlitchTip fetch behavior, dedup is not wired into the filing path, mutation audit is missing, and there is no MCP exposure.
Fix docs and MCP registration before claiming these tools are usable by LLM clients.
#4 and #7 stay closed because real code landed, but their remaining exposure/audit/integration gaps are follow-up work.

Scope

Remove or explain stale *-readonly naming.
Document actual server names, tool namespaces, capabilities, and limitations.
Document registration and reload/reconnect steps for supported MCP clients.
Correct Jenkins read-only claims now that trigger code exists.
Document GlitchTip filing/dedup as partial until the orchestrator follow-up lands.
Update roadmap/status docs so completed code, exposed tools, audited mutation paths, and client usability are tracked separately.

Acceptance criteria

Operator docs accurately name the current Jenkins and GlitchTip MCP servers.
Docs no longer imply jenkins-readonly or glitchtip-readonly are usable registered names unless those names are deliberately implemented by #151.
Jenkins docs distinguish read-only tools from any trigger/write-capable surface.
Jenkins docs do not claim the whole server is read-only while jenkins_trigger_build exists in that boundary.
GlitchTip docs distinguish tested read-only tools from partial filing/dedup orchestration.
Registration/reload instructions are included for relevant clients.
Roadmap docs avoid marking Jenkins/GlitchTip items fully complete until registration, exposure, audit, and integration gaps are resolved.

Non-goals

Do not implement MCP registration here except as required by documentation updates; core registration belongs to #151.
Do not correct Jenkins trigger safety here; that belongs to #152.
Do not complete GlitchTip filing orchestration here; that belongs to #153.

Ordering

This is implementation issue 4 of 5. It can proceed alongside or immediately after #151-#153, but should reflect their final decisions before being closed.

## Context Child implementation issue from the accepted Jenkins/GlitchTip MCP audit decision. The accepted audit status is the working source of truth: - `jenkins-readonly` and `glitchtip-readonly` do not exist as registered server names; current names are `jenkins-mcp` and `glitchtip-mcp`. - Jenkins mutating trigger behavior exists even though the docs describe the server boundary as read-only. - GlitchTip filing/dedup is partial: filing uses mocked GlitchTip fetch behavior, dedup is not wired into the filing path, mutation audit is missing, and there is no MCP exposure. - Fix docs and MCP registration before claiming these tools are usable by LLM clients. - #4 and #7 stay closed because real code landed, but their remaining exposure/audit/integration gaps are follow-up work. ## Scope - Remove or explain stale `*-readonly` naming. - Document actual server names, tool namespaces, capabilities, and limitations. - Document registration and reload/reconnect steps for supported MCP clients. - Correct Jenkins read-only claims now that trigger code exists. - Document GlitchTip filing/dedup as partial until the orchestrator follow-up lands. - Update roadmap/status docs so completed code, exposed tools, audited mutation paths, and client usability are tracked separately. ## Acceptance criteria - Operator docs accurately name the current Jenkins and GlitchTip MCP servers. - Docs no longer imply `jenkins-readonly` or `glitchtip-readonly` are usable registered names unless those names are deliberately implemented by #151. - Jenkins docs distinguish read-only tools from any trigger/write-capable surface. - Jenkins docs do not claim the whole server is read-only while `jenkins_trigger_build` exists in that boundary. - GlitchTip docs distinguish tested read-only tools from partial filing/dedup orchestration. - Registration/reload instructions are included for relevant clients. - Roadmap docs avoid marking Jenkins/GlitchTip items fully complete until registration, exposure, audit, and integration gaps are resolved. ## Non-goals - Do not implement MCP registration here except as required by documentation updates; core registration belongs to #151. - Do not correct Jenkins trigger safety here; that belongs to #152. - Do not complete GlitchTip filing orchestration here; that belongs to #153. ## Ordering This is implementation issue 4 of 5. It can proceed alongside or immediately after #151-#153, but should reflect their final decisions before being closed.