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

Closed
opened 2026-07-05 01:56:37 -05:00 by jcwalker3 · 1 comment
Owner

Purpose

Fix MCP registration and naming for Jenkins/GlitchTip servers to ensure discoverability by LLM clients.

Acceptance criteria

  • Add explicit entry points and client-registration docs.
  • Decide whether to keep jenkins-mcp / glitchtip-mcp names or deliberately introduce jenkins-readonly / glitchtip-readonly.
  • Add discoverability tests proving tools are visible to clients.

Related to parent integrations discussion.

## Purpose Fix MCP registration and naming for Jenkins/GlitchTip servers to ensure discoverability by LLM clients. ## Acceptance criteria * Add explicit entry points and client-registration docs. * Decide whether to keep `jenkins-mcp` / `glitchtip-mcp` names or deliberately introduce `jenkins-readonly` / `glitchtip-readonly`. * Add discoverability tests proving tools are visible to clients. Related to parent integrations discussion.
Author
Owner

Claimed for author implementation. Branch: feat/issue-146-fix-mcp-registration-naming.

Refs #146

Claimed for author implementation. Branch: `feat/issue-146-fix-mcp-registration-naming`. Refs #146
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#146