Vulcan MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VULCAN_MCP_HOST | No | Optional host address for the Vulcan listener. Defaults to loopback. If set to a non-loopback address, VULCAN_MCP_TOKEN must also be defined. | |
| VULCAN_MCP_TOKEN | No | Optional token used to authenticate requests to the Vulcan listener. If set, the same value must be configured in the MCP client environment. Required when VULCAN_MCP_HOST is set to a non-loopback address. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vulcan_systemA | Master tool for Vulcan connectivity, active mine project inventory, and SDK capabilities. Actions:
|
| vulcan_block_modelA | Master tool for inspecting and querying Vulcan block models (.bmf). Actions:
|
| vulcan_triangulationA | Master tool for 3D triangulations, topography surfaces, and pit shells (.00t / .tri). Actions:
|
| vulcan_designA | Master tool for Vulcan Design Databases (.dgd.isis), layers, and 3D CAD polylines. Actions:
|
| vulcan_drillholesA | Master tool for ISIS Drillhole Databases (.dhd.isis): collars, surveys, assays, lithology, and 3D display. Actions:
|
| vulcan_legendA | Master tool for reading and updating Maptek Envisage colour legends (.scd). Actions:
|
| vulcan_screenshotA | Capture the Maptek Vulcan 3D window as a compressed JPEG image. Downscales to |
| vulcan_canvasC | Run a Vulcan Workbench macro command or print a message to Vulcan's Report Window. |
| vulcan_execute_codeA | Execute custom Python code inside Vulcan's active session ( Assign to |
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 9 tools
Each master tool targets a clearly distinct Vulcan domain: system, block models, triangulations, design DBs, drillholes, legends, screenshots, canvas commands, and Python execution. The main ambiguity is between vulcan_canvas (Workbench macro/Report Window) and vulcan_execute_code (custom Python), which could be confused by an agent choosing how to execute arbitrary logic.
All tool names follow a consistent vulcan_ prefix plus a clear domain noun: vulcan_system, vulcan_block_model, vulcan_triangulation, etc. Snake_case is used consistently throughout, and the action names inside the master tools are also predictable.
Nine master tools is a well-scoped surface for a complex mining-software integration. The master-tool pattern groups many related actions under coherent domains rather than exposing dozens of flattened tools, keeping the top-level count manageable.
The surface covers connectivity, project inventory, block-model querying/statistics, triangulation inspection/display, design DB layers and polylines, drillhole inspection/display, legends, screenshots, and code/macro execution. Minor lifecycle gaps remain, such as block-model or triangulation editing/export operations, but core read/query/display workflows are well covered.