Skip to main content
Glama

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 .hx workflows and extract command patterns plus referenced files;

  • create reproducible .hx and Python scripts in a job directory;

  • generate .pyscro plus .rc script-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 metadata

Related 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.server

The 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 .hx experiment 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=false and inspect logs before claiming success.

  • Review generated .pyscro and .rc files in a disposable AMIRA_LOCAL layout 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 tools
create_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

    B3.2/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: creating different script types, launching, running, inspecting, listing, and reading logs. No overlapping functionality.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables building and modifying parametric solid models in a local SOLIDWORKS installation via the COM API.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients like Codex to control Ansys Workbench and ICEM CFD locally, executing scripts, managing projects, and running simulations.
      1
      MIT
    • F
      license
      C
      quality
      B
      maintenance
      Bridges 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.
      59
      3
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      15
      MIT