Command-line interface

StaticalPrismCmd.exe is Prism for AL's command-line tool. You use it to run reports in a script or a build pipeline, to show and install a license, to inspect and clear the package cache, to open a workspace in Prism for AL, and to run the MCP server for AI agents without a Prism window.

The Prism for AL MSIX package registers StaticalPrismCmd.exe as an execution alias, so it runs from any command prompt or script, whatever PATH holds, and always runs the installed version.

The reports and the MCP server need a license or a trial license. Without one, Prism for AL runs with limited features: report lists no reports, and the MCP server commands stop with exit code -32.

Help and workspaces

Put -h after the tool for a list of commands and the exit codes, or after a command for that command's help:

StaticalPrismCmd.exe -h
StaticalPrismCmd.exe report -h
StaticalPrismCmd.exe report onprem-usages -h

The tool prints the Prism logo, the license profile and its version first. It leaves them out when it runs an MCP server and when package-cache writes JSON, so that output stays clean for the program that reads it.

The report, open and MCP server commands take a workspace argument, in any of these forms:

• A folder that holds AL source and an app.json, or several such modules.
• A Visual Studio Code workspace file (.code-workspace).
• An AL package file (.app).

A path that does not exist stops the command with Workspace not found and exit code 1. An option goes after the command it belongs to.

Report command

report builds the workspace symbol index, prints any parse errors it found, and saves one report. The report goes after report, and the workspace after the report:

StaticalPrismCmd.exe report <report> <workspace> [options]

Every report takes these options:

In a build pipeline, add --strict so that a workspace that does not parse fails the build, and --log-file so that a failed run leaves a log to read. The same reports run from the Reports page in a workspace window.

Solution metrics report

solution-metrics saves an Excel workbook (.xlsx) with object counts by type for each app, and a list of every object.

StaticalPrismCmd.exe report solution-metrics "C:\workspace\LearnPrism" -o "C:\reports\learn\solution-metrics.xlsx"

Object dependencies report

object-dependencies saves a tab-separated file of the objects each object depends on, with the kind of dependency.

StaticalPrismCmd.exe report object-dependencies "C:\workspace\LearnPrism" -o "C:\reports\learn\object-dependencies.csv"

Unreferenced objects report

unreferenced-objects saves a tab-separated list of the objects that no other object references.

StaticalPrismCmd.exe report unreferenced-objects "C:\workspace\LearnPrism" -o "C:\reports\learn\unreferenced-objects.csv"

OnPrem usages report

onprem-usages builds a full Code graph and saves a tab-separated list of the code that uses procedures and objects scoped to OnPrem. It takes longer than the other reports, because of the code graph.

StaticalPrismCmd.exe report onprem-usages "C:\workspace\LearnPrism" -o "C:\reports\learn\onprem-usages.csv" --log-file "C:\reports\learn\onprem-usages.log" --strict

Only one code graph builds at a time on a machine. When another one holds the graph folder, the report stops with “Graph server temporary directory is already in use. Please try again, …”; run it again a moment later.

Parse errors report

parse-errors saves a text file (.txt) of the files that failed to parse, with each error.

StaticalPrismCmd.exe report parse-errors "C:\workspace\LearnPrism" -o "C:\reports\learn\parse-errors.txt"

License command

license shows the license status of Prism for AL on this machine. It takes no arguments or options and always exits with 0.

StaticalPrismCmd.exe license

It prints one line per fact:

License install command

license install saves a license key, checks it, and prints the resulting status as license does. It saves the key where the Activate license window does, and a running Prism for AL picks it up without a restart.

Give the key exactly once: as the argument, with --key-file or with --stdin. In a script, use one of the two options, so the key does not appear on a command line.

StaticalPrismCmd.exe license install --key-file "C:\keys\prism-for-al.txt"

The License file line names the file the key went to. When Prism for AL does not see a key you installed, compare that line with the license file Prism for AL reads.

Package cache command

package-cache inspects and clears the package cache that Prism for AL, its MCP servers and StaticalPrismCmd.exe share. It needs no workspace and no license, so it works when a license has lapsed and the disk is full. The Package cache page shows the same cache in Prism for AL.

StaticalPrismCmd.exe package-cache list
StaticalPrismCmd.exe package-cache clear --publisher Microsoft --dry-run

package-cache list shows a table of the cached packages: Publisher, Name, Version, Size, State (ready, extracting, failed, stopped or initial) and Pins, the number of holders using the package, with (peer) for those in other processes. A last line gives the count, the total size and the cache folder. package-cache clear deletes the selected packages that nothing is using, and prints an outcome per package and a summary.

Selectors match exactly, ignoring case, and several selectors narrow the selection together. clear needs a selector or --all, so a mistyped selector never empties the cache. Before it deletes, it asks “Delete N package(s) from the cache?”; without a console to ask on, it stops with “Refusing to delete N package(s) without confirmation. Re-run with --yes.”

Open command

open opens a workspace in Prism for AL. When Prism for AL is running, the tool uses that instance; otherwise it starts Prism for AL and waits for it. A workspace that is already open is not opened again.

StaticalPrismCmd.exe open "C:\workspace\LearnPrism"

When the tool cannot reach Prism for AL, it prints “Unable to connect to Prism For AL GUI process.” and exits with -1.

MCP server commands

mcp-server-http runs an MCP server over HTTP, at http://localhost:<port>, for a workspace without a Prism window. mcp-server-stdio runs one that talks over its standard input and output: you do not run it yourself, but put it in an agent's MCP configuration, and the agent starts it. How to choose between them and connect a client is in Start the server.

StaticalPrismCmd.exe mcp-server-http "C:\workspace\LearnPrism" --port-search 47821..47920
StaticalPrismCmd.exe mcp-server-stdio "C:\workspace\LearnPrism"

The server starts at once and builds the symbol index and the code graph in the background; a tool that needs them rejects calls until they are ready. The HTTP server prints “MCP server is running on http://localhost:47821”; press Ctrl+C to stop it. The stdio server writes its messages to standard error, never to standard output, and stops when its standard input closes.

Exit codes

Every command ends with one of these exit codes, which StaticalPrismCmd.exe -h also lists:

Related

• MCP server: connect an agent, and every tool and resource the server offers.
• Reports page: run the same reports from a workspace window.
• Activate license window: activate or remove a license in Prism for AL.
• Package cache page: the package cache in Prism for AL.
• Installation: install the MSIX package that brings the tool.