Build with AI

Overview

The AIC Remote MCP Server is an Early Access feature. Refer to the Early Access lifecycle stage. Ping Identity Support must enable it per tenant before you can use it.

To request enablement

Open a support case and provide the following information:

  1. Select PingOne Advanced Identity Cloud as the product family.

  2. Select Tenant Settings as the product.

  3. Select AIC Remote MCP Server as the affected component.

  4. For What Hostname(s) or Tenant ID(s) does this apply to?, list every PingOne Advanced Identity Cloud tenant FQDN that should have the server enabled. For example: https://openam-example.forgeblocks.com/.

  5. Enter Enable AIC Remote MCP as both the issue title and the issue description.

If the support form asks for a product version or sub-component, select the not-applicable option.
Support case screenshots
Support case product
Enablement request: product and tenant details
Support case title and issue description
Enablement request: issue details

The AIC Remote MCP Server is currently available in Rapid (Sandbox) environments only. Support for Development, UAT, Staging, and Production environments is rolling out over the coming weeks.

The AIC Remote MCP Server is a Ping-hosted, HTTP-based Model Context Protocol (MCP) server that lets AI agents interact with your PingOne Advanced Identity Cloud environments over the network. Point your MCP client at a hosted endpoint, sign in with your AIC administrator account through OAuth 2.0, and issue natural-language prompts. MCP exposes AIC’s REST APIs as a set of tools the AI agent can invoke.

Remote versus local

Use the AIC Remote MCP Server for new projects. Future tooling and features are prioritized here over the local stdio AIC MCP Server.

Environments and access

Available tools are gated by the tier of the PingOne Advanced Identity Cloud environment you connect to:

Environment tier Available tools

Sandbox and Development

Full tool set. Read, write, and delete across every category.

UAT, Staging, and Production

Read-only tools, plus the report-authoring tools (createCustomReport, duplicateReport, importReportTemplate).

Refer to Sandbox, Development, and UAT for tenant tier definitions.

Use cases

Category Example prompts

Journey and script management

"Create a new MFA journey", "Add a scripted decision node to the registration flow"

Application and identity provider management

"Create an OIDC app called MyPortal", "Configure a Google OIDC identity provider"

Identity operations

"Find all users with admin in their username", "Update the email for user xyz123"

Themes and branding

"Create a branded theme with our corporate colors", "Set the new theme as default"

Policy and notifications

"Set the minimum password length to 12 for alpha users", "Configure the outbound SMTP provider"

CORS and network policies

"Create a CORS policy allowing https://example.com"

Reporting

"Run the user last login report for the past 30 days", "Create a custom report showing users by city"

Audit and logging

"Show me failed login attempts in the last hour", "Find all logs for transaction abc-123"

ESVs and feature management

"Create a new API key variable", "Enable AI Agents"

Key features

  • Hosted by Ping: Ping deploys and updates the server for each tenant. You don’t install or maintain anything locally.

  • Natural language interaction: Administer PingOne Advanced Identity Cloud from whichever AI client you use daily.

  • Broad tool coverage: Across identity, orchestration, applications, branding, policy, network, observability, and reporting. Refer to Available tools for the full catalog.