Tool Boundaries

This document defines the strict boundaries between the different MCP server packages within the monorepo.

1. Architectural Philosophy

One MCP Server per Trust Boundary: While the packages share a monorepo, their runtime services must remain entirely separate. There is no single "everything" server.

gitea-mcp: Restricted to source-control and work-item capabilities (issues, PRs, comments). This package must not have Jenkins or Ops credentials, nor can it execute deploy operations.
jenkins-mcp: Focused on CI/CD capabilities. This package must not have Ops credentials unless explicitly configured for a specific, isolated pipeline later.
ops-mcp: Dedicated to live environment and host checks. In its initial state, this package starts as strictly read-only (e.g., health checks, status checks, log reading).