PowerMCPby Power-Agent
One Python package with separate MCP servers for pandapower, PyPSA, OpenDSS, PowerWorld, PSS/E, PowerFactory, PSCAD and more.
PSS/E has no dedicated MCP server yet. The PowerMCP collection includes a PSS/E server that runs on the same Windows machine through psspy: it opens and solves cases, reads dynamic-simulation output and can call most psspy functions by name, which makes it thin but broad. A companion PowerSkills pack guides the agent through PSS/E base cases. Siemens's own AI offer is the PSS/E Copilot, a separate assistant rather than an MCP server.
One Python package with separate MCP servers for pandapower, PyPSA, OpenDSS, PowerWorld, PSS/E, PowerFactory, PSCAD and more.
Skills that tell an agent which PowerMCP tool to use first, plus ten mitigation playbooks for power-system study findings.
Listings are sorted by origin, then by recent activity. GitHub data is refreshed nightly. Nothing here is ranked.
An MCP server or skill can only do what PSS/E lets programs do. PSS/E exposes 2 automation interfaces:
Siemens offers the Gridscale X PSS/E Copilot, a pilot SaaS add-on with a Windows front end and a Siemens cloud LLM back end. It answers PSS/E questions in natural language and returns ready-to-run Python scripts that execute locally against PSS/E 35, 36 or 37; simulation output is uploaded only if you choose to. Its product sheet, effective 22 May 2026, doesn't mention MCP, and Siemens publishes no PSS/E MCP server.
Checked 4 Nov 2026. Sources: Gridscale X PSS®E Copilot product sheet (Siemens), Gridscale X PSS®E product page (Siemens)
Taken from the listings' own documentation. Check each listing for exactly what it supports.
The listings here document setup for Claude Code, Claude Desktop, Codex CLI and Cursor. Install steps, copied from each project's own documentation, are on each listing's page. Most PSS/E integrations run on your own computer next to PSS/E, so you need PSS/E installed and licensed on the same machine unless the listing says otherwise.
No. Siemens's AI product for PSS/E is the Gridscale X PSS/E Copilot, a separate Windows app with a cloud back end that writes psspy scripts for you. The only MCP route is the community PowerMCP server.
Yes, with PowerMCP installed on the PSS/E machine and its psse.python_lib path pointed at your PSSPY folder. Claude can then open and solve cases and call psspy functions; contingency and dynamic runs go through the generic psspy tool rather than dedicated tools.
Its PSS/E README asks for PSS/E 35 or newer with the Python 3 psspy API. The configuration example points at PSS/E 36.2 with Python 3.11.
Not for conversion. PowerMCP's PowerIO server parses .raw cases on its own, so you can move a case into pandapower or PyPSA without PSS/E. Solving in PSS/E itself needs your licensed install.
AI-generated models, drawings and results must be checked by a qualified engineer before use.
Sources (checked 4 Nov 2026): PowerMCP PSS/E server README · Gridscale X PSS®E product page (Siemens) · Gridscale X PSS®E Copilot product sheet (Siemens) · PSS/E product page
PSS/E is a trademark of Siemens. Tresca is independent and not affiliated with or endorsed by Siemens.