dxi-mcp-server

Name: dxi-mcp-server
Rating: 62 (1 reviews)
Author: delphix

MCP Server

delphix/dxi-mcp-server

The Delphix DCT MCP Server integrates AI assistants with the Delphix Data Control Tower API, facilitating test data management and virtualization.

3 10No licenseUpdated 2026-08-07

Good

View on GitHub Open source file

Overview

This Model Context Protocol (MCP) server bridges AI clients like Claude, Cursor, and VS Code with Delphix Data Control Tower (DCT). It offers flexible configuration modes including a dynamic OpenAPI-driven mode and role-based persona toolsets, allowing developers and database administrators to manage datasets, environments, compliance jobs, and virtualization workflows directly through natural language instructions.

Capabilities

▸Dynamic API discovery using live OpenAPI specs
▸Persona-based toolset partitioning
▸Built-in confirmation safeguards for destructive operations
▸Cross-platform support with automated startup scripts
▸Retry logic and exponential backoff for robust API interactions

Best for

Provisioning and managing virtual databases (VDBs) through AI assistants, Executing database compliance and masking operations via natural language, Monitoring data virtualization engines and storage insights, Automating continuous data administration workflows

Works with

Claude CodeCursorGitHub CopilotOpenCode

Evoa Score breakdown= Σ (score × weight)

Task usefulness20%88 → +17.6

実タスクにどれだけ役立つか（機能の豊富さ・用途の明確さ）。 — AIによるcapabilities/use-cases解析

Code quality15%90 → +13.5

実装・指示の品質。 — AIによるSKILL.md/README解析

Maintenance15%100 → +15.0

リポジトリがどれだけ活発に保守されているか。 — GitHub 最終push日時の新しさ

Documentation12%29 → +3.5

ドキュメントの充実度・分かりやすさ。 — README/独自要約の情報量

Security15%50 → +7.5

危険・不審な挙動が無いか。 — AIによるセキュリティレビュー

Originality10%85 → +8.5

ありふれたラッパーではない独自性。 — AIによる独自性判定

Popularity8%35 → +2.8

コミュニティの採用度。 — GitHub Stars/Forks（対数スケール）

Compatibility5%100 → +5.0

対応AIエージェントの広さ。 — AIによる対応エージェント判定

Weighted total73.4 / 100

ライセンス不明/制限あり（Red）のSkillは総合スコアに0.85倍の補正を適用します。ランキングはこのScoreのみで決まり、広告で変わりません。算出方法の詳細 →

Security considerations

Requires sensitive API keys and base URLs. Secrets should be handled securely via environment variables rather than hardcoded configuration files. Built-in confirmation mechanisms mitigate the risk of executing destructive database commands.