What problem does it solve? Setting up PingOne MCP in an IDE fails frequently due to wrong redirect URIs, missing openid scope grants, non-WORKER app types, and broken hosted HTTP endpoints, leaving users with cryptic errors like net::ERR_FAILED or ACCESS_FAILED. ## Core Features & Use Cases - IDE-specific MCP installation: Asks whether the user runs Cursor or VS Code, then writes the correct stdio config to ~/.cursor/mcp.json or .vscode/mcp.json with matching redirect URIs. - PingOne Worker app creation: Creates MCP OAuth Workers (AUTHORIZATION_CODE + PKCE) or Management API Workers (client_credentials) via the PingOne Management API, including openid scope grants and role assignments. - Failure diagnosis: Maps symptoms like Invalid redirect URI, At least one scope must be granted, and post-login 403 to concrete fixes. - Use Case: A developer asks to set up PingOne MCP in VS Code; the skill creates a WORKER app with the 127.0.0.1:7464 callback, grants openid/profile/email scopes, writes .vscode/mcp.json, and verifies list_applications returns without 403. ## Quick Start Ask the assistant to install PingOne MCP and tell it whether you use Cursor or VS Code so it can create the Worker app and write the correct MCP config.