Unified B&R MCP Server — Build, Transfer, Debug, Trend for Automation Studio
Critical gaps across most tools. 11 of 38 tools (29%) have empty or missing input schemas (pvi_read_variable, pvi_write_variable, pvi_list_variables, pvi_write_variables_batch, pvi_watch_variables, pvi_get_trend_data, pvi_stop_watch, pvi_export_csv, pvi_dashboard, pvi_list_watch_sessions, pvi_fast_watch, pvi_fast_trend_chart, pvi_fast_stop, pvi_query_variables). Tools with visible schemas (build_project, pvi_connect, pvi_download_module) show good structure, but parameter descriptions are sparse. Error handling is minimal, most tools return generic 'Not connected' errors without recovery guidance. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (DESTRUCTIVE tools like pvi_coldstart, pvi_warmstart, pvi_diagnostics). Naming is consistent (verb_noun pattern) but descriptions vary widely in quality (build_project: 200+ chars; pvi_read_variable: 0 chars).
Build a B&R Automation Studio project using BR.AS.Build.exe. Returns exit code (0=success, 1=warnings, 3=error), build output, and parsed errors/warnings. Use buildMode "BuildAndTransfer" with simulation=true to deploy to ARSim.
Show the unified B&R MCP server configuration — build, PVI, and companion paths.
Get detailed information about a B&R Automation Studio project including configurations and modules.
List all B&R Automation Studio projects in the configured projects root directory.
Parse B&R build output into structured errors and warnings. Provide either raw text or a log file path.
Auto-detect and connect to a B&R PLC. When PVI_PLC_IP is explicitly configured, tries the hardware PLC first, then falls back to ARSim on localhost:11169. Otherwise tries ARSim first.
11 tools have empty or missing input schemas (pvi_read_variable, pvi_write_variable, pvi_list_variables, pvi_write_variables_batch, pvi_watch_variables, pvi_get_trend_data, pvi_stop_watch, pvi_export_csv, pvi_dashboard, pvi_list_watch_sessions, pvi_query_variables).
Destructive tools (pvi_coldstart, pvi_warmstart, pvi_diagnostics) lack tool annotations. No readOnlyHint, destructiveHint, or idempotentHint in schema. LLMs cannot distinguish safe from dangerous operations without explicit annotations.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
Compare a local module file with the version on the PLC. Returns: 0=equal, 9=file newer, 10=missing on PLC, 11=file older, 12=file missing, 13-16=other differences.
Cold restart the PLC. Clears all non-retained variables. CAUTION: This will stop all running programs. Set confirm=true to execute.
Connect to a B&R PLC via PVI (ANSL/TCP). Tests the connection and saves parameters for subsequent tool calls. Returns CPU type, AR version, and PLC status on success.
Generate a dashboard view of current watch sessions and their status.
Get the status of the local variable database including record count and last refresh time.
Execute a complete deployment workflow: build project, transfer modules, and verify on PLC.
Enter diagnostics mode on the PLC. All tasks are stopped but modules remain loaded. CAUTION: This will stop task execution. Set confirm=true to execute.
Disconnect from the current PLC. Stops any active variable watches and clears stored connection parameters.
Transfer a module file (.br) from the PC to the PLC. Use CHECK option to verify before transferring. Memory types: RAM, ROM, SYSROM, FIXRAM.
Export trend data from a watch session to a CSV file.
Stop a fast watch session running on the C# companion.
Generate a trend chart from fast watch data using the C# companion.
Start a high-speed variable watch using the C# companion for faster sampling rates.
Get PLC information including CPU type, AR version, PLC status, memory info, and hardware info.
Retrieve collected trend data from an active watch session.
Generate a comprehensive health report of the PLC including CPU info, memory, tasks, modules, and error log.
List all modules on the PLC including system and application modules. Returns name, version, memory type, module type, and date.
List all tasks running on the PLC. Returns task name, version, memory type, and date.
List all variables available on the connected PLC.
List all active variable watch sessions.
Check if a PLC is reachable. Mode 'tcp' is a fast TCP socket probe (~2s). Mode 'pvi' (default) runs a full PVITransfer connection and returns PLC status. Defaults to the current connection's IP if no address is provided.
Query the local variable database for variables matching search criteria.
Read the PLC error logbook. Returns error entries with timestamps and error codes.
Read a variable value from the connected PLC.
Refresh the local variable database by querying the connected PLC.
Stop an active variable watch session.
Disconnect from the current PLC and reconnect to a different target in one call. "hardware" connects to PVI_PLC_IP, "arsim" connects to ARSim on localhost:11169, "auto" uses the same logic as pvi_auto_connect.
Read a module from the PLC and save it to a file on the PC.
Warm restart the PLC. Retained variables are preserved. CAUTION: This will restart all programs. Set confirm=true to execute.
Start watching PLC variables and collect trend data at regular intervals.
Write a value to a variable on the connected PLC.
Write multiple variable values to the PLC in a single batch operation.
Error handling is minimal. Most tools return generic 'Not connected to PLC' errors without recovery guidance. No actionable error messages that tell LLM what to do next (e.g., 'Try pvi_connect first').
Output schemas are not documented. Tools like pvi_get_cpu_info, pvi_list_tasks, pvi_health_report return structured data but no schema is visible in source. LLMs cannot plan downstream calls without knowing response structure.
pvi_deploy_workflow has empty input schema ({}). Workflow tools typically require parameters (project path, target config, etc.). Schema must be populated or tool cannot be used.