docs: Document MCP security model and trust boundaries #8

Merged
jcwalker3 merged 2 commits from feature/52-security-docs into master 2026-07-01 10:40:15 -05:00
3 changed files with 4 additions and 2 deletions
Showing only changes of commit b402de83fe - Show all commits
+2
View File
@@ -2,6 +2,8 @@
This document defines the strict boundaries between the different MCP server packages within the monorepo. This document defines the strict boundaries between the different MCP server packages within the monorepo.
The project is named **MCP Control Plane** and lives in the `mcp-control-plane` repository. It groups the following packages: `common`, `gitea-mcp`, `jenkins-mcp`, `ops-mcp`, and `release-mcp`.
## 1. Architectural Philosophy ## 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. - **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.