Build with AI

PingOne Remote MCP Server overview (early access)

The PingOne Remote MCP Server is a PingOne-hosted service that lets artificial intelligence (AI) clients connect to PingOne through a single remote Model Context Protocol (MCP) endpoint. The PingOne Remote MCP Server doesn’t require you to install or run a local MCP server yourself.

The PingOne Remote MCP Server is currently an Early Access feature.

After configuring a supported client, users authenticate through PingOne with OAuth 2.0 and administrators can securely use MCP tools to administer PingOne.

What you can do

The PingOne Remote MCP Server uses a dedicated PingOne MCP Server platform application. This centralizes configuration and ensures a consistent connection model across supported MCP clients.

  • Connect supported AI clients, such as Claude Desktop, VS Code, Cursor, and OpenAI Codex CLI, to PingOne through a single remote server endpoint.

  • Sign on securely through PingOne using OAuth 2.0 instead of managing local server credentials on each machine.

  • Use MCP tools to work with PingOne administrative capabilities from your AI client, rather than depending only on the UI.

Example prompts

Category Example prompts

Find applications

"List the applications in my PingOne environment" — review existing application configuration before making changes.

Create an application

"Create a new OIDC web application named Customer Portal" — add a new PingOne application through MCP tools.

Update an application

"Update my application to add a new redirect URI" — change application settings without manually editing them in the UI.

Manage users

"Find user jamie@example.com and update their mobile number" — look up a user and change profile attributes.

Password or multi-factor authentication (MFA) help

"Enable MFA for this user" — complete common user security and access tasks.

Investigate audit logs

"Investigate audit logs for suspicious activity" — jamie@example.com had trouble signing on this afternoon. What happened?

Key features

  • Hosted, centrally managed, and automatically updated by PingOne, so you don’t need to install or run a local MCP server.

  • Access to standards-based MCP tools for PingOne administrative tasks.

  • Differentiated audit trail for human administrators versus MCP client actions.

  • Requires authentication using an PingOne Administrators Security Policy for secure access.

  • Supports headless administration through a unified entry point across supported PingOne services.