ARTICLES
What we found out.
Working notes from building this: where the official documentation stops being enough, what the protocols do rather than claim, and the things that only show up once you run them.
- A disposable MCP server for finding out what a client gives away How to measure what an MCP client actually hands a server it has just met — headers, roots, elicitation, sampling — and the transport details that will make the measurement wrong if you get them subtly right.
- Delegating less than you hold Four manager-to-sub-agent scenarios run against three role-scoped Gmail binaries, including a sub-agent that tries every write it can. What the process boundary actually guarantees, and what it does not.
- Workspace MCP binds identity to the connection, not to the agent An audit of Google's five Workspace MCP servers against the five REST APIs underneath them. Both wrappers reach the same endpoints with the same OAuth scopes; only one of them lets a manager agent hand a sub-agent less access than it holds itself.