OpenVSP MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENVSP_BIN | No | Path to the OpenVSP binary | vsp |
| VSPAERO_BIN | No | Path to the VSPAero binary | vspaero |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| openvsp.inspectA | Describe an OpenVSP geometry without modifying it. Returns component IDs and raw info. |
| openvsp.modifyB | Apply scripted parameter edits to an OpenVSP model without running VSPAero. Use set_commands to adjust geometry; returns the generated script path. |
| openvsp.run_vspaeroC | Run OpenVSP edits followed by VSPAero. Provide geometry commands and case_name. |
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 3 tools
Each tool has a clearly distinct purpose: inspect is for describing geometry, modify is for applying parameter edits, and run_vspaero is for running edits followed by VSPAero. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent pattern with the prefix 'openvsp.' and a descriptive action suffix (inspect, modify, run_vspaero). This verb-based naming is uniform and predictable, enhancing usability and clarity across the tool set.
With only 3 tools, the set feels thin for a server focused on OpenVSP geometry and VSPAero analysis. While it covers core operations, it may lack depth for more advanced workflows, such as managing multiple models or handling specific analysis outputs, which could limit agent capabilities.
The tools provide a basic workflow for inspecting, modifying, and running analyses on OpenVSP models, covering key operations. However, there are minor gaps, such as no tools for creating new models, saving/loading files, or accessing detailed VSPAero results, which agents might need to work around.