Schema | Ansys Research Runner MCP

Ansys Research Runner MCP

Describes the environment variables required to run the server.

Name	Required	Description	Default
`ANSYS_RESEARCH_ANSYS_ROOT`	No	Path to a nonstandard Ansys installation root to use for the current process. Standard installations are discovered automatically.

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.

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`	{}

Functions exposed to the LLM to take actions

Name	Description
doctorC	Report installed host and PyAnsys capabilities.
inspect_modelC	Inspect one confined supported CAD model into a Geometry Graph.
resolve_regionsC	Resolve semantic regions referenced by one Run Recipe.
validate_runB	Validate one Run Recipe and all referenced contracts.
plan_runC	Compile a supported recipe into immutable reviewed CAE-IR.
start_runA	Enqueue a run and immediately return its durable QUEUED snapshot.
get_run_statusC	Return a job snapshot and its append-only event history.
cancel_runC	Request safe cancellation through the Job Registry.
get_run_summaryC	Return bounded scalar results without any field arrays.
list_run_artifactsB	List artifact paths, hashes, media types, and sizes only.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/miziyo/ansys-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server