Nutanix Prism Central

io.github.WYRE-AI由 GitHub 帳號 WYRE-AI 發布v1.0.8更新於 Nov 21, 2026

Multitenant Streamable HTTP bridge over Nutanix's official v4 API MCP server (Prism Central).

概覽

AI 產生的概覽

多租戶 HTTP 橋接服務,將 Nutanix 官方 Prism Central v4 API MCP 伺服器重新對外提供,讓助理以唯讀方式使用 Nutanix 基礎架構工具。

可以做什麼
  • 透過 20 個 execute 工具執行各命名空間的 Nutanix 操作(aiops、clustermgmt、networking、storage、vmm、volumes 等)
  • 用四個探索工具查詢 API 操作、其 schema、程式碼範例與所需權限
  • 依租戶列出並呼叫工具,每個租戶的 Prism Central 憑證取自請求標頭
  • 透過 Streamable HTTP 同時服務舊版 initialize 握手用戶端與新版信封格式用戶端
  • 提供免驗證的健康檢查端點
適用情境
適用於多租戶閘道需要把各組織的 Prism Central 憑證經 HTTP 轉送給 Nutanix 官方 MCP 伺服器的情境,或希望讓助理取得唯讀的 Nutanix 清單與探索工具而不授予寫入權限時。
執行需求
以本機容器映像(ghcr.io/wyre-ai/nutanix-mcp)執行,監聽 8080 埠;啟動時必須提供真實的 CONDUIT_S2S_SECRET,每個 /mcp 請求需帶有效的 X-Gateway-S2S 簽章,以及 X-Nutanix-Pc-Host 和 X-Nutanix-Pc-Api-Key,或 X-Nutanix-Pc-Username 與 X-Nutanix-Pc-Password。執行類呼叫需要能連線到 Prism Central;僅列出工具則不需要。
安裝前請注意
Prism Central 憑證(主機、使用者名稱、密碼或 API 金鑰)經由請求標頭傳輸並寫入子行程環境變數;服務間密鑰應足夠強,佔位值會被伺服器拒絕。MCP_ALLOW_INSECURE_DEV=1 會略過簽章檢查,只應在本機回環位址使用。X-Nutanix-Pc-Insecure 會略過 TLS 驗證。上游伺服器為技術預覽版,且此橋接在 v1 為唯讀,寫入操作會被拒絕。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Nutanix Prism Central,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

nutanix-mcp

Multitenant Streamable HTTP bridge over nutanix/ntnx-api-mcp-server — Nutanix's official Prism Central v4 API MCP server — built so the WYRE conduit gateway can forward per-tenant Nutanix credentials as HTTP headers.

Upstream pin: Nutanix's server is a technical preview, pinned here at tag v0.8 (Apache-2.0). See Bumping the upstream pin.

Why

The upstream server is stdio-only (nutanix-mcp serve-stdio is its only serve mode) and reads its Prism Central credentials from environment variables at process startup — single-tenant per process. Our gateway is multi-tenant: every request carries the calling org's credentials as HTTP headers, and the vendor container has to translate those headers into something the upstream understands.

Because the upstream has no HTTP mode to proxy to, this bridge holds an MCP client session over stdio to each tenant child and re-serves it over Streamable HTTP:

  1. Listens on :8080 with POST /mcp and GET /health. Startup requires a real CONDUIT_S2S_SECRET. Every /mcp request must carry a valid X-Gateway-S2S signature of that secret.
  2. 401-gates every /mcp request on the X-Nutanix-Pc-* credential headers (below). Those headers are the only Prism Central credential source.
  3. Lazily spawns one nutanix-mcp serve-stdio child per credential tuple (keyed by a hash), with the tenant's PC_* env vars set, and connects an MCP client to it over stdio.
  4. Serves both protocol eras on /mcp via the v2 SDK's createMcpHandler(factory, { legacy: 'stateless' }) — 2025-era initialize-handshake clients (the conduit gateway today) and modern 2026-07-28 envelope clients. tools/list and tools/call delegate to the tenant's child session.
  5. Evicts idle children after 60 minutes (IDLE_EVICT_MS).

Tool names pass through unchanged: the upstream's 24 tools — 20 {namespace}_execute tools (aiops, clustermgmt, datapolicies, dataprotection, files, iam, licensing, lifecycle, microseg, monitoring, multidomain, networking, objects, opsmgmt, prism, security, storage, tenancy, vmm, volumes) plus 4 discovery tools (listOperations, getOperationSchema, getCodeSample, getOperationPermissions).

Read-only in v1 — deliberate

Every child is spawned with READ_ONLY_MODE=true (also the upstream default): the upstream rejects all non-GET operations before they ever reach Prism Central. v1 of this bridge ships read-only as a deliberate fleet decision. Write support would be a reviewed, versioned change to credentialsToChildEnv() in src/credentials.ts — not a config flip.

Credential contract

The gateway forwards these headers on every /mcp request; the bridge maps them onto the upstream child's environment. conduit's vendor-config must match this table exactly.

HeaderChild env varRequiredNotes
X-Nutanix-Pc-HostPC_HOSTyesPrism Central IP or FQDN
X-Nutanix-Pc-PortPC_PORTnoUpstream default 9440. Upstream quirk: any port other than 9440 makes it use http://, not https://
X-Nutanix-Pc-UsernamePC_USERNAMEwith passwordBasic auth pair
X-Nutanix-Pc-PasswordPC_PASSWORDwith usernameBasic auth pair
X-Nutanix-Pc-Api-KeyPC_API_KEYalternativeSent to PC as the X-ntnx-api-key request header; upstream prefers it over basic auth when both are set
X-Nutanix-Pc-InsecurePC_INSECUREno"true"/"false" — skip TLS verification (default false)

Validity rule: pcHost present AND (apiKey present OR username+password present). Anything else → HTTP 401 with a JSON-RPC error body.

READ_ONLY_MODE=true is additionally forced on every child (see above).

API-spec artifacts (baked at build time)

The upstream builds its tool surface from YAML API-spec artifacts, not from the live PC. nutanix-mcp init downloads them — and without PC credentials it runs in latest_release mode against the public developers.nutanix.com namespace API (no PC access required; verified empirically: 20 namespaces). The Docker build runs init once and bakes the artifacts into the image at /opt/nutanix-mcp/artifacts, shared read-only by all tenant children. Consequences:

  • tools/list and the discovery tools work with no reachable PC — only {namespace}_execute calls touch Prism Central.
  • Artifact versions are the latest public release at image build time, not the tenant PC's exact versions (the upstream's pc_compatible mode would need live PC access at spawn). For the read-only v1 surface this is the right trade: shared artifacts, fast tenant spawns.

Configuration

Copy .env.example. Leave CONDUIT_S2S_SECRET empty in that file and set a real value only in the environment you run.

Env varDefaultNotes
CONDUIT_S2S_SECRETempty (refuses to start)Service-to-service secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder (changeme, secret, replace-me, your-s2s-secret, replace-with-a-real-secret, and the other example values). Generate one with openssl rand -hex 32. Compose will not start without it. The value is never logged.
MCP_ALLOW_INSECURE_DEVunsetSet to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, skips X-Gateway-S2S, and binds 127.0.0.1 only. A non-loopback MCP_HTTP_HOST refuses to start. A known placeholder secret still refuses to start.
MCP_HTTP_HOST0.0.0.0 when a real secret is setBind address. A configured secret honors this value, including when it is unset (historical 0.0.0.0 container bind). The image and Compose set 0.0.0.0 inside the container. With no secret, MCP_ALLOW_INSECURE_DEV=1 binds 127.0.0.1 only.
PORT8080Public listen port (MCP_HTTP_PORT is the fallback).
NUTANIX_MCP_DIR/opt/nutanix-mcpUpstream checkout (venv + artifacts).
NUTANIX_MCP_BIN$NUTANIX_MCP_DIR/.venv/bin/nutanix-mcpUpstream console script the bridge spawns.
ARTIFACTS_DIR$NUTANIX_MCP_DIR/artifactsBaked YAML API-spec artifacts.
CHILD_LOG_DIR/tmp/nutanix-mcp-logsWritable dir for upstream per-process log files.
IDLE_EVICT_MS3600000Idle tenant timeout (60 min).
SPAWN_TIMEOUT_MS60000Max wait for a child to answer the MCP handshake.

/health and /healthz stay unauthenticated and do not read credentials.

HTTP authentication

With CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S. The check is verifyS2sHeader in src/s2s-verify.ts: the header value is t=<unix seconds>,v1=<hex>, where the hex is HMAC-SHA256 of the literal string t=<unix seconds> keyed with CONDUIT_S2S_SECRET (64 lowercase hex characters). The timestamp must be within 300 seconds of the server clock. A missing or invalid header is HTTP 401, before Prism Central credentials are read.

Sign with the same CONDUIT_S2S_SECRET the server process is using. Local development exports that value in the shell; reuse it for this request instead of generating another one.

bash
TS=$(date +%s)SIG=$(printf 't=%s' "$TS" | openssl dgst -sha256 -hmac "$CONDUIT_S2S_SECRET" -hex | awk '{print $NF}')curl -sS http://127.0.0.1:8080/mcp \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -H "X-Gateway-S2S: t=${TS},v1=${SIG}" \  -H 'X-Nutanix-Pc-Host: pc.example.com' \  -H 'X-Nutanix-Pc-Api-Key: fake' \  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"dev","version":"0"}}}'

This bridge is gateway mode. /mcp also requires X-Nutanix-Pc-Host and either X-Nutanix-Pc-Api-Key or both X-Nutanix-Pc-Username and X-Nutanix-Pc-Password. Those headers are the only credential source for that request. PC_* values in the process environment are not used as a fallback.

Local development

bash
# 1. Get the upstream at the pinned tag with a venv + artifactsgit clone --branch v0.8 --depth 1 https://github.com/nutanix/ntnx-api-mcp-server ../ntnx-api-mcp-servercd ../ntnx-api-mcp-serveruv venv .venv && uv pip install .ARTIFACTS_DIR=$PWD/artifacts .venv/bin/nutanix-mcp init   # no PC creds neededcd -
# 2. Build and run the bridge against itnpm ci && npm run build && npm test# HTTP refuses to start until CONDUIT_S2S_SECRET is a real value.# Export it so this shell keeps the same secret for the server, the# signing request above, and the Docker commands below.export CONDUIT_S2S_SECRET="$(openssl rand -hex 32)"NUTANIX_MCP_DIR=../ntnx-api-mcp-server node dist/index.js
# Alternative: local HTTP only, without a service-to-service secret (always# binds 127.0.0.1). A non-loopback MCP_HTTP_HOST makes this exit. The empty# assignment applies only to this process; the exported secret stays in the shell.MCP_ALLOW_INSECURE_DEV=1 CONDUIT_S2S_SECRET= \  NUTANIX_MCP_DIR=../ntnx-api-mcp-server node dist/index.js
# 3. Smoke it (health is unauthenticated; /mcp needs X-Gateway-S2S — see above)curl -s localhost:8080/health

Or build the image (it bakes everything, including a stdio smoke test that fails the build if serve-stdio can't answer tools/list). The image listens on 0.0.0.0 inside the container and still refuses to start without a real CONDUIT_S2S_SECRET. Publish the port on loopback. Prism Central credentials arrive on each request as X-Nutanix-Pc-* headers.

bash
docker build --platform linux/amd64 -t ghcr.io/wyre-ai/nutanix-mcp:dev .# Pass the exported secret. An empty value makes the container exit.docker run --rm \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -p 127.0.0.1:8080:8080 \  ghcr.io/wyre-ai/nutanix-mcp:dev

Compose refuses to start when CONDUIT_S2S_SECRET is unset. The gateway service publishes 127.0.0.1:8080:8080 and does not inject PC_HOST, PC_USERNAME, PC_PASSWORD, PC_API_KEY, or env_file. Use the exported secret so a later signing request matches the container:

bash
docker compose up

Bumping the upstream pin

The upstream is pinned to the reviewed tag v0.8 in the Dockerfile (NUTANIX_MCP_REF) — never main (NSA MCP guidance / fleet security baseline). To bump:

  1. Review the upstream diff between the current pin and the new tag (tool surface, credential handling, READ_ONLY_MODE semantics).
  2. Change NUTANIX_MCP_REF in the Dockerfile and the tag in this README.
  3. docker build locally — the build-time smoke tests assert the venv entrypoint runs and the stdio tool surface still answers (update the expected tool count if namespaces changed).
  4. Land as a feat:/fix: PR so semantic-release cuts a version.

License

Apache-2.0. The bundled ntnx-api-mcp-server is Apache-2.0 by Nutanix.

來源:README.md,提交 8a2e40d

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

3
  1. v1.0.8最新Nov 21, 2026
  2. v1.0.7Oct 14, 2026
  3. v1.0.6Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分