Connect to the real
Aether MCP engine.
This connection panel targets the native C++ AetherMCP server from checkpoint CP143—not a replacement game engine or scene-only mock API. Your engine runs in a private workspace on your computer. Browser game exports and native editor connections have separate requirements.
Build browser games with your AI.
Use the browser-project MCP setup and download. Connect to the public hosted MCP with your Model J Labs account, or use the local Node.js package. Both support 2D and shared 3D authoring, runtime tests and playable web export without the native desktop engine. The connection below is for native C++ projects.
Native MCP connection
Launch AetherMCP with the authenticated local HTTP bridge, then connect here. The token is sent only to your own loopback server by this page; it is not included in the site's requests or saved to browser storage.
<workspace>/.mcp-state/http-tokenDisconnected · Run your local MCP server to connect.
Start your real MCP server
- Obtain the matching CP143 native server kit for your operating system.
- Make a private Aether project folder.
- Start its MCP server. For the Linux CP143 connection kit use:
node run-server.mjs --workspace "/absolute/Aether Projects" --port 32190 --origin https://modeljlabs.com
The bridge generates a private random token and listens only on 127.0.0.1:32190. It does not expose your filesystem or engine on the public Internet.
Windows requires a CP143-matching AetherMCP.exe built from the CP143 native source. An older installed CP139 runtime must not silently be treated as compatible.
What this actually connects
When the native process responds, the panel asks the server for its MCP tool registry and aether_runtime_capabilities. You can then use compatible MCP clients to create or edit actual saved native scenes, run physics and gameplay simulations, and request native or web builds. Connecting this process alone does not establish a live editor: that requires a separate acknowledged, matching --editor-bridge connection.
For MCP clients that support stdio
{"mcpServers":{"aether":{"command":"/absolute/path/AetherMCP","args":["--workspace","/absolute/Aether Projects"]}}}Aether's local HTTP transport uses MCP Streamable HTTP (2025-03-26), bearer authentication, and a one-hour idle session lifetime. This site does not claim a hosted multi-user native engine.
CP143 status: real native tool discovery and local HTTP authentication have been tested; the separate CP143 browser gameplay export is available here. The public web editor has a separate deployment version and must not be represented as the CP143 native editor until the matching editor build is published.