- 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.
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:
- Discoverable Identity Tools: Find PingOne skills and its remote MCP connection in Antigravity’s marketplace, and connect supported clients to hosted PingOne or AIC tools without maintaining a local MCP server. Your team still configures and authorizes access.
- Deeper Mobile Customization: Control identity screens and interactions in shared React Native application code. Use DaVinci flows or AIC journeys for the identity steps behind them, with a supported module rather than a custom bridge to each platform’s native SDK.
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: