convez.ai
MCP ServerIntegração & APIsAvançado
Power-Agent

PowerMCP - Servidores MCP para Sistemas de Potência

Power-Agent/PowerMCP

IA para engenharia de sistemas elétricos via MCP

Ver no GitHub
BomPluginScore · de 0 a 100

Coleção open-source de servidores MCP que conecta LLMs a softwares de sistemas de potência como PowerWorld, PSSE e OpenDSS. Permite que agentes de IA interajam diretamente com aplicações de energia para simulação, análise de contingência e controle inteligente de redes elétricas.

Instalação

$npx convez-ai Power-Agent/PowerMCP

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
238
Forks
67
Acompanhando
7
Saúde
37%
Último commit
há 2 dias
Versão
v0.5.1
Issues abertas
18
Contribuidores
15

Casos de uso

  • Análise automática de contingência em redes de distribuição
  • Avaliação de cenários de crescimento de carga com relatórios inteligentes
  • Simulação e otimização de operação de sistemas de potência
  • Coordenação inteligente entre agentes IA e softwares SCADA/EMS

Veredito

PowerMCP é um projeto especializado e bem-estruturado que preenche uma lacuna real na integração de IA com engenharia elétrica. Demanda conhecimento técnico profundo em sistemas de potência, mas oferece um caminho claro via MCP para automatizar workflows críticos do setor energético.

README

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

PowerMCP ⚡

License: MIT Python Version

PowerMCP is an open-source collection of MCP servers for power system software like PowerWorld and OpenDSS. These tools enable LLMs to directly interact with power system applications, facilitating intelligent coordination, simulation, and control in the energy domain.

🌟 What is MCP?

The Model Context Protocol (MCP) is a revolutionary standard that enables AI applications to seamlessly connect with various external tools. Think of MCP as a universal adapter for AI applications, similar to what USB-C is for physical devices. It provides:

  • Standardized connections to power system software and data sources
  • Secure and efficient data exchange between AI agents and power systems
  • Reusable components for building intelligent power system applications
  • Interoperability between different AI models and power system tools

🤝 Our Community Vision

We're building an open-source community focused on accelerating AI adoption in the power domain through MCP. Our goals are:

  • Collaboration: Bring together power system experts, AI researchers, and software developers
  • Innovation: Create and share MCP servers for various power system software and tools
  • Education: Provide resources and examples for implementing AI in power systems
  • Standardization: Develop best practices for AI integration in the energy sector

🚀 Getting Started with MCP

📖 Quick start

🚀 New to PowerMCP? Start here!

The recommended way to get started is the powermcp package and its installer (see the Installation section below):

pip install powermcp
powermcp install        # pick tools, capture local paths, write your MCP client config

📋 The PowerMCP Tutorial PDF documents the original low-code / manual setup — cloning the repo and hand-editing the Claude Desktop config. It predates the powermcp installer and is not the recommended path; use it only if you specifically want the manual approach.

Video Demos

Check out these demos showcasing PowerMCP in action:

  • Contingency Evaluation Demo: An LLM automatically operates power system software, such as PowerWorld and pandapower, to perform contingency analysis and generate professional reports.

  • Loadgrowth Evaluation Demo: An LLM automatically operates power system software, such as PowerWorld, to evaluate different load growth scenarios and generate professional reports with recommendations.

Useful MCP Tutorials

MCP follows a client-server architecture where:

  • Hosts are LLM applications (like Claude Desktop or IDEs) that initiate connections
  • Clients maintain 1:1 connections with servers, inside the host application
  • Servers provide context, tools, and prompts to clients

Check out these helpful tutorials to get started with MCP:

📦 Installation

PowerMCP installs as a single Python package with an interactive CLI. Python 3.10+ is required.

pip install powermcp

The base install includes the two open-source engines that need no extra setup — pandapower and PyPSA. Every other tool is opt-in via an extra:

pip install powermcp[psse]              # add PSS/E support
pip install powermcp[andes,opendss]     # add several tools at once
pip install powermcp[opensource]        # all open-source tools (ANDES, Egret, OpenDSS, surge, HOPE, LTSpice, PowerIO)
pip install powermcp[all]               # everything (closed-source tools still need the local software)

Set up with the interactive installer

powermcp install

The wizard lets you pick tools (pandapower + PyPSA pre-selected), captures the local install path for any closed-source/EXE-based tools you choose (PSS/E, PSLF, PowerFactory, PSCAD, LTSpice), installs the right extras, and writes the MCP client configuration for Claude Desktop, Claude Code, and the Codex CLI. Use --dry-run to preview the changes, or --yes for a non-interactive core install.

In the interactive picker, move with ↑/↓ and press SPACE to toggle each tool before ENTER (ENTER alone keeps only the preselected tools). Prefer not to use the checkbox? Choose tools directly:

powermcp install --tools psse,andes      # core + the listed tools
powermcp install --all                   # every tool available on this platform

Re-running powermcp install pre-checks the tools you've already installed or configured, so it preserves and updates your setup instead of resetting to the core tools. Paths for tools like LTSpice are auto-detected and pre-filled, so you can usually just press Enter.

CLI commands

CommandDescription
powermcp installSetup wizard — interactive, or --tools <ids> / --all (also --dry-run, --yes, --clients)
powermcp run <tool>Launch a server over stdio (used by the generated client config)
powermcp listList the available tools, extras, and Windows-only flags
powermcp doctorCheck each tool's dependencies and configured paths
powermcp config show / config set <tool>.<key> <path>Inspect / set local software paths

Closed-source / EXE-based tools

These tools wrap commercial or locally-installed software, so PowerMCP stores the local path in ~/.powermcp/config.toml (captured by powermcp install, or set manually with powermcp config set):

ToolConfig keysExample
PSS/Epsse.python_lib, psse.binpowermcp config set psse.python_lib "C:\Program Files\PTI\PSSE36\36.2\PSSPY311"
PSLFpslf.python_libpowermcp config set pslf.python_lib "C:\Program Files\GE PSLF\PSLF_PYTHON"
PowerFactorypowerfactory.python_pathpowermcp config set powerfactory.python_path "...\DIgSILENT\PowerFactory 2024\Python\3.11"
LTSpiceltspice.exe (auto-detected)Found automatically in standard locations — usually no setup needed. Override: powermcp config set ltspice.exe "C:\Program Files\ADI\LTspice\LTspice.exe"
HOPEhope.repo_root, hope.julia_binpowermcp config set hope.repo_root "C:\src\HOPE"
PowerWorld(none)esa auto-discovers a running, licensed Simulator via COM; the powerworld extra also installs numba (required by esa)
PSCAD(none)pip install powermcp[pscad-windows] provides mhi-pscad; PSCAD must be installed

The Codex Desktop app on Windows has been reported to overwrite ~/.codex/config.toml; the Codex CLI is unaffected. If you use both, re-run powermcp install after Desktop edits.

Case conversion between servers (PowerIO)

The powerio extra adds a conversion server backed by powerio. It parses MATPOWER .m, PSS/E .raw, PowerWorld .aux, PowerModels JSON, and egret JSON into one format neutral network, converts between those formats with fidelity warnings, and builds the sparse matrices solvers need (B', B'', Y_bus, PTDF, LODF, Laplacian, LACPF).

Its JSON transport is the exchange format between PowerMCP servers: parse a case once, pass the returned json string between tool calls, and load it anywhere.

parse_case(path="case9.raw")                       # powerio server → {"json": ..., "summary": ...}
load_network_from_json(network_json=...)           # pandapower server ingests the transport
load_model_from_json(network_json=...)             # egret server stages it as a solvable case file
import_case_from_json(network_json=..., output_path="case9.nc")  # PyPSA server writes a .nc for its tools
compute_matrix(kind="ptdf", json=...)              # powerio server builds matrices from it
save_case(to="psse", out_path="case9.raw", json=...)  # stage a file for path-only servers

save_case covers the servers without a bridge: write the converted case to disk and point their load tools at the file (e.g. convert PowerWorld .aux to MATPOWER .m for ANDES).

Running from a clone (without installing)

Every server is still a standalone script. Clone the repo and run any server directly for use in Claude Desktop:

python pandapower/panda_mcp.py
python PSSE/psse_mcp.py          # uses ~/.powermcp/config.toml if present, else legacy default paths

Testing with your LLMs

Note: All MCPs should be tested via an MCP client (Claude Desktop, Claude Code, or Codex) before submitting a PR to ensure consistency.

powermcp install writes the client configuration for you. The generated entries look like the example in config.json. (The PowerMCP Tutorial PDF covers the older manual / low-code setup and isn't needed for the package install.)

📚 Documentation

For detailed documentation about MCP, please visit:

🤝 Contributing

We welcome contributions! Please see our Contributing Guidelines for details.

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

🙏 Acknowledgments

Core Team

Special Thanks

Ver o original no GitHub

Bom para

Relacionados