Requirements

Requirement	Detail
Windows	Windows 10 or 11. AI Power Tools is Windows-only because EA's automation interface is. The VS Code extension refuses to start on any other platform
Enterprise Architect on the same machine	Installed and licensed, running with a project open when the first EA operation is called. The server does not start EA. Where computer use is available the assistant can start EA and open the model, after asking you. Otherwise you do. Any edition that supports automation
EA version	EA 16.1 or later is the documented minimum. AI Power Tools is exercised on EA 17.0 and 17.1
Repository types	A local file (`.qea` or `.qeax`), a server connection, or a cloud connection through Pro Cloud Server, to the extent EA itself supports them. Some operations need a local file. See Supported repositories
Client	Claude Desktop 0.10.0 or later, for the Desktop extension that supplies the server to Claude Desktop chat, Claude Cowork and Claude Code in the Claude desktop app. A Claude account that can install the skills plugin. Claude Code in a terminal does not load Desktop extensions. VS Code 1.99 or later for the VS Code extension
Capabilities beyond the server	Computer use, local code execution and browser control depend on the client. Each skill works with the capabilities your client provides and says what changes without the rest. See Capabilities and surfaces
Python for the server	Not needed. The server ships as a compiled program
Python for the code engines	Needed wherever local code execution runs an engine: Python 3 on the machine where EA runs. `pyyaml` for the composition engine's notation bindings. `pyarrow` only for delivering the reporting business layer as Parquet files; it is deliberately not bundled, so install it when you choose Parquet files. `pywin32` only for scripts the AI writes to drive EA's automation interface directly, in `ea-com` and in `ea-mdg-deploy`'s automation checks; no reporting step needs it. Everything else uses Python's standard library
SQL Server, for reporting in a database	Needed only to deliver the reporting business layer as views in the EA repository's database or as a separate reporting database. Parquet files need no database. AI Power Tools connects with the Windows authentication of the account that runs the server, not with SQL logins, through the database providers Windows supplies, so nothing extra is installed. A separate reporting database can instead be a SQL database in Microsoft Fabric: that needs a Fabric capacity, the database created in the Fabric portal, the Microsoft OLE DB Driver for SQL Server on the machine where the server runs, and a person to complete the Microsoft Entra sign-in once per server process. Views in the EA database need a server connection whose repository is held in SQL Server, direct access to that database, and the rights to create views and a schema of their own there; the rights are checked before anything is written. A separate reporting database needs an account that can create that database and the tables, indexes and views in it, which in practice means owner-level rights on it; these rights are not checked in advance. The minimum SQL Server version is not stated. See Supported repositories
Network	Not needed for most tool calls. Used for background update checks, any ruleset you fetch from a web address, and the connection to the database that a reporting profile names, with its Microsoft Entra sign-in for a SQL database in Microsoft Fabric. See Security and data handling
One EA instance per seat	A per-user Sparx license caps concurrency at one EA instance. Do not start a second instance against the same model file