What problem does it solve? Setting up IDE MCP clients (Claude Code, Cursor, VS Code, GitHub Copilot) against PingOne's hosted Remote MCP Server involves OAuth app configuration, redirect URI rules, role-based tool visibility, and subtle failure modes that are hard to diagnose without a guided procedure. ## Core Features & Use Cases - Worker App Setup: Step-by-step creation of a public OAuth Worker application in the PingOne admin console with Authorization Code + PKCE (S256) and the correct redirect URIs for port 7474 callbacks. - Client Connection Guides: Concrete configuration for Claude Code (claude mcp add), Cursor (mcp.json), and VS Code/Copilot against https://mcp.pingone.com/admin/{envId}/mcp. - Troubleshooting Matrix: Ordered diagnostics for common failures such as wrong app type (NATIVE_APP vs WORKER), stale cached tokens, silent SSO hijack, missing feature flags, and role-based tool visibility. - Use Case: A developer sees only ~6 PingOne tools with every call denied; the skill identifies the app type as the root cause and walks through recreating it as a Worker app and clearing the cached token. ## Quick Start Connect my Claude Code client to the PingOne Remote MCP Server using my environment ID and Worker app client ID.