Published , by The Key editors.
Descope adds Cross App Access
In short: Descope added Cross App Access support on 1 September 2026. That gives teams building apps and MCP servers a way to accept ID-JAG grants from company identity providers. Descope's Free Forever tier includes its agentic identity hub, which makes testing the flow cheap.
Descope announced Cross App Access support on 1 September 2026. The addition gives teams building applications and MCP servers a way to accept ID-JAG grants from company identity providers. In the documented flow, an application built on Descope accepts the grant and returns an access token for the user.
This places the announcement on the application side of delegated access. Our recommendation is to begin with the relationship between the customer's identity provider and the application accepting the grant. Ask where each party appears in the proposed flow. That is an evaluation question, not a claim about additional integrations or supported providers.
Descope presents itself as an identity provider for AI agents. Its existing material describes tokens limited by scope and duration, along with support for SPIFFE SVIDs, mTLS and DPoP. These are distinct documented elements. We recommend listing the particular element a project needs instead of treating the broader agent identity label as a complete requirement.
The Free Forever tier includes Descope's agentic identity hub. The governance suite is Enterprise only. That suite includes approval, documented purpose and an accountable owner. The separation is important when comparing an initial test with a requirement for governance. Access to the hub should not be described as including the Enterprise governance suite.
Our recommendation is to define a small delegated access test before considering the wider product. Use a stated user, a company identity provider and an application that will accept the grant. Ask whether the proposed flow matches the documented Cross App Access capability. Keep approval and ownership questions visible, but assess them against the separate governance offering.
For readers following the key, Descope appears under delegated access with Cross App Access, a free starting point and workload identity. Those entries describe different reasons to investigate the product. They should not be treated as interchangeable conclusions. We recommend choosing the entry that reflects the actual problem, then checking the relevant documented capabilities and tier.
The announcement does not need to carry every possible agent identity requirement to be useful. Its specific contribution is support for accepting a company identity provider's grant and returning a user access token. Our editorial preference is to retain that narrow description when comparing it with broader platform claims. It makes the product's role easier to discuss without adding unsupported promises.
A useful evaluation record should therefore separate three questions. Does the delegated access flow fit the application? Does the included hub provide the intended starting point? Does the project also require the Enterprise governance suite? These are recommendations for structuring a review. They preserve the distinction between the announced protocol support, the available starting tier and the separately described governance functions.
Sources: Descope adds Cross App Access; Descope Agentic Identity Hub 3, read 2026-11-03