Topic starter
07/06/2026 8:09 pm
TL;DR: MCP Apps let developers render interactive app experiences directly inside Claude and ChatGPT, turning AI assistants into a new distribution layer and collapsing context-switching friction for users, according to WorkOS. The shift changes go-to-market, interface design, and approval logic for teams that govern human, NHI, and agentic access.
Editorial analysis by NHI Mgmt Group, based on content published by WorkOS: “The shift from apps with AI to AI with apps: Why your next app should live inside Claude”.
Key questions
Q: What breaks when apps are embedded inside Claude and ChatGPT without new access controls?
A: The old boundary between app discovery and app execution breaks down.
Q: Why do AI coding tools increase governance risk for IAM and NHI teams?
A: AI coding tools increase governance risk because they obscure who created the logic, which identities executed it, and whether the resulting automation has the right access scope.
Q: How should security teams implement approval controls for AI assistants?
A: Place the approval control at the point of execution, not just at login or onboarding.
Practitioner guidance
- Define assistant-native approval boundaries Document which actions may be triggered inside Claude or ChatGPT without an additional approval step, and require explicit sign-off for anything that changes records, sends messages, or moves data across systems.
- Inventory delegated credentials behind MCP workflows Map the service accounts, tokens, and API keys that power each assistant-integrated app, then verify that the scope of each credential matches the exact conversational workflow it serves.
- Separate discovery from execution permissions Make sure an app can be surfaced by the assistant without automatically inheriting write access, administrative scope, or cross-system action rights beyond the intended task.
Bottom line: MCP Apps turn Claude and ChatGPT into execution surfaces, so identity governance has to move closer to the assistant conversation itself.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 3 days ago by NHI Mgmt Group
07/06/2026 9:57 pm
Assistant-embedded apps create a new identity distribution layer, not just a new UI pattern. When Claude or ChatGPT becomes the place where an app is discovered and used, identity controls move from the login page to the conversation boundary. That changes how practitioners think about consent, session trust, and who is actually initiating the action. The implication is that governance has to follow the assistant surface, not stop at the service boundary.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: What is the difference between MCP access and ordinary app integration?
A: MCP connects an agent to tools and data sources in a way that can support autonomous action, so it must be treated as a privileged integration channel rather than a simple API connection. Ordinary app integration is usually static and user-scoped. MCP becomes riskier when it inherits broad scopes, writes back to systems, or can chain actions across services.
👉 Read our full editorial: MCP Apps shift app distribution inside Claude and ChatGPT
This post was modified 3 days ago by NHI Mgmt Group