The Siemens Amesim doc server (amesim-vendor-docs) on 2511, and the modeling server that does not start

Run status: EXERCISED 2026-09-03 on Simcenter Amesim 2511.

The Siemens "Simcenter AI Agents" package (a Goose fork, nine product bundles, reviewed 2026-09-03) ships an Amesim bundle with two MCP servers. One of them runs on 2511 and is now part of this workspace; the other does not start on 2511.

The doc server runs on 2511

• Installed at D:\apps\sim-ai-agents\amesim-vendor-docs\ and registered as the MCP server amesim-vendor-docs (in xcelerator-workspace/.mcp.json.template and the generated .mcp.json).
• Two tools: search_docs and get_doc_file.
• search_docs is SQLite FTS5 full-text search over the install's own documentation index.db. The first call builds the index, about 17 seconds; later calls are immediate.
• The bundle targets Amesim 2604, but the doc server reads whatever index the installed release carries, so it runs against 2511's documentation set unchanged.

It is distinct from the amesim-docs MCP server, which searches this knowledge base (the Support Center harvest). Use amesim-vendor-docs for the shipped reference text of a submodel or API call; use amesim-docs for the curated and community material here.

The modeling server does not start on 2511

The bundle's Amesim modeling server (the AMEOpen-backed executable) is built for 2604 and does not start on 2511: its bundled Python clashes with the 2511 AMEOpen pyd. Its tool surface was reimplemented instead in amesim-mcp/amesim_open.py on the ameopen_headless_direct_py module that ships inside 2511. See AMEOpen headless API on 2511. The exact tool contracts were recovered by dumping the bundle's bytecode docstrings with Amesim's Python 3.12.

Provenance and licence notes

The bundle's skills carry Siemens AG "proprietary and confidential" headers: use as a specification, never copy. The launcher points at a pre-production identity service and the Amesim bundle hard-codes a Siemens-internal licence fallback, neither of which is used here. The lesson that generalises: when a Siemens bundle targets a newer release than the one installed, check whether the underlying API ships in the installed release before writing it off. It did here.