visio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VISIO_MCP_MOCK | No | force the headless mock engine | 0 |
| VISIO_MCP_ATTACH | No | attach to a running Visio instance; 0 = always launch a dedicated instance (more deterministic) | 1 |
| VISIO_MCP_VISIBLE | No | show the Visio window | 0 |
| VISIO_MCP_DOT_MASTER | No | junction-dot master name | Point |
| VISIO_MCP_KEEP_ALIVE | No | keep the launched Visio instance after exit | 0 |
| VISIO_MCP_LABEL_FONT | No | default label font | Arial |
| VISIO_MCP_LABEL_SIZE | No | default label size | 10pt |
| VISIO_MCP_DOT_STENCIL | No | junction-dot stencil (e.g. RFIC_lib.vss) | |
| VISIO_MCP_WIRE_WEIGHT | No | default wire weight | 1.5 pt |
| VISIO_MCP_STENCIL_DIRS | No | ;-separated stencil search dirs for list_stencils |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Check server and Visio connection health. |
| new_documentA | Create a new blank Visio document; page is scaled 1:1 so coordinates are inches. Returns the document name. |
| open_documentA | Open an existing Visio document (.vsdx). |
| save_documentA | Save the current document (optionally to a new path). |
| close_documentC | Close the current document. |
| list_pagesA | List pages in the current document. |
| add_pageC | Add a new page and select it. |
| select_pageC | Select a page by name. |
| list_stencilsA | List Visio stencil files (.vss/.vssx/.vssm) found in the configured
stencil directories (VISIO_MCP_STENCIL_DIRS) or in |
| load_stencilA | Open a stencil file. If the file is locked by another Visio session, a temporary copy is opened instead. Returns a stencil key for drop_master. |
| list_mastersB | List all masters (symbols) in a stencil file, with shape counts. |
| drop_masterB | Drop a stencil master at (x, y) in inches. Returns shape_id. |
| draw_wireA | Draw an orthogonal polyline through a list of [x, y] points (inches). Each consecutive pair becomes a straight segment. Returns shape ids. |
| add_labelB | Add a centered text label (borderless, transparent) at (x, y). |
| add_junctionA | Place a solid junction dot at (x, y) for >=3-wire nodes. |
| set_line_weightA | Set LineWeight (e.g. '1.5 pt') on a shape and its sub-shapes. |
| delete_shapeB | Delete a shape by id. |
| find_shapeB | Find the first shape whose text contains |
| list_shapesA | List all shapes on the current page: id, master, text, position. |
| export_pageA | Export the current page to a file. fmt: png, jpg, gif, bmp, tif, svg, emf, pdf, vsdx. Returns the written path. |
| measured_pinsA | List stencil masters with measured pin geometry available. |
| pin_pointA | Absolute page coordinate (inches) of a symbol pin, based on measured geometry. Example: pin_point('NMOS1', 4.3, 6.0, 'gate') -> [4.049, 6.0]. Use the result as the endpoint of draw_wire so wires land on pins. |
| symbol_boundsA | Absolute ink bounding box of a symbol body (inches) for clearance checks — keep wires out of it. |
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 23 tools
Each tool targets a distinct resource/action, such as document lifecycle vs page management vs stencil operations vs shape operations. The geometry helpers (measured_pins, pin_point, symbol_bounds) are related but serve clearly different query purposes, so no two tools are ambiguous.
Most tools follow a verb_noun pattern (new_document, open_document, list_pages, drop_master, export_page) with consistent style. A few names deviate, such as health_check (object_verb) and measured_pins, pin_point, symbol_bounds (noun/adjective phrases), but the overall pattern is readable and predictable.
With 23 tools, the server feels heavy for a single MCP, though each tool serves a specific purpose within the broad Visio automation domain. The count is above the typical well-scoped range (3-15), but the tools are distributed across document, page, stencil, shape, drawing, and export concerns, so it is borderline rather than excessive.
The core workflow of creating, editing, and exporting diagrams is covered well: document CRUD, page management, stencil loading, master placement, drawing wires/labels/junctions, and export. However, there is no general shape property editor (only line weight), no text updating, no move/rotate/group operations, and no fill/color settings, which are notable gaps for a full Visio automation tool.