convez.ai
MCP ServerDevOps & InfraestruturaIntermediário
Knuckles-Team

Fan Manager

Knuckles-Team/fan-manager

Controle automático de ventiladores em Dell PowerEdge por temperatura

Ver no GitHub
InicialPluginScore · de 0 a 100

MCP server para controlar a velocidade dos ventiladores em servidores Dell PowerEdge baseado na temperatura da CPU. Funciona localmente via lm-sensors e ipmitool, sem necessidade de token ou URL de serviço. Oferece escalonamento logarítmico configurável com limites de segurança.

Instalação

$npx convez-ai Knuckles-Team/fan-manager

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
2
Forks
0
Acompanhando
1
Saúde
37%
Último commit
há 2 dias
Versão
v2.4.11
Issues abertas
1
Contribuidores
3

Casos de uso

  • Otimizar ruído e consumo de energia em datacenters
  • Monitorar e ajustar temperatura de servidores em tempo real
  • Integrar controle térmico com automação DevOps

Veredito

Ferramenta especializada e bem-arquitetada para ambientes com servidores Dell PowerEdge. Útil para administradores que precisam automatizar controle térmico, mas com escopo limitado ao hardware específico e requisitos de privilégio IPMI local.

README

A tradução para o português deste README ainda está na fila.

Fan Manager

CLI | MCP | Agent

PyPI - Version MCP Server PyPI - Downloads GitHub Repo stars GitHub forks GitHub contributors PyPI - License GitHub GitHub last commit (by committer) GitHub pull requests GitHub closed pull requests GitHub issues GitHub top language GitHub language count GitHub repo size PyPI - Wheel PyPI - Implementation

Version: 1.1.0

Documentation — Installation, deployment, and usage across the CLI and MCP interfaces, plus the integrated A2A agent server, are maintained in the official documentation.


Overview

Fan Manager controls the fan speed of Dell PowerEdge servers based on CPU temperature. It is a local tool: it reads temperatures via lm-sensors (sensors -j) and drives the server's BMC via ipmitool raw commands. It ships as a CLI, a Model Context Protocol (MCP) server, and an integrated A2A agent for the agent-utilities ecosystem.

Because fan control happens against the local host, no service URL or token is required — the connector degrades to a no-op/local config for authentication.


Key Features

  • Temperature-Driven Curve: Logarithmic CPU-temperature-to-fan-speed scaling with configurable min/max bounds and intensity.
  • Consolidated Action-Routed MCP Tools: Two togglable tool modules (temperature, fan-control) minimize token overhead in LLM contexts.
  • Fail-Safe Defaults: On a temperature read error during automatic control, the fans default to maximum.
  • Integrated Agent: Built-in Pydantic AI agent supporting the Agent Control Protocol (ACP) and Web UI (AG-UI).

CLI

The classic continuous service that polls temperature and adjusts the fans:

fan-manager --intensity 5 --cold 50 --warm 80 --slow 5 --fast 100 --poll-rate 24
FlagMeaning
-i, --intensityTemperature power intensity (scales logarithmically, 0-10)
-c, --coldMinimum temperature for fan scaling (°C)
-w, --warmMaximum temperature for fan scaling (°C)
-s, --slowMinimum fan speed (0-100)
-f, --fastMaximum fan speed (0-100)
-p, --poll-rateTemperature poll rate in seconds

Requires ipmitool and lm-sensors installed on the host, and privileges to issue raw IPMI commands to the BMC.


MCP

This server uses dynamic Action-Routed tools to optimize token overhead and maximize IDE compatibility.

Available MCP Tools

Tool ModuleToggle Env VarEnabled by DefaultDescription & Nested Methods
TemperatureTEMPERATURETOOLTrueRead CPU/sensor temperature (CONCEPT:FAN-001). Action-routed methods: get, get_core.
Fan ControlFANCONTROLTOOLTrueControl fan speed via IPMI (CONCEPT:FAN-002). Action-routed methods: set, auto.

Dynamic Tool Selection & Visibility

This MCP server supports dynamic toolset selection and visibility filtering at runtime, so you can restrict the exposed tools and avoid blowing up the LLM's context window. Configure filtering via:

  • CLI Arguments: --tools / --toolsets (and --disabled-tools / --disabled-toolsets).
  • Environment Variables: MCP_ENABLED_TOOLS / MCP_DISABLED_TOOLS, MCP_ENABLED_TAGS / MCP_DISABLED_TAGS.
  • HTTP Headers: x-mcp-enabled-tools / x-mcp-disabled-tags, etc.
  • Query Parameters: ?tools=tool1,tool2 or ?tags=fan-control.

MCP Configuration Examples

stdio Transport (Recommended for local IDEs e.g., Cursor, Claude Desktop)

{
  "mcpServers": {
    "fan-manager": {
      "command": "uvx",
      "args": ["--from", "fan-manager", "fan-manager-mcp"],
      "env": {
        "TEMPERATURETOOL": "True",
        "FANCONTROLTOOL": "True"
      }
    }
  }
}

Streamable-HTTP Transport (Recommended for production deployments)

{
  "mcpServers": {
    "fan-manager": {
      "command": "uvx",
      "args": ["--from", "fan-manager", "fan-manager-mcp"],
      "env": {
        "TRANSPORT": "streamable-http",
        "HOST": "0.0.0.0",
        "PORT": "8000"
      }
    }
  }
}

Connect to a pre-deployed remote or local Streamable-HTTP instance:

{
  "mcpServers": {
    "fan-manager": {
      "url": "http://localhost:8000/fan-manager/mcp"
    }
  }
}

Deploying the Streamable-HTTP server via Docker:

docker run -d \
  --name fan-manager-mcp \
  --privileged \
  -p 8000:8000 \
  -e TRANSPORT=streamable-http \
  -e PORT=8000 \
  knucklessg1/fan-manager:latest

The container needs access to the host's IPMI device (--privileged or --device /dev/ipmi0) to drive the BMC.


Agent

This repository features a fully integrated Pydantic AI Graph Agent. It communicates over the Agent Control Protocol (ACP) and interacts with the Agent Web UI (AG-UI) and Terminal interface.

Running the Agent CLI

fan-manager-agent --provider openai --model-id gpt-4o

Docker Compose Orchestration

The docker/agent.compose.yml configures the Agent, Web UI, and Terminal Interface alongside the MCP server. See docs/deployment.md for the full Compose stack.


Environment Variables

Fan Manager reads the following environment variables (all optional — every one has a safe default). They can be set in the process environment, in a .env file (auto-loaded), or in the MCP client's env block. See .env.example for a ready-to-copy template.

VariableDefaultScopeDescription
HOST0.0.0.0MCP serverBind address for streamable-http/sse transports.
PORT8000MCP serverBind port for streamable-http/sse transports.
TRANSPORTstdioMCP serverTransport: stdio, streamable-http, or sse.
AUTH_TYPEnoneMCP serverAuth strategy passed to the agent-utilities MCP factory (none for this local tool).
FASTMCP_LOG_LEVELINFOMCP serverLog verbosity for the underlying FastMCP server.
TEMPERATURETOOLTrueTool toggleRegister the temperature tool domain (CONCEPT:FAN-001).
FANCONTROLTOOLTrueTool toggleRegister the fan-control tool domain (CONCEPT:FAN-002).
IPMITOOL_PATHipmitoolLocal toolingPath/name of the ipmitool binary used to drive the BMC.
SENSORS_PATHsensorsLocal toolingPath/name of the lm-sensors binary used to read temperatures.
ENABLE_OTELTrueObservabilityEnable OpenTelemetry/logfire instrumentation for the agent.
ENABLE_DELEGATIONFalseSecurityEnable OIDC Bearer-token delegation middleware (inert by default — Fan Manager is a local tool).
EUNOMIA_TYPEnoneSecurityEunomia policy mode: none, embedded, or remote.
EUNOMIA_POLICY_FILEmcp_policies.jsonSecurityPath to the Eunomia policy file when EUNOMIA_TYPE is set.

Build-time only (not application config): UV_COMPILE_BYTECODE, NO_COLOR, and TERM are consumed by the build/runtime environment (Docker image build, terminal rendering) and are not read by the application code.


Security & Governance

Built directly upon the enterprise-ready agent-utilities core, standard security parameters are fully supported:

Access Control & Policy Enforcement

  • Eunomia Policies: Fine-grained, policy-driven tool authorization (none, embedded, or remote).
  • OIDC Token Delegation: Optional RFC 8693 token exchange (inert by default — Fan Manager is a local tool).

Runtime Security Grid

FeatureFunctionalityEnablement
Tool GuardSensitivity inspection with human-in-the-loop validationEnabled by default
Prompt Injection DefenseInput scanning, repetition monitoring, and recursive loop blocksEnabled by default
Context Safety GuardStuck-loop detectors and contextual overflow preemptive alertsEnabled by default

Installation

# Using uv (highly recommended)
uv pip install fan-manager[all]

# Using standard pip
python -m pip install fan-manager[all]

Documentation

The complete documentation is published as the official documentation site.

PageContents
Installationpip, source, extras, prebuilt Docker image
Deploymentrun the MCP and agent servers, Compose, env config
Usagethe MCP tools, the Api facade, the CLI
Overviewthe action-routed tool surface and architecture
Conceptsconcept registry (CONCEPT:FAN-*)

Contribute

Contributions are welcome! Please ensure code quality by executing local checks before submitting pull requests:

  • Format code using ruff format .
  • Lint code using ruff check .
  • Validate type-safety with mypy .
  • Execute test suites using pytest
Ver o original no GitHub

Bom para

Relacionados