Avizo MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Avizo MCP Server List the available workflows in my project directory"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Avizo MCP and Codex Skill
Local Model Context Protocol server and Codex skill for Thermo Scientific Amira-Avizo automation on Windows.
This repository is designed as a conservative bridge around an existing local Avizo installation. It does not call private Avizo APIs from outside the Avizo process. Instead, it helps an MCP client:
discover Avizo, AvizoToGo, Amira, bundled Python, docs, demos, and a job workdir;
inventory Avizo/Amira project trees containing
.hx,.am,.measure.am, TIFF stacks,Header.txt, DVC outputs, and deep-learning artifacts;inspect
.hxworkflows and extract command patterns plus referenced files;create reproducible
.hxand Python scripts in a job directory;generate
.pyscroplus.rcscript-object skeletons using the public Amira-Avizo extension pattern;launch Avizo/AvizoToGo/Amira or run Avizo's bundled Python;
capture and read job logs.
Repository Layout
src/avizo_mcp/ MCP server package
skills/avizo/ Codex skill that teaches agents how to use the MCP
examples/ Example MCP config and smoke-test scripts
pyproject.toml Python package metadataRelated MCP server: Ansys Workbench MCP
Install
Use standard Windows CPython, not MSYS Python. The mcp dependency pulls pywin32 on Windows, which is not available for MSYS Python builds.
py -3.12 -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e .Environment
Set these variables in your MCP client config or shell:
$env:AVIZO_HOME = "C:\Program Files\Thermo Scientific Amira-Avizo3D 2024.1"
$env:AVIZO_MCP_WORKDIR = "C:\Users\<you>\Documents\avizo_mcp_jobs"Optional overrides:
$env:AVIZO_EXE = "C:\Path\To\Avizo3D.exe"
$env:AVIZO_TO_GO_EXE = "C:\Path\To\AvizoToGo.exe"
$env:AMIRA_EXE = "C:\Path\To\Amira3D.exe"
$env:AVIZO_PYTHON_EXE = "C:\Path\To\python.exe"Run Manually
.\.venv\Scripts\python.exe -m avizo_mcp.serverThe server uses stdio transport for MCP clients.
Codex MCP Config
Use examples/codex_mcp_config.toml as a template. Replace paths with your local clone, venv Python, Avizo installation, and job workdir.
Skill
The reusable Codex skill lives at skills/avizo. To install it manually, copy that folder into your Codex skills directory, for example:
Copy-Item -Recurse .\skills\avizo "$env:USERPROFILE\.codex\skills\avizo"Restart Codex after installing or changing the MCP config.
Safety Notes
Treat raw CT,
.am, and.hxexperiment folders as read-only unless a user explicitly asks for in-place edits.Generate scripts and logs in
AVIZO_MCP_WORKDIR.For long Avizo jobs, launch with
wait=falseand inspect logs before claiming success.Review generated
.pyscroand.rcfiles in a disposableAMIRA_LOCALlayout before installing them into a production Avizo setup.
Publishing Notes
Choose an open-source license before publishing this repository. Do not vendor third-party Amira-Avizo automation code unless its license and attribution are handled.
Available Tools
12 toolscreate_hx_scriptC
Create a timestamped Avizo .hx script under the MCP work directory.
Inputs: content (required), job_name, filename. Returns: object
create_python_scriptC
Create a Python script under the MCP work directory for Avizo Python runs.
Inputs: content (required), job_name, filename. Returns: object
create_python_script_objectC
Create an Amira-Avizo .pyscro script-object skeleton and matching .rc registration.
Inputs: module_name (required), script_body, category, primary_type, +1 more. Returns: object
get_avizo_installationA
Report local Amira-Avizo paths used by this MCP server.
Inputs: no named parameters. Returns: object
inspect_hx_scriptB
Read the start of an Avizo .hx script and summarize common commands.
Inputs: script_path (required), max_lines. Returns: object
inventory_avizo_projectC
Inventory an Avizo/Amira project tree and classify common files.
Inputs: root_path (required), max_files. Returns: object
launch_avizoC
Launch an Avizo executable with optional command-line arguments.
Inputs: executable, args, wait, timeout_sec, +1 more. Returns: object
list_demo_projectsC
List bundled Avizo .hx demo projects.
Inputs: limit, contains. Returns: object
list_hx_scriptsC
List .hx scripts in a project tree with basic metadata.
Inputs: root_path (required), contains, limit. Returns: object
read_job_logC
Read a log file produced by this MCP server.
Inputs: log_path (required), max_chars. Returns: object
run_avizo_pythonC
Run a Python script using Avizo's bundled Python interpreter.
Inputs: script_path (required), args, wait, timeout_sec, +1 more. Returns: object
run_hx_scriptC
Launch Avizo or AvizoToGo with a .hx script path.
Inputs: script_path (required), executable, extra_args, wait, +2 more. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose: creating different script types, launching, running, inspecting, listing, and reading logs. No overlapping functionality.
All tools use a consistent verb_noun pattern in snake_case, such as create_hx_script, launch_avizo, list_hx_scripts. The naming style is uniform and predictable.
12 tools is a well-scoped count for an Avizo MCP server, covering script creation, execution, project inspection, and configuration without being excessive or insufficient.
The tool set covers creation, execution, inspection, and listing of scripts and projects, but lacks update or delete operations for scripts, which are minor gaps.
Related MCP Connectors
Control Unreal Engine to browse assets, import content, and manage levels and sequences. Automate…
Search, read, and automate TextMine documents, records, workflows, integrations, and agent tasks.
Build, check and report on MIDAS CIVIL NX bridge models through the MIDAS IT Europe plugins.
Manage SysML2 projects; check, evaluate, verify, query, document and diagram models.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables building and modifying parametric solid models in a local SOLIDWORKS installation via the COM API.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients like Codex to control Ansys Workbench and ICEM CFD locally, executing scripts, managing projects, and running simulations.1MIT
- FlicenseCqualityBmaintenanceBridges with an installed API monitoring application to enable launching and status checks, live background capture, process attach, filter-tree inspection, GUI actions, and opening, validating, decoding, searching, inspecting, exporting, and comparing saved captures and related metadata.593-
- AlicenseAqualityCmaintenanceEnables headless control of DHI MIKE Zero, including launching and batch-running simulations, monitoring job progress and logs, and reading/plotting simulation results from DFS and RES1D files.15MIT