Eyebrow Text
BLOG
Title
Ping Extends AI-First Headless Identity with Google Antigravity Plugin
Subtitle
Ping extends AI-first headless identity with a new PingOne plugin for Google Antigravity, remote MCP servers, and React Native orchestration SDK support.
title
Table of Contents
theme
default
centered
false
heading
Key Takeaways
body
  • What’s Available: Ping is extending AI-first headless identity with the Ping Identity PingOne Plugin in Google Antigravity’s new plugin marketplace, packaging skills with the PingOne remote MCP server so agents can configure and monitor PingOne environments. Ping-hosted remote MCP servers for PingOne and PingOne Advanced Identity Cloud (AIC) are in early access, and React Native SDK support spans DaVinci flows and AIC journeys.
  • Who It Helps: Developers using Antigravity, identity teams administering PingOne and AIC through AI clients, and mobile teams delivering identity experiences across iOS and Android.
  • Why It Matters Now: It makes Ping’s AI-first headless tools more discoverable in agent workflows, and gives mobile builders and their AI coding assistants more control over the identity experience through React Native application code.

Expanding AI-First Headless Identity

Ping is extending AI-first headless identity with a new PingOne plugin for Google Antigravity. Now available in Antigravity’s new plugin marketplace, Ping’s plugin combines PingOne skills with the PingOne remote Model Context Protocol (MCP) server so AI agents can configure and monitor PingOne multi-tenant environments from within the Antigravity platform.

Ping’s latest expansion of AI-first headless features also includes Ping-hosted remote MCP servers for PingOne and PingOne Advanced Identity Cloud (AIC), plus React Native SDK support for DaVinci flows and AIC journeys. The plugin and remote MCP servers make Ping’s AI-first headless tools more discoverable; React Native SDK support gives builders and their AI coding assistants more control over the mobile identity experience.

These features build on what Ping introduced in May with AI-first headless identity, which is comprised of agent-ready docs, skills, MCP servers, and a command-line interface (CLI) on top of existing APIs, software development kits (SDKs), and infrastructure-as-code patterns.

AI-first headless identity means identity work can start in the tools builders already use, not only in an admin console.

Why Agentic Engineering Needs Discoverable Identity Tools

In agentic engineering, an AI agent needs more than the ability to write code. It needs product guidance and tools it can find and use in the workflow. When that context sits elsewhere, builders spend time locating documentation, supplying examples, and connecting tools before the agent can help with identity work.

Ping’s AI-first headless identity already gives builders agent-ready documentation, skills, and MCP tools. The Antigravity plugin and Ping-hosted remote MCP servers make that foundation more discoverable: the plugin brings PingOne skills and its remote MCP connection into Antigravity’s marketplace, while remote MCP endpoints expose supported PingOne and AIC tools to agents once the client is configured and authorized. These additions bring more of Ping’s capabilities into the places builders and their agents already work.

Mobile builders and the agents helping them face a different challenge: shaping identity to fit the app without building their own bridges to separate iOS and Android SDKs. React Native SDK support gives them a supported way to customize screens and interactions in shared JavaScript or TypeScript code, while DaVinci flows or AIC journeys define the identity steps behind them.

Bring PingOne into Your Antigravity Workflow

Antigravity is Google’s agentic development platform, allowing anyone to build in the agent-first era. Antigravity’s marketplace gives builders a central place to discover installable packages of agent capabilities. Ping’s plugin brings PingOne-specific skills together with its remote MCP server, so builders can start with a package designed for PingOne instead of assembling those components separately.

The skills give agents product-specific guidance, while the remote MCP server provides the connection for supported administrative actions. Teams still configure and authorize that connection for their PingOne environment.

Read Google’s Antigravity marketplace announcement and explore the Ping Identity PingOne Plugin.

How Ping-Hosted Remote MCP Servers Work

The remote MCP servers for PingOne and PingOne Advanced Identity Cloud (AIC) let teams connect their agents to their Ping SaaS tenants. Access is disabled by default. Once access is enabled, a developer adds the server configuration to a supported AI client, such as Antigravity, Claude Code, or ChatGPT, to configure and monitor their tenant with AI agents.

What Changes from Local to Remote MCP Server

The table below shows how the remote, Ping-hosted option compares with running a server yourself.

What to Compare
Local MCP Server
Remote MCP Server
Where it Runs
Your team provisions and secures the MCP server’s hosting environment, including appropriate sandbox infrastructure and isolation
Ping hosts and manages the server
Setup
You download, install, and configure the server
You prompt a supported AI coding agent or client to connect to Ping’s hosted endpoint
Updates
Each server installation managed by your team
Managed by Ping; no local MCP server installations to maintain
Approval & Oversight
Your team governs local server deployment, configuration, and access
Your team approves endpoint access and applies gateway or network policies where its infrastructure supports them

React Native Support for Ping’s Orchestration Capabilities

AI-first headless identity extends beyond administration: builders also need ways to bring orchestrated identity into the applications they create.

React Native lets teams build iOS and Android applications with shared JavaScript or TypeScript code. The Ping Orchestration SDK connects that shared application layer to native identity capabilities, with product-specific modules for DaVinci flows and AIC journeys.

Your team controls the mobile interface. Your orchestration product defines the identity steps behind it. Instead of maintaining a custom bridge to separate iOS and Android SDKs, teams can use the supported React Native module for their Ping product.

React Native Support for PingOne DaVinci

The October 8 React Native 1.1 release introduced the first public DaVinci module. It brings DaVinci flows to React Native apps through a single TypeScript API backed by the native Android and iOS DaVinci modules.

The app starts a flow, renders the inputs or actions it requires, submits the response, and handles the resulting session. Your React Native components control presentation, while the native modules handle communication with PingOne and sensitive authentication data.

The release includes form rendering and submission, FIDO passkey registration and authentication, social sign-on, PingOne Protect signals, and collectors for flow navigation, polling, and QR codes. Get started with our “Try it out” guide, and for a deeper dive, refer to React Native usage.

React Native Support for PingOne AIC

The June React Native 1.0 release brought support for AIC and PingAM authentication journeys. The Journey module lets React Native apps start and navigate journeys, respond to callbacks, and manage the resulting session.

Its AIC/PingAM capabilities include passkeys, OATH and push-based MFA, device binding, social sign-on, and user self-service. Teams can deliver these experiences through shared application code while the SDK connects to the native implementations underneath.

The AIC React Native sample tutorial shows how to connect an app to an authentication journey and run it on iOS and Android.

Shared Mobile Development, Product-Specific Orchestration

DaVinci teams use flows; AIC teams use journeys. Both have a supported React Native integration path, while their modules, configuration, and available capabilities remain product-specific.

Server-side orchestration can reduce hard-coded identity logic in an app. Changes that use capabilities the app already handles can stay in the orchestration layer; new UI components, native capabilities, or SDK dependencies may still require an app update.

What Builders and Identity Teams Gain

Builders gain easier discovery of Ping tools and more control over mobile identity:

Start Building with Ping’s AI-First Headless Identity

Install the PingOne plugin from the Google Antigravity marketplace:

Connect your AI tools to Ping:

Bring orchestrated identity into your mobile app:

Frequently Asked Questions

Which Ping platform deployment options have remote MCP servers?
Ping hosts remote MCP servers for PingOne and PingOne Advanced Identity Cloud (AIC). PingOne supports administrative tasks including DaVinci flows where enabled; AIC supports tasks including journeys and environment configuration. Available tools and access requirements differ by product.
Does AI-first headless identity replace the admin console?
No, Ping's AI-first headless approach does not replace the admin console. The UI is no longer the gatekeeper but becomes a choice, and the console remains fully supported. You can use the CLI, SDKs, infrastructure as code, or AI agents when they fit, without adopting agents right away.
Which AI coding tools connect to the Ping remote MCP server?
Use a supported MCP client that can connect to the relevant remote endpoint and complete its OAuth 2.0 authentication flow. Check the product documentation for client configuration and compatibility.
Can an AI agent deploy identity changes to production?
AI agents should not make identity changes directly in production. Ping recommends using agents to build and test configurations in development or sandbox environments, then promoting reviewed and validated changes through governed CI/CD pipelines. Deterministic tools such as Ping CLI or Terraform apply the approved changes. Agents can help prepare changes or operate the pipeline, but the pipeline—not the agent—applies them to production. See Managing Production Environments for the recommended governance model.
Are the remote MCP servers available for production use?
The remote MCP servers are in early access. The AIC remote MCP server is currently available only in sandbox environments and requires enablement by Ping Identity Support. Check the PingOne and AIC documentation for current availability and access requirements.
When did React Native support become available for Ping’s Orchestration products?
AIC/PingAM journey support was included in React Native 1.0, publicly released on June 29, 2026. DaVinci flow support was added in React Native 1.1 on October 8, 2026. See the release notes for details.
Is the React Native integration the same for DaVinci and AIC?
Both support cross-platform mobile development, but use different modules: the DaVinci module for DaVinci flows and the Journey module for AIC/PingAM journeys. Support across both products does not mean identical features or interchangeable flows.
title
Build with Ping Identity Using AI
body
Explore AI-first headless identity resources for remote MCP, React Native support for DaVinci, agent skills, and the Ping CLI, and start building identity into your AI-assisted workflows.
Supporting text
primary-link
https://developer.pingidentity.com/build-with-ai/
primary-link-text
Start Building with AI
primary-link-title
Start Building with AI
use-tertiary-arrow-button-style
secondary-link
secondary-link-text
secondary-link-title
use-tertiary-arrow-button-style-2