PingOne MCP Server

The PingOne MCP (Model Context Protocol) server enables AI assistants to review and manage PingOne tenants by integrating the PingOne management API to AI assistant conversations.

[!CAUTION] Preview Software Notice

This is preview software provided AS IS with no warranties of any kind.

• Functionality, features, and APIs are subject to change at any time without prior notice
• Use against production environments or mission-critical workloads is not advised
• Limited support is available during the public preview phase — please report bugs and provide feedback via the GitHub issue tracker

Your use of this software constitutes acceptance of these terms.

[!CAUTION] Security Notice

Depending on the requests made to the MCP server, tenant configuration or data may be returned. Do not use the MCP server with untrusted MCP clients, agent code or LLM inference and ensure least privilege principles are followed when granting role permissions to MCP server users.

[!WARNING] Review Generated Configuration

Configuration can be generated dynamically using LLM and user feedback represented dynamically back to agents/conversations. Be sure to review generated configuration before promoting to production environments, or those serving live identity/access requests.

Features

• Administer your PingOne environment using natural language - Interact with PingOne from whichever AI IDE or MCP client tool you use daily.

• Secure authentication - Supports OAuth 2.0 PKCE flow for local deployment and Device Code Flow for containerized deployment. All actions are user-based and auditable. Tokens stored securely in OS keychain (local) or ephemerally (Docker).

• Environment, application and population operations - Provides tool integrations to create, update and analyze configurations for tenant activities.

Use Cases

This MCP server is designed to help developers integrate PingOne capabilities into their applications, while also helping tenant administrators monitor and troubleshoot issues. Common use cases include:

• Accelerate application development
• Generate sample applications
• Monitor tenants and environment configuration

Have you got an interesting use case or project you'd like to share with the community? We'd love to hear about it on the PingOne Community pages!

Getting Started

The PingOne MCP server may be run as a Docker container or as a binary distribution executable.

[!IMPORTANT] Docker requires MCP client URL mode elicitation support

The Docker method can only be used with MCP clients that support URL mode elicitation (introduced in the 2025-11-25 MCP specification). This capability is essential for securely providing the authorization URL to the user during device mode authentication, ensuring the URL is only presented to the human user and not presented to be processed by the AI agent.

To use the Docker container method, see the Docker Usage Instructions.

The following instructions in this readm

... View full README on GitHub