MCP server for controlling SAP2000 from AI agents, built on the PySap2000 SDK
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"sap2000-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# sap2000-mcp-server An **MCP (Model Context Protocol)** server for controlling **SAP2000** from AI agents such as Claude Desktop, Codex, and Cursor. Built on the [PySap2000](https://github.com/JIANGYAO-AISA/PySap2000) SDK. > **Status: placeholder / name reservation.** > Active development is in progress. This release reserves the package name on PyPI; it is not yet functional. > Track progress at the [GitHub repository](https://github.com/HeisenbergJY1/sap2000-mcp-server). ## Planned architecture - **Transport**: STDIO (local AI clients) in V1; Streamable HTTP (remote) in V2 - **Engine**: PySap2000 SDK (only path to SAP2000 COM — no raw COM from MCP layer) - **Runtime**: Single COM worker thread with a request queue (SAP2000 COM is STA-bound) - **Philosophy**: Workflow-oriented tools, not 1:1 OAPI mappings; stateless server; dry-run human-in-the-loop for write operations ## Platform requirements - Windows 10+ (SAP2000 COM is Windows-only) - SAP2000 v24+ - Python 3.10+ ## License MIT
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.