An MCP server allowing LLMs to interact with Ansys/AGI STK - Digital Mission Engineering Software
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"stk-mcp": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP server allowing LLMs to interact with Ansys/AGI STK - Digital Mission Engineering Software
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Pi Coding Agent extension (CLI-first) — routes bash/read/grep/find/ls through lean-ctx CLI for strong token savings. Optional MCP bridge can register advanced tools.
Apify MCP Server
97% token reduction for AI coding sessions — zero deps, 21 languages, MCP server
MCP proxy that compresses prose fields (tool descriptions, etc.) using caveman rules. Same accuracy, fewer context tokens.
MCP Security Weekly
Get CVE alerts and security updates for Stk Mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
STK-MCP is an MCP (Model Context Protocol) server designed to enable Large Language Models (LLMs) or other MCP clients to interact with Ansys/AGI STK (Systems Tool Kit) - the leading Digital Mission Engineering software.
This project allows controlling STK via an MCP server, supporting both STK Desktop (Windows only) and STK Engine (Windows & Linux). It utilizes FastMCP from the official MCP Python SDK.
The primary goal of this project is to bridge the gap between programmatic interaction and the powerful simulation capabilities of STK. By exposing STK functionalities through a robust CLI and an MCP server, users can command STK simulations using simple commands or LLM-driven applications.
The MCP application, defined in src/stk_mcp/app.py, exposes STK operations as MCP tools, which are dynamically managed by a CLI entry point in src/stk_mcp/cli.py.
Typer.list-tools command enumerates available MCP tools.cli.py), MCP (app.py), STK logic (stk_logic/), and MCP tools (tools/).agi.stk12 Python wheel corresponding to your STK installation must be available. Typically found under CodeSamples\Automation\Python in your STK install.git clone <repository-url>
cd stk-mcp
# Create the virtual environment
uv venv
# Activate it
# On Windows (in PowerShell/CMD):
# .venv\Scripts\activate
# On Linux (in bash/zsh):
source .venv/bin/activate
uv add ./agi.stk12-12.10.0-py3-none-any.whl
# or: uv add path/to/your/STK/CodeSamples/Automation/Python/agi.stk12-*.whl
pyproject.toml)
uv sync
This project is a command-line application. Ensure your virtual environment is activated before running commands.
uv run -m stk_mcp.cli list-tools
Prints a table of tool names and their descriptions.
Use the run command to start the MCP server. The server will automatically start and manage an STK instance.
Run with uv run so you don’t need to install the package into site-packages.
1) STK Engine (recommended for automation, Windows/Linux):
uv run -m stk_mcp.cli run --mode engine
2) STK Desktop (Windows only, shows GUI): Ensure STK Desktop is closed; the server will launch and manage its own instance.
uv run -m stk_mcp.cli run --mode desktop
The server will start, initialize STK, and listen for MCP connections on http://127.0.0.1:8765 by default.
3. Command Options:
You can see all options with the --help flag:
stk-mcp run --help
Once the server is running, you can connect to it using any MCP client, such as the MCP Inspector.
http://127.0.0.1:8765).