Fix MCP registration and naming for Jenkins/GlitchTip servers #151

New Issue

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

jcwalker3 commented

2026-07-05 01:57:02 -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 MCP server code exists as jenkins-mcp.
GlitchTip MCP server code exists as glitchtip-mcp.
jenkins-readonly and glitchtip-readonly do not exist as registered server names; the current names are jenkins-mcp and glitchtip-mcp.
No automatic client registration exists through pyproject.toml entry points or repo docs.
Fix docs and MCP registration before claiming these tools are usable by LLM clients.

This issue must be completed before treating the Jenkins or GlitchTip MCP work as client-usable.

Scope

Add explicit entry points and client-registration documentation for the Jenkins and GlitchTip MCP servers.
Decide and document the canonical server names:
- either keep jenkins-mcp / glitchtip-mcp, or
- deliberately introduce jenkins-readonly / glitchtip-readonly as configured names.
Make naming consistent across code, packaging, docs, tests, and examples.
Add discoverability coverage proving configured MCP clients can see the expected tools.

Acceptance criteria

pyproject.toml or the chosen packaging surface exposes explicit entry points for both servers.
Repo docs show how to register/reload the servers in MCP clients.
The docs name the actual registered server names and do not imply nonexistent *-readonly names unless those names are intentionally implemented.
Tests or validation scripts prove expected Jenkins tools are visible to a configured client.
Tests or validation scripts prove expected GlitchTip tools are visible to a configured client.
Coverage includes a negative case for an enabled server/configuration that exposes no usable tools.

Non-goals

Do not change Jenkins trigger authorization/audit behavior here except where required for naming or discoverability.
Do not complete GlitchTip filing orchestration here.
Do not claim #4, #6, or #7 fully complete based on registration changes alone.

Ordering

This is implementation issue 1 of 5 and should be completed first because invisible tools caused the roadmap drift.

## Context Child implementation issue from the accepted Jenkins/GlitchTip MCP audit decision. The accepted audit status is the working source of truth: - Jenkins MCP server code exists as `jenkins-mcp`. - GlitchTip MCP server code exists as `glitchtip-mcp`. - `jenkins-readonly` and `glitchtip-readonly` do not exist as registered server names; the current names are `jenkins-mcp` and `glitchtip-mcp`. - No automatic client registration exists through `pyproject.toml` entry points or repo docs. - Fix docs and MCP registration before claiming these tools are usable by LLM clients. This issue must be completed before treating the Jenkins or GlitchTip MCP work as client-usable. ## Scope - Add explicit entry points and client-registration documentation for the Jenkins and GlitchTip MCP servers. - Decide and document the canonical server names: - either keep `jenkins-mcp` / `glitchtip-mcp`, or - deliberately introduce `jenkins-readonly` / `glitchtip-readonly` as configured names. - Make naming consistent across code, packaging, docs, tests, and examples. - Add discoverability coverage proving configured MCP clients can see the expected tools. ## Acceptance criteria - `pyproject.toml` or the chosen packaging surface exposes explicit entry points for both servers. - Repo docs show how to register/reload the servers in MCP clients. - The docs name the actual registered server names and do not imply nonexistent `*-readonly` names unless those names are intentionally implemented. - Tests or validation scripts prove expected Jenkins tools are visible to a configured client. - Tests or validation scripts prove expected GlitchTip tools are visible to a configured client. - Coverage includes a negative case for an enabled server/configuration that exposes no usable tools. ## Non-goals - Do not change Jenkins trigger authorization/audit behavior here except where required for naming or discoverability. - Do not complete GlitchTip filing orchestration here. - Do not claim #4, #6, or #7 fully complete based on registration changes alone. ## Ordering This is implementation issue 1 of 5 and should be completed first because invisible tools caused the roadmap drift.

jcwalker3 added the mcp documentation testing integration jenkins glitchtip labels 2026-07-05 01:57:05 -05:00

jcwalker3 referenced this issue

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

Correct Jenkins trigger safety boundary #152

jcwalker3 referenced this issue

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

Complete GlitchTip-to-Gitea filing orchestrator #153

jcwalker3 referenced this issue

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

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

jcwalker3 referenced this issue

2026-07-05 01:58:05 -05:00

Add integration and discoverability coverage for Jenkins/GlitchTip MCP clients #155

jcwalker3 commented

2026-07-05 23:58:21 -05:00

Claiming this for implementation as the next eligible open issue.

Preflight: authenticated as jcwalker3 / prgs-author; exact claim_issue resolved to gitea.issue.comment and is allowed. I will use branch feat/issue-151-mcp-registration-naming, keep scope limited to #151, and stop after opening a PR. No review or merge actions will be performed from this author session.

Claiming this for implementation as the next eligible open issue. Preflight: authenticated as `jcwalker3` / `prgs-author`; exact `claim_issue` resolved to `gitea.issue.comment` and is allowed. I will use branch `feat/issue-151-mcp-registration-naming`, keep scope limited to #151, and stop after opening a PR. No review or merge actions will be performed from this author session.

jcwalker3 referenced a pull request that will close this issue

2026-07-06 00:09:40 -05:00

Fix MCP registration and naming for Jenkins/GlitchTip servers (Issue #151) #226

sysadmin referenced this issue

2026-07-06 00:16:23 -05:00

Fix MCP registration and naming for Jenkins/GlitchTip servers (Issue #151) #226

sysadmin closed this issue

2026-07-06 00:20:15 -05:00

sysadmin referenced this issue from a commit

2026-07-06 00:20:17 -05:00

Merge pull request 'Fix MCP registration and naming for Jenkins/GlitchTip servers (Issue #151)' (#226) from feat/issue-151-mcp-registration-naming into master

jcwalker3 referenced this issue