surfer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SURFER_MCP_VISIBLE | No | Set to 1 to show Surfer, or 0 to launch it in the background. | 1 |
| SURFER_MCP_WORKSPACE | No | Working directory: relative tool paths are resolved within it. | %USERPROFILE%\Documents\SurferMCP (or ~/SurferMCP) |
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 |
|---|---|
| surfer_statusA | Report Surfer availability, version, visibility, workspace and open document count. |
| list_documentsA | List the documents currently open in Surfer with their index, name, path and saved state. |
| set_surfer_visibleA | Show or hide the Surfer application window. Surfer starts automatically if needed. |
| create_gridB | Interpolate XYZ point data into a binary Surfer grid (.grd). Args: data_file: CSV, TSV or whitespace text file containing X, Y, Z columns. output_grid: Destination .grd path (workspace-relative or absolute). Defaults to grids/.grd. x_col: 1-based X column. y_col: 1-based Y column. z_col: 1-based Z column. algorithm: Gridding algorithm; kriging by default. cols: Grid columns (10-4000). rows: Grid rows (10-4000). |
| create_contour_mapB | Create a map from a .grd grid in a new Surfer plot document. Args: grid_file: Input .grd grid. title: Optional map title. style: "color" renders a coloured raster with contour lines, "lines" draws plain contours, "filled" fills contours (grayscale in Surfer 13). output_image: Optional export path; format inferred from extension (png, jpg, pdf, tif, svg, emf). save_plot: Optional .srf plot path. |
| create_cross_sectionA | Create a geological cross-section along a straight line through a grid. The plot combines a location map (with the section line) and a profile below it. Args: grid_file: Input .grd grid. start_x: Section start X in map units. start_y: Section start Y in map units. end_x: Section end X in map units. end_y: Section end Y in map units. title: Section title, e.g. "A-A'". style: Map style behind the section: "color", "lines" or "filled". vertical_exaggeration: Vertical scale factor (1.0 = true scale). x_label: Horizontal axis label. y_label: Vertical axis label. output_image: Optional export path (png, jpg, pdf, tif, svg, emf). save_plot: Optional .srf plot path. save_profile_data: Optional tab-delimited .dat path for the sampled profile values. |
| create_surface_mapC | Create a 3D surface view from a .grd grid. |
| export_documentA | Export an open Surfer document to png, jpg, pdf, tif, svg or emf. Args: output_file: Destination path; the extension selects the export filter. document: Document name, 1-based index, or "active". |
| save_plotC | Save an open Surfer document as a .srf plot file. |
| close_documentC | Close an open Surfer document, optionally saving it first. |
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 10 tools
The three map-producing tools (create_contour_map, create_surface_map, create_cross_section) share the same input (a .grd grid) but their descriptions make the distinct outputs clear. The only real friction is export_document vs. save_plot, since 'save_plot' also appears as a parameter name inside the create_* tools, which could momentarily confuse selection.
Nine of ten tools follow a clean verb_noun pattern (list_documents, create_grid, export_document, close_document, etc.). The outlier is surfer_status, which uses a noun-first form instead of something like get_status or report_status.
Ten tools is a well-scoped surface for driving a desktop gridding/mapping application: three lifecycle/document tools, one data-to-grid tool, three map builders, and three output tools. Every tool maps to a distinct step in the workflow and none feel redundant.
The core pipeline (XYZ data -> grid -> map -> export/save -> close) is fully covered, plus status and visibility control. The notable gap is an open_document tool for re-opening existing .srf plots, and there is no way to inspect or delete saved workspace files, but agents can work around these by regenerating plots.