How It Works
The plugin runs a small local bridge inside the editor. The cfa CLI and MCP server connect over a local port; nothing leaves your machine except the license check.
Loading…
The plugin runs a small local bridge inside the editor. The cfa CLI and MCP server connect over a local port; nothing leaves your machine except the license check.
The plugin runs a small local bridge inside the editor. The cfa CLI and the MCP server connect to that bridge over a local port and send commands. Nothing leaves your machine except the single license check.
cfa health_check does more than say yes. It reports the editor it reached: project name, the full .uproject path, the engine version, the process id, and the port. Read it to be sure you are driving the editor you mean. If no editor is up it returns a clear "status": "error" telling you to open one.
Confirm the bridge and see which editor you reached:
cfa health_check{
"result": {
"project_name": "jiggi",
"project_path": ".../jiggi.uproject",
"engine_version": "5.8.0",
"pid": 39524,
"port": 55557
},
"status": "success"
}