pingone-mcp

Reads and updates PingOne resources via the hosted MCP server with Management API fallback.

1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/curtismu7/AI-DEMO2 --skill pingone-mcp-curtismu7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pingone-mcp
Source: https://github.com/curtismu7/AI-DEMO2/tree/main/pingone/pingone-mcp
Command: npx skills add https://github.com/curtismu7/AI-DEMO2 --skill pingone-mcp-curtismu7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developers working with PingOne need a consistent way to read and update admin-plane resources (applications, populations, users, DaVinci flows, environment config) without guessing which endpoint or authentication method to use, and without confusing the hosted admin MCP server with data-plane MCP servers. ## Core Features & Use Cases - MCP-first routing rules: Encodes when to use the hosted PingOne MCP tools versus falling back to the direct Management API (e.g., createEnvironment, resource/scope CRUD, application grants). - Per-consumer authentication guidance: Documents how Claude Code, Cursor, the BFF runtime, and smoke scripts each authenticate to the MCP endpoint. - Health checking: Provides a smoke script (npm run smoke:pingone-mcp) that mints a worker token and verifies the live tool count. - Use Case: While developing a banking demo, you need to list applications in a PingOne environment. The Skill tells you to call the hosted MCP listApplications tool with camelCase parameters, and to fall back to the REST Management API if the MCP call fails. ## Quick Start Ask the agent to list the applications in your PingOne environment using the hosted MCP server with credentials from demo_api_server/.env.

Frequently Asked Questions about pingone-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I read or update PingOne applications and users during development?▼

Use the hosted PingOne MCP server at https://api.pingone.{region}/v1/environments/{envId}/mcp with tools like listApplications and getUser. Parameters are camelCase, and the environment ID and region come from demo_api_server/.env.

When should I use the PingOne Management API instead of the MCP server?▼

Use the direct Management API for createEnvironment, resource server and scope CRUD, and application grants, since these are not exposed via MCP. Also fall back to the Management API on any MCP failure such as 5xx errors, missing tools, or auth errors.

How does each consumer authenticate to the PingOne MCP server?▼

Claude Code uses interactive OAuth via .air/mcp.json, Cursor uses a hosted HTTP MCP entry with a static OAuth client ID, and the BFF and smoke scripts use a worker client_credentials Bearer token. There is no Basic auth on the MCP endpoint itself.

Why does the PingOne MCP tools/list return very few tools?▼

A small tool list means the worker app lost admin roles in the target environment; a healthy baseline is about 67 tools. Check the pingOneWorkerPreflight verdicts in the BFF startup logs to diagnose missing roles.

How do I verify the PingOne MCP connection is healthy?▼

Run npm run smoke:pingone-mcp, which mints a worker token and calls tools/list using credentials from demo_api_server/.env. Success prints the live tool count; the check is deliberately not run in CI.