In the editor
Open a saved .aimbox. The AI connection wizard stays disabled until the document is saved.
AI → Start MCP server. Or finish AI → AI Connection… and start MCP from the wizard.
Pick the client you actually use (Cursor, Codex, Claude, Copilot, Antigravity, Other). Files are written in the project folder (git root). AIMEDITOR does not write home-global MCP config.
What the connection does
The AI does not open AIMEDITOR itself. It runs AIMBOX.Mcp.Bridge and uses pipeName in aimbox-mcp.connection.json to reach the editor pipe.
Restarting the editor changes the pipe name. The editor rewrites the project connection JSON. Restart the AI session too.
An AI that is not in the list
If that AI is an MCP client and can launch a stdio server, it can attach. Use the same contents the wizard writes for Other (.mcp.json).
Server id AIMBOX, command = installed AIMBOX.Mcp.Bridge.exe, env VSX200_MCP_CONNECTION = absolute path to that project’s aimbox-mcp.connection.json.
If the client wants servers instead of mcpServers, or type: stdio, match that shape. Chat-only products without MCP cannot connect.
Check
Cursor CLI: from the project folder, agent --approve-mcps then agent mcp list → aimbox: ready.
Codex: trust the folder, then codex mcp list.
Claude Code: AIMBOX in the project MCP list.
Antigravity: AIMBOX inside agy.
Ollama: ollmcp reading .mcp.json. This is not the Ollama app chat window.