Avizo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AMIRA_EXE | No | Path to Amira3D.exe (optional override) | |
| AVIZO_EXE | No | Path to Avizo3D.exe (optional override) | |
| AVIZO_HOME | Yes | Path to the Avizo/Amira installation directory (e.g., C:\Program Files\Thermo Scientific Amira-Avizo3D 2024.1) | |
| AVIZO_TO_GO_EXE | No | Path to AvizoToGo.exe (optional override) | |
| AVIZO_PYTHON_EXE | No | Path to bundled Python executable (optional override) | |
| AVIZO_MCP_WORKDIR | Yes | Directory for job scripts and logs (e.g., C:\Users\<you>\Documents\avizo_mcp_jobs) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_avizo_installationA | Report local Amira-Avizo paths used by this MCP server. |
| list_demo_projectsC | List bundled Avizo |
| inventory_avizo_projectC | Inventory an Avizo/Amira project tree and classify common files. |
| list_hx_scriptsC | List |
| inspect_hx_scriptB | Read the start of an Avizo |
| create_hx_scriptC | Create a timestamped Avizo |
| create_python_scriptC | Create a Python script under the MCP work directory for Avizo Python runs. |
| create_python_script_objectC | Create an Amira-Avizo |
| launch_avizoC | Launch an Avizo executable with optional command-line arguments. |
| run_hx_scriptC | Launch Avizo or AvizoToGo with a |
| run_avizo_pythonC | Run a Python script using Avizo's bundled Python interpreter. |
| read_job_logC | Read a log file produced by this MCP server. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.