Releasesby GlyphRender MCP now supports OAuth for Claude Code, Codex, and Cursor
The Render MCP server now supports OAuth-based authentication for Claude Code, Codex, and Cursor: The MCP server continues to support API key authentication for other applications and non-interactive environments, such as CI/CD. See setup instructions for each supported tool in the documentation .
Also shipped Jul 22, 2026Render in July 2026 →
External OAuth and configurable scopes for MCP servers (General availability)
Two new hierarchical parameters let you bind MCP servers to your organization’s existing identity provider (IdP) and control which OAuth scopes MCP clients discover. This enables MCP clients such as Claude, Cursor, and ChatGPT to authenticate against your corporate IdP instead of Snowflake OAuth.
Variant and Variant shredding are now generally available
Variant is now generally available . Variant is a flexible data type for semi-structured data that delivers structured-like query performance through Variant shredding, which is also generally available.
Transactions are now generally available
Transactions that write to Unity Catalog managed Delta tables are now generally available. Group multiple SQL statements across one or more tables into a single atomic transaction using BEGIN ATOMIC ... END; or BEGIN TRANSACTION; ... COMMIT; syntax. All changes succeed together or roll back together, ensuring data consistency across your operations.
Email notifications for expiring service principal tokens are now generally available
Databricks now automatically sends an email notification when a service principal token is set to expire within seven days. Because service principals don't have their own mailboxes, Databricks sends these notifications to workspace admins.
Role-based access control (RBAC) is in Public Preview
Role-based access control (RBAC) is now in Public Preview. RBAC lets users assume a role in Databricks using only that role's permissions for the duration of the session instead of their own accumulated permissions. This enables exclusive access.
Governance Hub is in Beta
Governance Hub is in Beta . Governance Hub is a centralized, account-level UI in the account console for monitoring governance across your Databricks account. It provides a unified view of data health and coverage, AI usage and spend, and cost drivers, with prioritized insights and recommendations. All views respect existing permissions.
More from RenderEvery Render release →
Managed OIDC now supports Anthropic and OpenAI
Render’s managed OpenID Connect (OIDC) authentication now supports Anthropic and OpenAI in addition to AWS. Render services can authenticate to both providers without storing long-lived API keys. Render instead issues short-lived identity tokens for each service and automatically rotates them as needed.
Trigger service deploys with the Render MCP server
The Render MCP server now includes a trigger_deploy tool that enables you (and your agents) to kick off a new deploy of an existing service. This can be helpful for retrying a deploy after a transient failure or forcing a clean rebuild by clearing the build cache.
Default Bun version updated to 1.3.14
Newly created services now use Bun 1.3.14 by default. You can always specify a different version . Existing services keep their original default Bun version to prevent breaking changes.
Reduced median service build time by 40% (all runtimes)
Render service builds now run on nodes with faster CPU and disk. These improvements have reduced the median build time for a Render service by 40%, with this reduction reflected across all runtimes: Before this rollout (week of July 13), median build time was 38 seconds, consistent with prior weeks.
New compute plans, and new IDs for existing plans
We're introducing new compute plans for Render services, including memory-optimized plans with higher ratios of RAM to CPU and a new 12-CPU tier for web services, private services, and background workers. To support the expanded catalog, we're also changing compute plan IDs to a spec-based format that includes the relevant specs.
Introduced the Flex compute plan for Render Workflows
Render Workflows uses a new default compute plan for task runs: flex . The flex compute plan provides up to 1 CPU and 4 GB of RAM. Task runs on flex are billed only for the CPU and RAM they actually use, resulting in significantly lower costs for computationally inexpensive runs.
Added usage telemetry to the Render CLI
The Render CLI now automatically collects usage telemetry to help us understand common use cases and improve user experience. Telemetry is enabled by default in version 2.26.0 or later.
See your service's deploys on a new page
Services now have a new Deploys page in the Render Dashboard. The Deploys page features: Your service's deploy history, without a date cutoff. A Live badge indicating the current deploy. Status of in-progress deploys. A banner flagging when auto-deploys are disabled.