Arena MCP Extractor
Inspects Rockwell Automation Arena simulation models (.doe) through Arena's Windows COM API, extracting model metadata, modules, connections, submodels, visual layout, material-handling data, compatibility audits, and optional SIMAN source from a temporary copy.
Provides read-only inspection and reading of Arena SQLite results databases, including supported statistics views.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Arena MCP Extractor
A read-only Model Context Protocol (MCP)
server and CLI for inspecting Rockwell Automation Arena simulation models.
It opens .doe files through Arena's Windows COM object model and returns
JSON-compatible data for a downstream simulation translator.
The server does not save, run, or edit the original model. Optional SIMAN generation uses a temporary copy. SQLite result databases are opened read-only. Extracted data can contain confidential model details; check your client's data handling policies before sharing it with an AI provider.
Requirements
Windows with Python 3.10 or later.
A licensed local Arena installation registered as
Arena.Application.An MCP-compatible client for agent integration; the CLI also works independently.
Platform-independent unit tests can run on Linux without Arena, but live COM extraction requires Windows and Arena.
Related MCP server: Arena MCP Extractor
Installation
From the repository directory in PowerShell:
python -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e .
.\.venv\Scripts\arena-mcp.exe doctorYou can activate the environment with .\.venv\Scripts\Activate.ps1 and use
arena-mcp directly. Activation is not required when using the full executable
path. See Development for test dependencies.
Configure model access
By default, the server searches existing Documents and Desktop folders under your home directory, including OneDrive equivalents, and Arena's public Documents folder. Model and results paths must be within an allowed root.
To replace those defaults, set ARENA_MODEL_ROOTS to existing directories
separated by semicolons on Windows:
$env:ARENA_MODEL_ROOTS = "C:\Arena\Models;C:\Shared\Arena"
.\.venv\Scripts\arena-mcp.exe doctor --live-checkdoctor reports platform, Arena registration, and available roots; the optional
live check also connects to Arena. A failed check returns a nonzero exit code.
The shell assignment above lasts only for that shell and processes it launches.
Set the variable in Windows environment settings and restart the client, or
configure it explicitly for the MCP server as shown below.
ARENA_ALLOW_ANY_PATH=1 disables the allowed-root restriction. Use it only when
you trust the client and intend to permit access to supported files anywhere the
server process can read.
Connect an MCP client
Install the project first. In the examples below, replace
C:\path\to\arena-mcp with the absolute path to your checkout and
C:\Arena\Models with an existing allowed model folder. Keep the executable on
the same Windows machine as Arena; a remote agent or container cannot use its
local COM installation automatically. Merge examples into existing configuration
instead of replacing other servers.
These examples start the server over stdio, its default transport. Once
connected, ask the client to call arena_status with live_check: true, then
use extract_arena_report on a model inside an allowed root.
Abacus.AI
For Abacus Desktop (Code Mode), its CLI, or its VS Code extension, add this to
~/.abacusai/mcp.json (or the project's .abacusai/mcp.json):
{
"mcpServers": {
"arena": {
"command": "C:\\path\\to\\arena-mcp\\.venv\\Scripts\\arena-mcp.exe",
"args": [],
"env": {
"ARENA_MODEL_ROOTS": "C:\\Arena\\Models"
}
}
}
}Reload the client after editing the file. Use /mcp to check the connection, or
manage it in Abacus Settings > MCP servers in VS Code. See the
Abacus MCP documentation.
Claude Code
Register the server from PowerShell:
claude mcp add --env 'ARENA_MODEL_ROOTS=C:\Arena\Models' --transport stdio arena -- 'C:\path\to\arena-mcp\.venv\Scripts\arena-mcp.exe'Use claude mcp list or /mcp in Claude Code to check it. See
Claude Code's MCP documentation.
Codex
Register the server from PowerShell:
codex mcp add arena --env 'ARENA_MODEL_ROOTS=C:\Arena\Models' -- 'C:\path\to\arena-mcp\.venv\Scripts\arena-mcp.exe'
codex mcp listCodex stores the configuration in ~/.codex/config.toml by default; local Codex
CLI and IDE clients on the same host share it. See the
Codex MCP documentation.
Cursor
Add the same mcpServers JSON shown in Abacus.AI to
~/.cursor/mcp.json for your user, or .cursor/mcp.json for the project.
Add "type": "stdio" inside the arena entry, replace the example paths, and
check the server in Cursor's MCP settings. See the
Cursor MCP documentation.
Gemini CLI
Add the same mcpServers JSON shown in Abacus.AI to
~/.gemini/settings.json for your user, or .gemini/settings.json for the
project. Replace the example paths and use /mcp in Gemini CLI to check the
connection. See the Gemini CLI MCP documentation.
GitHub Copilot
For the Copilot harness in VS Code, add the following to
~/.copilot/mcp-config.json (or the workspace-root .mcp.json):
{
"mcpServers": {
"arena": {
"type": "stdio",
"command": "C:\\path\\to\\arena-mcp\\.venv\\Scripts\\arena-mcp.exe",
"args": [],
"env": {
"ARENA_MODEL_ROOTS": "C:\\Arena\\Models"
},
"tools": ["*"]
}
}
}Alternatively, open Chat: Open Customizations > MCP Servers, add a
Command (stdio) server, and select the desired configuration scope. Verify
the connection by asking Copilot to call arena_status. See the
VS Code MCP configuration reference.
CLI usage
With the virtual environment activated, use:
arena-mcp --status
arena-mcp --list-models
arena-mcp --inspect 'C:\Arena\Models\MyModel.doe'
arena-mcp --extract 'C:\Arena\Models\MyModel.doe'
arena-mcp --audit 'C:\Arena\Models\MyModel.doe'
arena-mcp --report 'C:\Arena\Models\MyModel.doe' --output report.json--report combines the audit and neutral IR in one primary Arena session and
includes module counts, truncation state, warnings, and translation readiness.
Optional SIMAN extraction opens an isolated temporary copy separately.
--max-modulesand--max-repeat-rowsapply to--extract,--audit, and--report.--include-vba-source,--include-siman-source, and--include-binary-payloadsapply to--auditand--report.--output PATHwrites JSON to a new file and refuses to overwrite an existing file. Without it, JSON is written to stdout.arena-mcp --helplists all options. Runningarena-mcpwithout a CLI operation starts the stdio MCP server.
MCP tools
All tools are annotated read-only.
Tool | Purpose |
| Check registration and optionally connect to Arena |
| Discover |
| Summarize model metadata, modules, and compatibility |
| List modules and their operands |
| List the model's connection graph |
| Extract the neutral intermediate representation (IR) |
| Return the audit and IR together |
| Classify module definitions for translation |
| Report data coverage and translation blockers |
| Inspect attached panels and operand definitions |
| Extract submodel hierarchies |
| Extract layout and animation data |
| Extract material-handling collections |
| Inspect OLE compound-file streams |
| Generate SIMAN source from a temporary copy |
| Inspect an Arena SQLite results database |
| Read a supported statistics view |
Use extract_arena_report as the usual starting point after checking status.
Review its completeness and audit.coverage_report fields before translating;
warnings, limits, and coverage gaps can make the extracted data incomplete.
Output contracts
IR schema version:
0.3.0Audit schema version:
2.0.0Combined report schema version:
1.0.0
The combined-report JSON Schema validates the report envelope and key nested fields; it is not a complete schema for every IR and audit field. The example report is synthetic, not an Arena extraction. Individual tools return their relevant version fields where defined; not every response has both schema versions.
Troubleshooting
Arena is not registered or reachable: run
arena-mcp doctor --live-checkon the Windows machine, then check the Arena installation, license, and COM registration.Path is outside allowed roots: use an existing directory in
ARENA_MODEL_ROOTS, ensure the client passes it to the server, and restart or reconnect the server.arena-mcp --statusshows the resolved roots.Server does not start: check that the configured executable path points to the virtual environment created during installation and that the client runs on the Windows host, not a remote environment.
Request hangs: lock acquisition and collection-readiness waits are bounded, but a COM method already blocked inside Arena cannot currently be canceled safely by a client timeout.
Development
.\.venv\Scripts\python.exe -m pip install -e '.[test]'
.\.venv\Scripts\python.exe -m unittest discover -vThe unit tests also run on Linux using an equivalent Python environment. CI
tests Windows and Linux with Python 3.10 and 3.12; it does not run live Arena
integration tests. Tests are grouped by feature in tests/. Run a
specific group with, for example, python -m unittest -v tests.test_model.
See AGENTS.md for coding-agent guidance.
Project layout
arena_api.py: shared API facade; use thearena-mcpcommand-line entry point for CLI and server operation.arena_mcp/cli.py,server.py: CLI and MCP adapters.arena_mcp/com.py,paths.py,environment.py: COM sessions, allowed paths, status, and discovery.arena_mcp/model.py,audit.py,reports.py, and related modules: extraction, coverage audits, and combined reports.arena_mcp/artifacts.py,results.py: compound/SIMAN artifacts and read-only SQLite results.arena_mcp/schemas/,examples/: report schema and synthetic fixture.
License and disclaimer
The original written material in this repository is licensed under MIT; see LICENSE for attribution requirements and third-party material. This project is not affiliated with or endorsed by Rockwell Automation. Arena is their trademark, and a licensed installation is required.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Geometry and CAD file metadata extraction for STL, OBJ, PLY, PCD, LAS/LAZ, glTF/GLB.
Manage SysML2 projects; check, evaluate, verify, query, document and diagram models.
Excel analytics: inspect, query (JSON rows), charts, and JSON-to-xlsx workbook writing.
Read title blocks, parts lists, revision history and notes from 2D engineering drawings.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceControls FlexSim simulation engine via Model Context Protocol, enabling natural language-driven simulation modeling and automation.2-
- AlicenseNot gradedqualityDmaintenanceRead-only MCP server that exposes Rockwell Automation Arena simulation models to LLM clients via COM, without modifying them.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI-driven control of Autodesk Navisworks via COM, supporting model tree browsing, property queries, searching, isolation, recoloring, and screenshots without a .NET add-in.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create, edit, compile, and run Rockwell Arena simulation models from plain-language descriptions, then analyse results with confidence intervals and compare what-if scenarios. Provides model inspection, error attribution, screenshots, and Arena module reference tools to any MCP client.MIT