A Model Context Protocol (MCP) server that provides AI assistants with seamless access to PingOne's DaVinci identity orchestration platform resources. This server enables AI models to interact with DaVinci flows, applications, connectors, variables, and forms through a standardized interface.
[!WARNING]
SECURITY & LEAST PRIVILEGE: This server grants an AI model significant access to your DaVinci environment configuration. All data returned from tools may be sent to the LLM provider.
A Model Context Protocol (MCP) server for PingOne DaVinci
2026-11-16
स्टार
—
टूल
—
अपटाइम
—
Use ONLY with trusted MCP clients.
Follow the Principle of Least Privilege: Ensure the authenticating user is assigned a role with the minimum necessary permissions (e.g., DaVinci Admin Read Only).
HUMAN REVIEW REQUIRED: Always review all AI-generated configurations or insights before applying them to a live environment.
Overview
DaVinci is PingOne's no-code identity orchestration platform that allows organizations to build sophisticated identity and access management workflows. This MCP server acts as a bridge between MCP-compatible AI assistants and the DaVinci API, enabling:
Flow Management: List and inspect identity orchestration flows and their versions.
Flow Validation: Check flow configuration errors and deployment readiness.
Returns details of a single DaVinci application by ID.
list_application_flow_policies
Returns all flow policies for a DaVinci application.
describe_application_flow_policy
Returns details of a single flow policy for a DaVinci application.
Flow Tools
Tool
Description
list_flows
Returns a list of all DaVinci flows. Supports attributes to project the response to specific top-level fields. Flow type is derived from the trigger field: no trigger = standard flow; trigger.typeAUTHENTICATION = PingOne flow; trigger.typeAUTHENTICATION + trigger.subtypeCIBA = CIBA flow; trigger.typeSCHEDULE = scheduled flow; trigger.typeBATCH_PROCESSING_SUBFLOW = batch processing subflow. readOnly: true means the flow is read-only.
describe_flow
Returns the complete definition of a DaVinci flow including the full node graph, edges, and settings. Use when auditing or understanding a flow's internal logic. Supports attributes to project the response to specific top-level fields and expand to include related fields inline (e.g. "dvlinterDetails").
list_flow_versions
Returns all versions of a specific DaVinci flow.
describe_flow_version
Returns the complete definition of a specific DaVinci flow version, including the full node graph, edges, settings, and trigger configuration. Supports expand to include related fields inline (e.g. skcomponents).
Connector Tools
Tool
Description
list_connectors
Returns a list of all available DaVinci connector types from the catalog.
describe_connector
Returns the full details of a single DaVinci connector type by ID, including metadata, capabilities, configurable properties, and required credentials.
list_connector_instances
Returns a list of all deployed DaVinci connector instances.
describe_connector_instance
Returns details of a single deployed DaVinci connector instance by ID.
Variable Tools
Tool
Description
list_variables
Returns a list of all DaVinci variables. Supports limit (1–50), cursor for pagination, and a SCIM filter to narrow results.
describe_variable
Returns details of a single DaVinci variable by ID.
Form Tools
Tool
Description
list_forms
Returns a list of all DaVinci forms. Use for discovery and finding form IDs. Use describe_form for field-level details. Supports a SCIM filter on category (eq).
describe_form
Returns full configuration of a single DaVinci form including fields and layout.
Collection: davinci_flow_troubleshooting
Specialized tools for flow validation, execution monitoring, and debugging.
Flow Troubleshooting Tools
Tool
Description
validate_flow
Validates a DaVinci flow configuration using the DVLinter validation engine. Use this tool to check deployment readiness, identify configuration errors and warnings (best-practice violations), and troubleshoot flow issues. Analyzes nodes (connectors and capabilities), connections (connector instances), node properties, and overall structure. Returns validation results including error counts or warning counts, and specific issue descriptions. Error locations: (1) linterError property within each node in graphData.elements.nodes for node specific issues (2) allLinterErrors property in graphData for all flow-level errors and warnings. Zero errors indicates deployment-ready status. This is a read-only operation that does not modify the flow.
list_flow_executions
Returns a list of all executions for a specific DaVinci flow. Use this tool to find execution IDs for troubleshooting, debugging, or monitoring flow executions. Supports limit (max 500) and cursor for pagination and SCIM filter on timestamp (ge, le) with ISO 8601 dates, transactionId (eq) for specific transaction details.
summarize_flow_execution
Returns detailed information about a specific DaVinci flow execution with status (success/failure), timestamps, input/output data, errors with stack traces, and user context. Use this tool to debug failures, summarize flow execution results, analyze execution behavior, verify data transformations, or investigate user-specific issues. Supports limit (max 500) and cursor for pagination and SCIM filter on timestamp (ge, le) with ISO 8601 dates.
Authentication
The server uses OAuth 2.0 Authorization Code flow with PKCE for secure authentication:
Automatic Token Management: Secure token storage using the system keychain (via keytar).
DaVinci Enabled: Ensure the DaVinci service is added to your environment.
In the PingOne Admin Console, navigate to Environments > Your Environment > Services and ensure DaVinci is listed and active.
Worker Application: A PingOne Worker Application in the same environment (see Setup for details).
User Permissions: The authenticating user must be created in the environment if not present, and the user must have an appropriate role, such as DaVinci Admin Read Only.
Setup
1. PingOne Worker Application Setup
The MCP server requires a Worker Application to authenticate with the PingOne API.
The server requires a command to execute and supports several flags to customize its behavior. These should be added to the args array in your MCP client configuration:
Commands
start: Initiates the MCP server (required for normal operation).
Options
--include-collections <list>: Comma-separated list of collection names to include (e.g., davinci_admin, davinci_flow_troubleshooting).
--exclude-collections <list>: Comma-separated list of collection names to exclude.
--include-tools <list>: Comma-separated list of tool names to include.
--exclude-tools <list>: Comma-separated list of tool names to exclude.
--verbose: Enable verbose logging to stderr.
--logout: Trigger a logout flow on startup by clearing stored tokens.
--help: Show the help message.
MCP Configuration Examples
These examples show how to configure claude_desktop_config.json for different scenarios. Change accordingly for other providers
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
सवाल
@ping Identity/davinci कैसे इंस्टॉल करें?
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
क्या @ping Identity/davinci के लिए API key चाहिए?
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
@ping Identity/davinci कौन सा ट्रांसपोर्ट इस्तेमाल करता है?
@ping Identity/davinci stdio पर लोकल चलता है।
@ping Identity/davinci की पिछली जाँच कब हुई थी?
पिछली जाँच 2026-11-16 को हुई। A Model Context Protocol (MCP) server for PingOne DaVinci