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

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

New Issue
Open
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

Extend the existing Gitea execution profile model (see #12, #19, docs/gitea-execution-profiles.md, docs/credential-isolation.md) into a generic per-service MCP profile/config model suitable for Jenkins and GlitchTip.

The model should preserve credential isolation:

  • Gitea tools hold only Gitea credentials.
  • Jenkins tools hold only Jenkins credentials.
  • GlitchTip tools hold only GlitchTip credentials.
  • Orchestrators coordinate without becoming an all-powerful credentials holder.

Acceptance criteria

  • Defines profile schema for Jenkins and GlitchTip.
  • Defines allowed_operations per service.
  • Missing profile or credentials fail closed.
  • Tokens are never printed or logged.
  • Environment overrides are documented.
  • Audit identity/source is included in mutating actions.
  • Existing Gitea profile behavior remains backward compatible.
Extend the existing Gitea execution profile model (see #12, #19, `docs/gitea-execution-profiles.md`, `docs/credential-isolation.md`) into a generic per-service MCP profile/config model suitable for Jenkins and GlitchTip. The model should preserve credential isolation: * Gitea tools hold only Gitea credentials. * Jenkins tools hold only Jenkins credentials. * GlitchTip tools hold only GlitchTip credentials. * Orchestrators coordinate without becoming an all-powerful credentials holder. ## Acceptance criteria * Defines profile schema for Jenkins and GlitchTip. * Defines `allowed_operations` per service. * Missing profile or credentials fail closed. * Tokens are never printed or logged. * Environment overrides are documented. * Audit identity/source is included in mutating actions. * Existing Gitea profile behavior remains backward compatible.
jcwalker3 added the mcpsecurityarchitecture labels 2026-07-02 05:46:51 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
architecture
Architecture / structural design
 bug
chore
design
Design / investigation, no implementation
 documentation
Docs / runbooks
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 mcp
MCP server / tooling
 mutating
Mutating action; requires gating
 nice-to-have
portability
Cross-platform / portability
 read-only
Read-only, no mutation
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 roadmap
Roadmap / umbrella issue
 security
Security / trust boundary
 status:in-progress
Issue is being worked on
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 workflow
Cross-tool workflow
No Label architecture mcp security
Milestone
No items
No Milestone
Projects
Clear projects
No project
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
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?