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

docs: Document MCP security model and trust boundaries for #52

Browse Source
This commit is contained in:
Jason Walker
2026-07-01 03:46:45 -04:00
parent 989856a007
commit 509ff7574a
4 changed files with 44 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/credential-isolation.md
+9
View File
@@ -0,0 +1,9 @@
# Credential Isolation
This document describes how credentials and sensitive environment variables are handled within the MCP tools monorepo.
## Separate Credentials
Even though multiple MCP servers share the same monorepo, they **must** have separate credentials and runtimes.
- **No Shared Environments**: Each MCP server (`gitea-mcp`, `jenkins-mcp`, `ops-mcp`, etc.) must be instantiated as an independent service with its own dedicated `.env` configuration file.
- **Strict Isolation**: A server will only have access to the credentials required for its specific trust boundary. For instance, `gitea-mcp` has no access to Jenkins or Ops authentication tokens.