STK-MCP

What is STK-MCP?

STK-MCP is an MCP (Model Context Protocol) server that enables Large Language Models or other MCP clients to interact with Ansys/AGI STK (Systems Tool Kit), the leading digital mission engineering software. It supports both STK Desktop (Windows only) and STK Engine (Windows & Linux), using the official MCP Python SDK.

How to use STK-MCP?

Clone the repository, create a virtual environment, add the STK Python wheel from your STK installation, and run uv sync. Then list available tools with uv run -m stk_mcp.cli list-tools and start the server with uv run -m stk_mcp.cli run --mode engine (or --mode desktop on Windows). The server listens on http://127.0.0.1:8765 by default; stop it with Ctrl+C.

Key features of STK-MCP

• CLI powered by Typer for tool listing and server control.
• Dual mode: STK Engine (Windows/Linux) and STK Desktop (Windows).
• OS-aware: desktop mode auto-disabled on non-Windows platforms.
• Managed lifecycle: STK instance started/stopped with the MCP server.
• Tool discovery via list-tools command enumerating available MCP tools.
• Modular architecture separating CLI, MCP app, STK logic, and tools.

Use cases of STK-MCP

• Automate satellite orbit creation and configuration via LLM commands.
• Compute access intervals between satellites and ground facilities.
• Retrieve satellite LLA ephemeris over a scenario period.
• List and inspect objects in an active STK scenario.
• Set up and manage STK scenarios programmatically from an MCP client.

FAQ from STK-MCP

What operating systems are supported?

STK Engine mode works on Windows and Linux. STK Desktop mode requires Windows. macOS is not supported; STK-dependent tools will be unavailable.

What prerequisites are needed?

Python 3.12 or higher, Ansys/AGI STK version 12.x (Desktop or Engine), and the corresponding agi.stk12 Python wheel from your STK installation.

How does STK-MCP handle concurrent access?

STK access is serialized with a global lock to avoid concurrency issues with multi-threaded access to the STK instance.

Does the server manage the STK lifecycle?

Yes. The server automatically starts an STK instance when launched and closes it when the server is stopped (e.g., via Ctrl+C).

What transport and default settings does the server use?

The MCP server listens on HTTP at 127.0.0.1:8765 by default, configurable via environment variables with the STK_MCP_ prefix. No authentication is described.