nutanix-mcp-server

Created By
takanorisuzukia year ago
Nutanix Prism Central と連携してクラスタ・仮想マシン情報を取得する MCP (Model Context Protocol) サーバーの FastAPI 実装
Overview

what is Nutanix MCP Server?

Nutanix MCP Server is a FastAPI implementation that retrieves cluster and virtual machine information by integrating with Nutanix Prism Central using the Model Context Protocol (MCP).

how to use Nutanix MCP Server?

To use the Nutanix MCP Server, clone the repository, set up the environment, configure the .env file with your Nutanix Prism Central credentials, and start the server using Uvicorn.

key features of Nutanix MCP Server?

  • FastAPI-based REST API for retrieving Nutanix cluster and VM information.
  • Integration with Nutanix Prism Central for real-time data access.
  • Swagger UI for easy API documentation and testing.

use cases of Nutanix MCP Server?

  1. Monitoring Nutanix cluster health and performance.
  2. Retrieving detailed information about virtual machines in a Nutanix environment.
  3. Integrating with Dify for natural language queries about cluster and VM data.

FAQ from Nutanix MCP Server?

  • What is the minimum environment required to run the server?

The server can run on macOS, Linux, or Windows with Python 3.12 or higher.

  • Can I use this in a production environment?

This is a prototype and should not be used in production environments.

  • How do I access the API documentation?

You can access the API documentation at http://127.0.0.1:8000/docs after starting the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
takanorisuzuki
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago