SE MCP For Plugin Dev Server

This MCP Server enables AI-assisted Space Engineers plugin development by providing a decompiled game index and an HTTP transport to connect coding agents from your IDE or remote hosts. It streamlines building, testing, and iterating on plugins with AIly enhanced code indexing and automatic session management.

How to use

You connect your MCP client to the server via HTTP or run a local stdio server that your IDE can launch. Start by running the built-in HTTP transport to expose the MCP endpoint locally, then attach your coding agent from within your editor. The difference between HTTP transport and a local stdio server is how the MCP client connects: HTTP uses a URL you can reach from any machine, while stdio runs a local process started by the editor.

How to install

Prerequisites you need installed on Windows x64 with .NET 8.0 SDK and Git for tooling are:

• Space Engineers installed via Steam
• .NET 8.0 SDK (Windows x64)
• ILSpy 8.2.0.7535 (install via SetupILSpy.bat)
• Python 3.12 or newer
• Git
• At least 1GB free disk space

Ensure these executables are available on your PATH:

• ilspycmd
• python
• git

Define this environment variable for the game root directory:

SPACE_ENGINEERS_ROOT should point to your Space Engineers install path, for example:

SPACE_ENGINEERS_ROOT=C:\\Program Files (x86)\\Steam\\steamapps\\common\\SpaceEngineers"}]} ,{

Additional notes and configuration

Prepare the game decompilation and code index so your editor can index the decompiled game data for AI-assisted coding. Run the preparation script; it decompiles the game and installs the code index. When it finishes, you should see DONE.

To run the MCP server over HTTP for external access, the preparation step creates a batch file named HttpServer.bat. Use it to start the HTTP transport. Your MCP client can connect to the local endpoint at 127.0.0.1:8000.

Test the HTTP endpoint in a browser or with a client: http://127.0.0.1:8000/sse/ should respond with an event stream header (event: endpoint). This confirms the server is reachable and serving Server-Sent Events.

If you want to expose the MCP server to the internet, you can forward 127.0.0.1:8000 to a public hostname and wrap it in HTTPS via a reverse proxy. Whitelist your public hostname in your chosen MCP client settings to allow remote connections.