ADR: Confirm and extend MCP Control Plane trust-boundary model for Jenkins and GlitchTip #71

New Issue

2026-07-02T05:43:38-05:00

jcwalker3 commented

2026-07-02 05:43:38 -05:00

Curated 2026-07-02 to reflect review consensus (issue text only; not started).

This ADR does not reopen whether the MCP Control Plane model exists — the
existing docs (docs/tool-boundaries.md, docs/safety-model.md,
docs/credential-isolation.md, docs/release-workflows.md,
docs/gitea-execution-profiles.md) already define that direction. It
confirms that model and decides the open extensions for Jenkins and
GlitchTip.

Decisions to record

Whether this repo stays Gitea-only or becomes / feeds the mcp-control-plane
monorepo.
Package naming: common, gitea-mcp, jenkins-mcp, ops-mcp or
glitchtip-mcp, release-mcp.
Where GlitchTip belongs: ops-mcp, glitchtip-mcp, or observability-mcp.
Reaffirm: one server per trust boundary; no single "everything" MCP
server; no credential mixing; read-only first; mutations gated and
audited.

Acceptance criteria

ADR file added under docs/ (e.g. docs/adr/).
Records a clear decision for each open question above.
Does not duplicate boundary text that #79 will apply to the docs — this ADR is
the decision record; #79 is the application.

Feeds: #79 (doc application), #75 (umbrella sequencing).

_Curated 2026-07-02 to reflect review consensus (issue text only; not started)._ This ADR does **not** reopen whether the MCP Control Plane model exists — the existing docs (`docs/tool-boundaries.md`, `docs/safety-model.md`, `docs/credential-isolation.md`, `docs/release-workflows.md`, `docs/gitea-execution-profiles.md`) already define that direction. It **confirms** that model and **decides the open extensions** for Jenkins and GlitchTip. ## Decisions to record * Whether this repo stays Gitea-only or becomes / feeds the `mcp-control-plane` monorepo. * Package naming: `common`, `gitea-mcp`, `jenkins-mcp`, `ops-mcp` **or** `glitchtip-mcp`, `release-mcp`. * Where GlitchTip belongs: `ops-mcp`, `glitchtip-mcp`, or `observability-mcp`. * Reaffirm: **one server per trust boundary**; **no single "everything" MCP server**; **no credential mixing**; **read-only first**; **mutations gated and audited**. ## Acceptance criteria * ADR file added under `docs/` (e.g. `docs/adr/`). * Records a clear decision for each open question above. * Does not duplicate boundary text that #79 will apply to the docs — this ADR is the decision record; #79 is the application. Feeds: #79 (doc application), #75 (umbrella sequencing).

jcwalker3 added the architecture design jenkins glitchtip labels 2026-07-02 05:44:13 -05:00

jcwalker3 referenced this issue

2026-07-02 05:46:25 -05:00

MCP Control Plane umbrella: Jenkins + GlitchTip integrations #75

jcwalker3 changed title from ~~Draft ADR for Jenkins, GlitchTip, and MCP Control Plane architecture~~ to ADR: Confirm and extend MCP Control Plane trust-boundary model for Jenkins and GlitchTip

2026-07-02 11:45:57 -05:00

jcwalker3 referenced this issue

2026-07-02 11:45:57 -05:00

Investigate Jenkins read-only build status tools #72

jcwalker3 referenced this issue

2026-07-02 11:45:58 -05:00

Investigate GlitchTip read-only error/event tools #73

jcwalker3 referenced this issue

2026-07-02 11:45:59 -05:00

Extend profile/config model for multi-service MCP boundaries #76

jcwalker3 referenced this issue

2026-07-02 11:46:00 -05:00