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.