Skip to main content
Glama
Vulcan MCP

Vulcan MCP

by LuiccianDev

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VULCAN_MCP_HOSTNoOptional 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_TOKENNoOptional 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
vulcan_systemA

Master tool for Vulcan connectivity, active mine project inventory, and SDK capabilities.

Actions:

  • ping: Check live connection to Maptek Vulcan Desktop.

  • project_info: List all block models (.bmf), triangulations (.00t/.tri), design DBs (.dgd.isis), drillhole DBs (.dhd.isis), specifications (.dsf), and legends (.scd) in the active project.

  • capabilities: Inspect available Python modules inside Vulcan (pandas, PIL, win32gui).

vulcan_block_modelA

Master tool for inspecting and querying Vulcan block models (.bmf).

Actions:

  • list: List all .bmf files in the project.

  • info: Get block model origin, extent, block sizes, total blocks, and variable definitions (requires model).

  • query_xyz: Read block grades/attributes at world coordinates (model, x, y, z, optional variables).

  • stats: Compute grade-tonnage statistics, volume-weighted mean, and cutoff summary (model, variable, optional cutoff, density, select).

vulcan_triangulationA

Master tool for 3D triangulations, topography surfaces, and pit shells (.00t / .tri).

Actions:

  • list: List all triangulation files in the project.

  • info: Return node count, face count, 3D bounding box extent, closure/consistency/crossing state, centroid, and volume (name).

  • elevation: Query surface Z elevation at [[x, y], ...] coordinates (name, points).

  • point_inside: Check whether 3D coordinates [[x, y, z], ...] lie inside a closed triangulation solid (name, points).

  • load: Display triangulation on Vulcan's 3D graphics screen (name).

  • unload: Remove triangulation from Vulcan's 3D graphics screen (name).

vulcan_designA

Master tool for Vulcan Design Databases (.dgd.isis), layers, and 3D CAD polylines.

Actions:

  • list_dbs: List all .dgd.isis databases in the project.

  • list_layers: List all layers and object counts inside a DGD (dgd).

  • layer_info: Inspect objects inside a layer with pagination (dgd, layer, optional limit, offset).

  • load_layer: Render a design layer onto the 3D screen (dgd, layer, optional use_temp_objects, load_method).

  • clear_temp: Remove temporary CAD objects displayed on the 3D screen.

  • create_polyline: Create a 3D polyline or closed polygon in a layer (dgd, layer, points, optional closed, colour, name).

vulcan_drillholesA

Master tool for ISIS Drillhole Databases (.dhd.isis): collars, surveys, assays, lithology, and 3D display.

Actions:

  • list_dbs: List all drillhole databases in the project.

  • schema: Return tables (e.g. COLLARES, DIRECCIONES, LEYES, LITOLOGIA), fields, string_fields, and total hole count (db).

  • holes: Paginated list of drillhole IDs (db, optional limit, offset).

  • hole: Get collar, survey, assay, and lithology records for a single hole (db, hole, optional table).

  • high_grade: Scan an interval table for the highest-grade intercepts (db, table, field, min_value, limit).

  • display: Render 3D drillholes in Vulcan's 3D viewport colour-coded by grade (db, optional holes, table, field, limit, max_segments, mode, save_layer).

  • clear_display: Remove rendered 3D drillholes from Vulcan's 3D viewport.

vulcan_legendA

Master tool for reading and updating Maptek Envisage colour legends (.scd).

Actions:

  • list: List .scd legend files and available colour presets.

  • inspect: Parse all schemes (BLOCK_COLOUR, DRILL_COLOUR, SAMPLES_COLOUR) in a legend (scd).

  • update: Update interval colours of a legend table (scd, scheme, table, and preset or colours). Automatically creates a .scd.bak backup.

  • restore: Restore a legend from its .scd.bak backup (scd).

vulcan_screenshotA

Capture the Maptek Vulcan 3D window as a compressed JPEG image.

Downscales to max_width (default 800px) and encodes as JPEG (quality=70) to minimise token consumption while preserving clear visual context of the 3D scene.

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 (vulcan and vulcan_gui preloaded).

Assign to result inside your snippet to return structured JSON values alongside stdout/stderr.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 9 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityNo data
ResponsivenessOutdated data