2026-10-31 — MCP, plugins, and Workspace consolidation
The GWAS Agency plan separates three organizational spaces: CRH VC (C), gwasai (G), and zwasai (Z).
Decision
Build organization-owned MCP endpoints by security boundary rather than by AI model vendor. CRH VC manages principal operations; GWAS Agency provides tools and resource catalogs; ZWAS independently verifies releases.
Proposed endpoints
https://mcp.crh.vc/mcp
https://mcp.gwasai.com/mcp
https://mcp.zwasai.com/mcp (proposal)
Google Workspace
Consider making gwasai.com the primary identity of the existing gwas.ai Workspace account, only after inventories of mail, users, aliases, billing and OAuth dependencies.
Working implementation
A live HTTPS HTML surface is available at CRH VC. Google Docs and Sheets are reference sources, not currently public live databases. Private provider mutations require authentication.
Execution sequence
1. Establish public documentation and role views.
2. Deploy a read-only MCP server with official SDK.
3. Implement OAuth and explicit C/G/Z authorization.
4. Connect GitHub, Cloudflare, Porkbun and Workspace using scoped permissions.
5. Verify with Z and approve production operations with C.