Okta Cross App Access and tool approvals
Mintive and Okta partner on Cross App Access
Static API keys for agents are hard to scope and harder to revoke. Agents that connect through the Okta identity provider can now get a short-lived access token for the underlying app, using the policies you already run and leaving a revocable audit trail instead of static API keys.
This is part of the MCP spec's Enterprise-managed Auth, and it is available for Mintive enterprise organizations. See Cross App Access.
Docs: Cross App Access
Hold new catalog tools until an admin approves them
Third-party MCP servers can change their tool list at any time. You can now set an organization-level default that keeps any newly added tool off until an admin turns it on, so you decide what users can reach across every server.

Passthrough headers for remote MCPs
Some upstream tools key off your own auth headers, which a gateway would normally strip. Remote MCP gateway admins can now allowlist HTTP headers to pass from the client through to underlying servers, so those tools keep working.
Docs: Pass-through headers
Also in this release
Customize the MCP access-request prompt
The message users see when requesting tool access is now editable in the gateway approval settings. Set ticket-number requirements, what context to include, and where the request routes.
Minty help chat
In-app support now runs on our own chat widget with Minty built in.
Direct IdP redirect on SSO login
Organizations with SSO now go straight to their identity provider at login, removing an interstitial step.
Inline access-grant editor
The VMCP access-policy tab now edits grants inline, so you add or remove them without leaving the page.
Configurable agent identity email
Each agent bundle can forward a specific email identity to underlying MCP servers, useful when downstream tools check caller identity for access control.