[jcombs-pointblue]

Design note for letting a person's agent do day-to-day administration through the console over MCP. Nothing is built; docs/MCP.md ends with the decisions to take.

• Why the console, not DirXMLDevWeb: administration acts as the person on live data, which the console already handles (roles, scopes, production confirmation, audit). DirXMLDevWeb's MCP stays for development.
• Agent keys with LDAP only: the person signs in, makes a key and types their password again. Calls with the key run on the service account's connection with the RFC 4370 proxied-authorization control, the way single sign-on already works (Ldap.actAs, Engines.openAs). No OSP or OpenID provider is needed, and the key never stands for a password.
• Production: writes from a key become pending changes that a person approves in the console.
• Identity Applications: only where OSP exists. One password grant when the key is made, then refresh tokens, so OSP's oidpInstanceData doesn't fill. The client goes into DirXMLDev core.

🤖 Generated with Claude Code