pingone-mcp-install

Installs PingOne MCP server for Cursor or VS Code and creates PingOne Worker applications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about pingone-mcp-install

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

FAQPage Schema
How do I install PingOne MCP server in VS Code or Cursor?▼

Install the binary with brew install pingone-mcp-server, create a WORKER-type OAuth app with redirect URIs matching your IDE, then write the stdio config to ~/.cursor/mcp.json for Cursor or .vscode/mcp.json for VS Code with your environment ID and client ID.

How do I create a PingOne Worker app for MCP OAuth?▼

POST to /v1/environments/{envId}/applications with type WORKER, grantTypes AUTHORIZATION_CODE and REFRESH_TOKEN, tokenEndpointAuthMethod NONE, and PKCE S256. Then grant the openid, profile, and email scopes via the application's grants endpoint.

Why does PingOne MCP fail with net::ERR_FAILED?▼

This error occurs when the MCP config points to the hosted HTTP endpoint at api.pingone.com, which does not work for IDE Connect. Switch the configuration to stdio mode using the local pingone-mcp-server binary instead.

What redirect URI does VS Code need for PingOne MCP?▼

VS Code requires exactly http://127.0.0.1:7464/callback registered on the Worker application. Cursor needs that URI plus localhost variants, the cursor:// scheme callback, and the cursor.com agents callback.

Why do I get 403 ACCESS_FAILED after PingOne MCP login succeeds?▼

A 403 after successful login means the OAuth client is a NATIVE_APP instead of WORKER, or the signed-in user lacks admin roles. Recreate the app as type WORKER and grant the user Environment Admin, plus DaVinci Admin if using DaVinci tools.

When should I not use this install skill?▼

Do not use it for calling PingOne MCP tools after a healthy install, for banking data-plane MCP servers, or for general Management API user CRUD. Those belong to the pingone-mcp and pingone-api-calls skills respectively.