Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 87 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

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

New Issue
Closed
opened 2026-07-02 05:46:28 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-02 05:46:28 -05:00
Owner
Copy Link
Copy Source

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

Extend the existing Gitea execution-profile model
(docs/gitea-execution-profiles.md) into a generic per-service MCP
profile/config model for Jenkins and GlitchTip.

Must be clear

  • The shared profile/config model is a schema / library, not a shared
    credential pool    .
  • Tokens remain service-local; profiles are per service.
  • allowed_operations are namespaced, e.g. gitea.issue.create,
    jenkins.build.read, glitchtip.event.read.
  • forbidden_operations, if present, override allowed_operations.
  • Orchestrators must not directly hold every service credential.

Acceptance criteria

  • Defines a per-service profile schema (Jenkins, GlitchTip) reusing the Gitea
    field model.
  • Missing profile or credentials fail closed.
  • token_source_name records the source name only, never the value; tokens
    are never printed or logged.
  • Environment overrides documented.
  • Audit identity/source included in mutating actions.
  • Existing Gitea profile behavior remains backward compatible.

Belongs in the common package (per #71). Parent: #75.

_Curated 2026-07-02 to reflect review consensus (issue text only; not started)._ Extend the existing Gitea execution-profile model (`docs/gitea-execution-profiles.md`) into a generic **per-service** MCP profile/config model for Jenkins and GlitchTip. ## Must be clear * The shared profile/config model is a **schema / library**, **not a shared credential pool**. * Tokens remain **service-local**; profiles are **per service**. * `allowed_operations` are **namespaced**, e.g. `gitea.issue.create`, `jenkins.build.read`, `glitchtip.event.read`. * `forbidden_operations`, if present, **override** `allowed_operations`. * Orchestrators **must not** directly hold every service credential. ## Acceptance criteria * Defines a per-service profile schema (Jenkins, GlitchTip) reusing the Gitea field model. * Missing profile or credentials **fail closed**. * `token_source_name` records the source **name only, never the value**; tokens are never printed or logged. * Environment overrides documented. * Audit identity/source included in mutating actions. * Existing Gitea profile behavior remains backward compatible. Belongs in the `common` package (per #71). Parent: #75.
jcwalker3 added the mcpsecurityarchitecture labels 2026-07-02 05:46:51 -05:00
sysadmin added the status:in-progress label 2026-07-02 14:22:17 -05:00
jcwalker3 removed the status:in-progress label 2026-07-02 14:44:37 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
No labels architecture mcp security
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

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