Nutanix Prism Central

Name: Nutanix Prism Central
Author: wyre-technology

作者：wyre-technology版本 1.0.0i★ –i在你的电脑上运行

注册名称io.github.wyre-technology/nutanix-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： PORT, IDLE_EVICT_MS, SPAWN_TIMEOUT_MS

你需要

Docker已安装 Docker

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "nutanix": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "PORT",
        "-e",
        "IDLE_EVICT_MS",
        "-e",
        "SPAWN_TIMEOUT_MS",
        "ghcr.io/wyre-technology/nutanix-mcp:v1.0.0"
      ],
      "env": {
        "PORT": "your-value",
        "IDLE_EVICT_MS": "your-value",
        "SPAWN_TIMEOUT_MS": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add nutanix --env PORT=your-value --env IDLE_EVICT_MS=your-value --env SPAWN_TIMEOUT_MS=your-value -- docker run -i --rm -e PORT -e IDLE_EVICT_MS -e SPAWN_TIMEOUT_MS ghcr.io/wyre-technology/nutanix-mcp:v1.0.0

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "nutanix": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "PORT",
        "-e",
        "IDLE_EVICT_MS",
        "-e",
        "SPAWN_TIMEOUT_MS",
        "ghcr.io/wyre-technology/nutanix-mcp:v1.0.0"
      ],
      "env": {
        "PORT": "your-value",
        "IDLE_EVICT_MS": "your-value",
        "SPAWN_TIMEOUT_MS": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "nutanix": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "PORT",
        "-e",
        "IDLE_EVICT_MS",
        "-e",
        "SPAWN_TIMEOUT_MS",
        "ghcr.io/wyre-technology/nutanix-mcp:v1.0.0"
      ],
      "env": {
        "PORT": "your-value",
        "IDLE_EVICT_MS": "your-value",
        "SPAWN_TIMEOUT_MS": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

PORT env
Public listen port for the bridge (POST /mcp, GET /health)
IDLE_EVICT_MS env
Idle tenant timeout before an upstream child is evicted (ms)
SPAWN_TIMEOUT_MS env
How long to wait for a spawned child to answer the MCP handshake (ms)

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 wyre-technology 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 18444 个服务器的 0%
发布到注册中心的时间比此分类中其他 18444 个服务器的 21% 更新
基础检查结果等于或优于此分类中其他 18444 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Nutanix Prism Central 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.0.0）于3个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Egovframe Scaffold MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

作者：formulahendry起步阶段↓ 66/周★ 44014个月前更新

在你的电脑上运行

安装

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

作者：desktop-commander正在增长★ 2113天前更新

在云端运行✓ desktopcommander.app

安装

Egovframe Scaffold MCP

eGovFrame (전자정부 표준프레임워크) projects: templates, components, CRUD, build, 5.x migration, dependencies

作者：EricSeokgon起步阶段↓ 1440/周今天更新

在你的电脑上运行

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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:

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.
401-gates every /mcp request on the X-Nutanix-Pc-* credential headers (below). Those headers are the only Prism Central credential source.
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.
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.
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.

Header	Child env var	Required	Notes
`X-Nutanix-Pc-Host`	`PC_HOST`	yes	Prism Central IP or FQDN
`X-Nutanix-Pc-Port`	`PC_PORT`	no	Upstream default `9440`. Upstream quirk: any port other than 9440 makes it use `http://`, not `https://`
`X-Nutanix-Pc-Username`	`PC_USERNAME`	with password	Basic auth pair
`X-Nutanix-Pc-Password`	`PC_PASSWORD`	with username	Basic auth pair
`X-Nutanix-Pc-Api-Key`	`PC_API_KEY`	alternative	Sent to PC as the `X-ntnx-api-key` request header; upstream prefers it over basic auth when both are set
`X-Nutanix-Pc-Insecure`	`PC_INSECURE`	no	`"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 var	Default	Notes
`CONDUIT_S2S_SECRET`	empty (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_DEV`	unset	Set 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_HOST`	`0.0.0.0` when a real secret is set	Bind 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.
`PORT`	`8080`	Public listen port (`MCP_HTTP_PORT` is the fallback).
`NUTANIX_MCP_DIR`	`/opt/nutanix-mcp`	Upstream checkout (venv + artifacts).
`NUTANIX_MCP_BIN`	`$NUTANIX_MCP_DIR/.venv/bin/nutanix-mcp`	Upstream console script the bridge spawns.
`ARTIFACTS_DIR`	`$NUTANIX_MCP_DIR/artifacts`	Baked YAML API-spec artifacts.
`CHILD_LOG_DIR`	`/tmp/nutanix-mcp-logs`	Writable dir for upstream per-process log files.
`IDLE_EVICT_MS`	`3600000`	Idle tenant timeout (60 min).
`SPAWN_TIMEOUT_MS`	`60000`	Max 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= ,v1= , where the hex is HMAC-SHA256 of the literal string t= 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.

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

# 1. Get the upstream at the pinned tag with a venv + artifacts

git clone --branch v0.8 --depth 1 https://github.com/nutanix/ntnx-api-mcp-server ../ntnx-api-mcp-server cd ../ntnx-api-mcp-server uv venv .venv && uv pip install . ARTIFACTS_DIR=$PWD/artifacts .venv/bin/nutanix-mcp init # no PC creds needed cd -

2. Build and run the bridge against it

npm 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.

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:

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:

Review the upstream diff between the current pin and the new tag (tool surface, credential handling, READ_ONLY_MODE semantics).
Change NUTANIX_MCP_REF in the Dockerfile and the tag in this README.
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).
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.