paraview-mcp-python 0.1.2__tar.gz → 0.1.4__tar.gz

{paraview_mcp_python-0.1.2 → paraview_mcp_python-0.1.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: paraview-mcp-python
-Version: 0.1.2
+Version: 0.1.4
 Summary: MCP server for controlling ParaView via AI assistants
 Project-URL: Homepage, https://github.com/djeada/paraview-mcp-server
 Project-URL: Repository, https://github.com/djeada/paraview-mcp-server
@@ -50,18 +50,21 @@ paraview-mcp-server
 
 ## What Parts Are There?
 
-There are three moving pieces:
+There are four moving pieces in the GUI workflow:
 
 | Part | Runs where | Purpose |
 |---|---|---|
 | **MCP client** | Codex CLI, Claude Desktop, or another MCP host | Starts the MCP server and calls tools. |
 | **MCP server** | Normal Python environment | Speaks MCP over stdio and forwards tool calls to ParaView over TCP. |
-| **ParaView GUI bridge** | Already-open ParaView GUI process | Receives TCP JSON commands and executes `paraview.simple` operations in that live GUI session. |
+| **ParaView bridge** | `pvpython` process | Receives TCP JSON commands and executes `paraview.simple` operations. |
+| **ParaView runtime** | `pvserver` plus a ParaView GUI client | Owns the shared ParaView session that the GUI and bridge both use. |
 
-The ParaView bridge is the ParaView-side component. It plays the same role as
-the Blender add-on in `blender-mcp-server`: it must run inside the application
-you want to control. For live GUI control, start the bridge from ParaView's
-Python Shell using `scripts/start_paraview_gui_bridge.py`.
+ParaView is not Blender: Python plugins and VTK timer callbacks are pipeline
+extension mechanisms, not a safe general-purpose remote-control hook for a live
+GUI process. The supported GUI workflow here uses ParaView's client/server
+model. `paraview-mcp-launch` starts a local `pvserver`, connects the ParaView
+GUI as the first client, then connects a `pvpython` bridge client to the same
+session.
 
 ```
 ┌──────────────────────────────┐      stdio      ┌────────────────────────┐
@@ -72,24 +75,24 @@ Python Shell using `scripts/start_paraview_gui_bridge.py`.
                                                               │ 127.0.0.1:9876
                                                    ┌──────────▼─────────────┐
                                                    │ ParaView Bridge        │
-                                                   │ live GUI process       │
+                                                   │ pvpython client        │
                                                    └──────────┬─────────────┘
-                                                              │
+                                                              │ ParaView client/server
                                                    ┌──────────▼─────────────┐
-                                                   │ paraview.simple        │
-                                                   │ ParaView runtime       │
+                                                   │ pvserver + GUI client  │
+                                                   │ shared ParaView state  │
                                                    └────────────────────────┘
 ```
 
 Why a ParaView-side bridge? ParaView's useful automation API is
 `paraview.simple`, and it must execute inside a ParaView Python runtime. The
-MCP server itself is only a protocol adapter; it cannot modify a ParaView GUI
-unless the bridge is running inside that GUI process.
+MCP server itself is only a protocol adapter; it cannot modify a ParaView
+session unless a ParaView-side bridge is running.
 
 For live GUI modification, use:
 
 ```text
-Codex/Claude -> MCP server -> bridge inside open ParaView GUI -> live GUI session
+Codex/Claude -> MCP server -> pvpython bridge -> pvserver <- ParaView GUI
 ```
 
 For headless automation, use:
@@ -118,6 +121,7 @@ This installs:
 
 ```bash
 paraview-mcp-server
+paraview-mcp-launch
 ```
 
 ### Option B: Clone this repository for the ParaView bridge
@@ -137,49 +141,37 @@ This creates:
 
 ```bash
 .venv/bin/paraview-mcp-server
+.venv/bin/paraview-mcp-launch
 ```
 
 ---
 
 ## Start Everything
 
-Start the pieces in this order.
+Start the ParaView side with one command:
 
-### 1. Start the ParaView GUI Bridge
-
-Open ParaView, then run the GUI bridge script from the Python Shell:
+```bash
+cd /path/to/paraview-mcp-server
+paraview-mcp-launch
+```
 
-1. In ParaView, open **Tools -> Python Shell**.
-2. Click **Run Script**.
-3. Select:
+For a local editable checkout:
 
-```text
-/absolute/path/to/paraview-mcp-server/scripts/start_paraview_gui_bridge.py
+```bash
+.venv/bin/paraview-mcp-launch
 ```
 
 Expected output:
 
 ```text
-ParaView MCP GUI bridge started on 127.0.0.1:9876
-```
-
-If `paraview-mcp-python` is installed into ParaView's Python environment, you
-can also start the live GUI bridge directly from the Python Shell:
-
-```python
-from bridge.gui_bridge import start_gui_bridge, stop_gui_bridge
-start_gui_bridge()
+ParaView MCP bridge ready on 127.0.0.1:9876
+Launching ParaView GUI connected to cs://127.0.0.1:11111
 ```
 
-Leave ParaView open. MCP commands now modify this live GUI session.
-
-To stop the bridge from the ParaView Python Shell:
-
-```python
-stop_gui_bridge()
-```
+Keep that terminal running. Closing it stops the GUI, bridge, and local
+`pvserver` session.
 
-### 2. Optional: Start a Headless `pvpython` Bridge
+### Optional: Start a Headless `pvpython` Bridge
 
 Use this only when you do not need to modify an already-open ParaView GUI:
 
@@ -197,7 +189,7 @@ ParaView bridge ready on 127.0.0.1:9876
 Keep that terminal running. This controls the `pvpython` session, not a GUI
 window opened separately.
 
-### 3. Verify the Bridge Directly
+### Verify the Bridge Directly
 
 Before involving an MCP client, send one raw bridge command:
 
@@ -219,7 +211,7 @@ Expected response shape:
 
 If this fails, fix the bridge before configuring Codex or Claude.
 
-### 4. Register the MCP Server with Codex CLI
+### Register the MCP Server with Codex CLI
 
 If you installed from PyPI:
 
@@ -238,7 +230,7 @@ codex mcp list
 Codex starts the MCP server automatically when needed. The ParaView bridge
 must already be running separately.
 
-### 5. Register with Claude Desktop
+### Register with Claude Desktop
 
 **Claude Desktop** — add to `claude_desktop_config.json`:
 
@@ -260,7 +252,7 @@ which paraview-mcp-server
 
 Restart Claude Desktop after editing the config.
 
-### 6. Verify Through Your MCP Client
+### Verify Through Your MCP Client
 
 With the bridge still running, ask your MCP client:
 
@@ -269,8 +261,8 @@ List all sources in the current ParaView session.
 ```
 
 The client should call `paraview_scene_list_sources` and return the current
-ParaView pipeline sources from the live GUI session if you started
-`start_paraview_gui_bridge.py`.
+ParaView pipeline sources from the server-backed GUI session started by
+`paraview-mcp-launch`.
 
 ---
 
@@ -480,16 +472,17 @@ paraview-mcp-server/
 │   └── paraview_mcp_server/
 │       ├── __init__.py          # Re-exports main()
 │       ├── server.py            # FastMCP stdio server (31 tools)
+│       ├── launcher.py          # Starts pvserver, GUI, and bridge together
 │       └── headless.py          # Headless pvpython executor + job manager
 ├── bridge/
 │   ├── __init__.py
 │   ├── server.py                # TCP socket bridge server
-│   ├── gui_bridge.py            # Non-blocking live GUI bridge lifecycle
+│   ├── gui_bridge.py            # Experimental in-GUI bridge helpers
 │   ├── command_handler.py       # Command registry + paraview.simple handlers (27 commands)
 │   └── execution.py             # trusted local python.execute helper
 ├── scripts/
-│   ├── start_paraview_gui_bridge.py
 │   ├── start_paraview_bridge.py
+│   ├── start_paraview_gui_bridge.py
 │   ├── paraview_bridge_request.py
 │   └── library/                 # Reusable pvpython snippets
 │       ├── open_dataset.py

{paraview_mcp_python-0.1.2 → paraview_mcp_python-0.1.4}/README.md

@@ -17,18 +17,21 @@ paraview-mcp-server
 
 ## What Parts Are There?
 
-There are three moving pieces:
+There are four moving pieces in the GUI workflow:
 
 | Part | Runs where | Purpose |
 |---|---|---|
 | **MCP client** | Codex CLI, Claude Desktop, or another MCP host | Starts the MCP server and calls tools. |
 | **MCP server** | Normal Python environment | Speaks MCP over stdio and forwards tool calls to ParaView over TCP. |
-| **ParaView GUI bridge** | Already-open ParaView GUI process | Receives TCP JSON commands and executes `paraview.simple` operations in that live GUI session. |
+| **ParaView bridge** | `pvpython` process | Receives TCP JSON commands and executes `paraview.simple` operations. |
+| **ParaView runtime** | `pvserver` plus a ParaView GUI client | Owns the shared ParaView session that the GUI and bridge both use. |
 
-The ParaView bridge is the ParaView-side component. It plays the same role as
-the Blender add-on in `blender-mcp-server`: it must run inside the application
-you want to control. For live GUI control, start the bridge from ParaView's
-Python Shell using `scripts/start_paraview_gui_bridge.py`.
+ParaView is not Blender: Python plugins and VTK timer callbacks are pipeline
+extension mechanisms, not a safe general-purpose remote-control hook for a live
+GUI process. The supported GUI workflow here uses ParaView's client/server
+model. `paraview-mcp-launch` starts a local `pvserver`, connects the ParaView
+GUI as the first client, then connects a `pvpython` bridge client to the same
+session.
 
 ```
 ┌──────────────────────────────┐      stdio      ┌────────────────────────┐
@@ -39,24 +42,24 @@ Python Shell using `scripts/start_paraview_gui_bridge.py`.
                                                               │ 127.0.0.1:9876
                                                    ┌──────────▼─────────────┐
                                                    │ ParaView Bridge        │
-                                                   │ live GUI process       │
+                                                   │ pvpython client        │
                                                    └──────────┬─────────────┘
-                                                              │
+                                                              │ ParaView client/server
                                                    ┌──────────▼─────────────┐
-                                                   │ paraview.simple        │
-                                                   │ ParaView runtime       │
+                                                   │ pvserver + GUI client  │
+                                                   │ shared ParaView state  │
                                                    └────────────────────────┘
 ```
 
 Why a ParaView-side bridge? ParaView's useful automation API is
 `paraview.simple`, and it must execute inside a ParaView Python runtime. The
-MCP server itself is only a protocol adapter; it cannot modify a ParaView GUI
-unless the bridge is running inside that GUI process.
+MCP server itself is only a protocol adapter; it cannot modify a ParaView
+session unless a ParaView-side bridge is running.
 
 For live GUI modification, use:
 
 ```text
-Codex/Claude -> MCP server -> bridge inside open ParaView GUI -> live GUI session
+Codex/Claude -> MCP server -> pvpython bridge -> pvserver <- ParaView GUI
 ```
 
 For headless automation, use:
@@ -85,6 +88,7 @@ This installs:
 
 ```bash
 paraview-mcp-server
+paraview-mcp-launch
 ```
 
 ### Option B: Clone this repository for the ParaView bridge
@@ -104,49 +108,37 @@ This creates:
 
 ```bash
 .venv/bin/paraview-mcp-server
+.venv/bin/paraview-mcp-launch
 ```
 
 ---
 
 ## Start Everything
 
-Start the pieces in this order.
+Start the ParaView side with one command:
 
-### 1. Start the ParaView GUI Bridge
-
-Open ParaView, then run the GUI bridge script from the Python Shell:
+```bash
+cd /path/to/paraview-mcp-server
+paraview-mcp-launch
+```
 
-1. In ParaView, open **Tools -> Python Shell**.
-2. Click **Run Script**.
-3. Select:
+For a local editable checkout:
 
-```text
-/absolute/path/to/paraview-mcp-server/scripts/start_paraview_gui_bridge.py
+```bash
+.venv/bin/paraview-mcp-launch
 ```
 
 Expected output:
 
 ```text
-ParaView MCP GUI bridge started on 127.0.0.1:9876
-```
-
-If `paraview-mcp-python` is installed into ParaView's Python environment, you
-can also start the live GUI bridge directly from the Python Shell:
-
-```python
-from bridge.gui_bridge import start_gui_bridge, stop_gui_bridge
-start_gui_bridge()
+ParaView MCP bridge ready on 127.0.0.1:9876
+Launching ParaView GUI connected to cs://127.0.0.1:11111
 ```
 
-Leave ParaView open. MCP commands now modify this live GUI session.
-
-To stop the bridge from the ParaView Python Shell:
-
-```python
-stop_gui_bridge()
-```
+Keep that terminal running. Closing it stops the GUI, bridge, and local
+`pvserver` session.
 
-### 2. Optional: Start a Headless `pvpython` Bridge
+### Optional: Start a Headless `pvpython` Bridge
 
 Use this only when you do not need to modify an already-open ParaView GUI:
 
@@ -164,7 +156,7 @@ ParaView bridge ready on 127.0.0.1:9876
 Keep that terminal running. This controls the `pvpython` session, not a GUI
 window opened separately.
 
-### 3. Verify the Bridge Directly
+### Verify the Bridge Directly
 
 Before involving an MCP client, send one raw bridge command:
 
@@ -186,7 +178,7 @@ Expected response shape:
 
 If this fails, fix the bridge before configuring Codex or Claude.
 
-### 4. Register the MCP Server with Codex CLI
+### Register the MCP Server with Codex CLI
 
 If you installed from PyPI:
 
@@ -205,7 +197,7 @@ codex mcp list
 Codex starts the MCP server automatically when needed. The ParaView bridge
 must already be running separately.
 
-### 5. Register with Claude Desktop
+### Register with Claude Desktop
 
 **Claude Desktop** — add to `claude_desktop_config.json`:
 
@@ -227,7 +219,7 @@ which paraview-mcp-server
 
 Restart Claude Desktop after editing the config.
 
-### 6. Verify Through Your MCP Client
+### Verify Through Your MCP Client
 
 With the bridge still running, ask your MCP client:
 
@@ -236,8 +228,8 @@ List all sources in the current ParaView session.
 ```
 
 The client should call `paraview_scene_list_sources` and return the current
-ParaView pipeline sources from the live GUI session if you started
-`start_paraview_gui_bridge.py`.
+ParaView pipeline sources from the server-backed GUI session started by
+`paraview-mcp-launch`.
 
 ---
 
@@ -447,16 +439,17 @@ paraview-mcp-server/
 │   └── paraview_mcp_server/
 │       ├── __init__.py          # Re-exports main()
 │       ├── server.py            # FastMCP stdio server (31 tools)
+│       ├── launcher.py          # Starts pvserver, GUI, and bridge together
 │       └── headless.py          # Headless pvpython executor + job manager
 ├── bridge/
 │   ├── __init__.py
 │   ├── server.py                # TCP socket bridge server
-│   ├── gui_bridge.py            # Non-blocking live GUI bridge lifecycle
+│   ├── gui_bridge.py            # Experimental in-GUI bridge helpers
 │   ├── command_handler.py       # Command registry + paraview.simple handlers (27 commands)
 │   └── execution.py             # trusted local python.execute helper
 ├── scripts/
-│   ├── start_paraview_gui_bridge.py
 │   ├── start_paraview_bridge.py
+│   ├── start_paraview_gui_bridge.py
 │   ├── paraview_bridge_request.py
 │   └── library/                 # Reusable pvpython snippets
 │       ├── open_dataset.py

{paraview_mcp_python-0.1.2 → paraview_mcp_python-0.1.4}/bridge/command_handler.py

@@ -8,6 +8,7 @@ is available.
 from __future__ import annotations
 
 import logging
+import os
 from typing import TYPE_CHECKING, Any
 
 from bridge.models import (
@@ -346,7 +347,8 @@ class CommandHandler:
             camera.SetViewUp(*params["view_up"])
         if "parallel_scale" in params:
             camera.SetParallelScale(params["parallel_scale"])
-        view.StillRender()
+        if os.environ.get("PARAVIEW_MCP_GUI_BRIDGE") != "1":
+            view.StillRender()
         pos = list(camera.GetPosition())
         fp = list(camera.GetFocalPoint())
         up = list(camera.GetViewUp())

paraview_mcp_python-0.1.4/bridge/gui_bridge.py

@@ -0,0 +1,264 @@
+"""Helpers for starting the bridge from an already-open ParaView GUI session."""
+
+from __future__ import annotations
+
+import contextlib
+import json
+import logging
+import os
+import select
+import socket
+import traceback
+import uuid
+from dataclasses import dataclass
+from typing import Any
+
+from bridge.server import BUFFER_SIZE, HOST, PORT
+
+logger = logging.getLogger(__name__)
+
+
+@dataclass
+class _ClientState:
+    sock: socket.socket
+    buffer: bytes = b""
+
+
+class ParaViewGuiBridgeServer:
+    """Nonblocking TCP bridge polled from ParaView's GUI event loop."""
+
+    def __init__(self, host: str = HOST, port: int = PORT, poll_interval_ms: int = 50):
+        self._host = host
+        self._port = port
+        self._poll_interval_ms = poll_interval_ms
+        self._server_socket: socket.socket | None = None
+        self._clients: dict[socket.socket, _ClientState] = {}
+        self._running = False
+        self._interactor: Any | None = None
+        self._observer_id: int | None = None
+        self._timer_id: int | None = None
+        # Import here so this module can be imported without ParaView installed.
+        from bridge.command_handler import CommandHandler
+
+        self._handler = CommandHandler()
+
+    @property
+    def host(self) -> str:
+        return self._host
+
+    @property
+    def port(self) -> int:
+        return self._port
+
+    @property
+    def is_running(self) -> bool:
+        return self._running
+
+    def start(self) -> None:
+        if self._running:
+            return
+        self._interactor = self._get_render_window_interactor()
+        if not callable(getattr(self._interactor, "AddObserver", None)):
+            raise RuntimeError("ParaView render window interactor does not support VTK observers")
+        if not callable(getattr(self._interactor, "CreateRepeatingTimer", None)):
+            raise RuntimeError("ParaView render window interactor does not support repeating timers")
+
+        self._server_socket = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
+        self._server_socket.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)
+        self._server_socket.setblocking(False)
+        self._server_socket.bind((self._host, self._port))
+        self._host, self._port = self._server_socket.getsockname()[:2]
+        self._server_socket.listen(5)
+
+        self._observer_id = self._interactor.AddObserver("TimerEvent", self._on_timer)
+        self._timer_id = self._interactor.CreateRepeatingTimer(self._poll_interval_ms)
+        os.environ["PARAVIEW_MCP_GUI_BRIDGE"] = "1"
+        self._running = True
+        logger.info("ParaView GUI bridge listening on %s:%s", self._host, self._port)
+
+    def stop(self) -> None:
+        self._running = False
+        if self._interactor is not None and self._timer_id is not None:
+            destroy_timer = getattr(self._interactor, "DestroyTimer", None)
+            if callable(destroy_timer):
+                with contextlib.suppress(Exception):
+                    destroy_timer(self._timer_id)
+        if self._interactor is not None and self._observer_id is not None:
+            remove_observer = getattr(self._interactor, "RemoveObserver", None)
+            if callable(remove_observer):
+                with contextlib.suppress(Exception):
+                    remove_observer(self._observer_id)
+        self._timer_id = None
+        self._observer_id = None
+        self._interactor = None
+        os.environ.pop("PARAVIEW_MCP_GUI_BRIDGE", None)
+
+        for client in list(self._clients):
+            self._close_client(client)
+        if self._server_socket is not None:
+            with contextlib.suppress(OSError):
+                self._server_socket.close()
+            self._server_socket = None
+
+    def _on_timer(self, _obj: Any, _event: str) -> None:
+        self.poll()
+
+    def poll(self) -> None:
+        """Process pending socket work without blocking the GUI event loop."""
+        if not self._running or self._server_socket is None:
+            return
+        sockets = [self._server_socket, *self._clients]
+        try:
+            readable, _, errored = select.select(sockets, [], sockets, 0)
+        except OSError:
+            return
+
+        for sock in errored:
+            if sock is self._server_socket:
+                logger.error("ParaView GUI bridge server socket failed")
+                self.stop()
+                return
+            self._close_client(sock)
+
+        for sock in readable:
+            if sock is self._server_socket:
+                self._accept_ready_clients()
+                return
+            else:
+                if self._read_client(sock):
+                    return
+
+    def _accept_ready_clients(self) -> None:
+        if self._server_socket is None:
+            return
+        while True:
+            try:
+                conn, addr = self._server_socket.accept()
+            except BlockingIOError:
+                break
+            except OSError:
+                break
+            conn.setblocking(False)
+            self._clients[conn] = _ClientState(conn)
+            logger.info("Client connected from %s", addr)
+
+    def _read_client(self, sock: socket.socket) -> bool:
+        state = self._clients.get(sock)
+        if state is None:
+            return False
+        try:
+            data = sock.recv(BUFFER_SIZE)
+        except BlockingIOError:
+            return False
+        except OSError:
+            self._close_client(sock)
+            return False
+        if not data:
+            self._close_client(sock)
+            return False
+
+        state.buffer += data
+        while b"\n" in state.buffer:
+            line, state.buffer = state.buffer.split(b"\n", 1)
+            if not line.strip():
+                continue
+            try:
+                request = json.loads(line.decode("utf-8"))
+                response = self._process_request(request)
+            except Exception as exc:
+                response = {"id": None, "success": False, "error": str(exc)}
+            self._send_response(sock, response)
+            return True
+        return False
+
+    def _send_response(self, sock: socket.socket, response: dict[str, Any]) -> None:
+        try:
+            sock.sendall((json.dumps(response) + "\n").encode("utf-8"))
+        except OSError:
+            self._close_client(sock)
+
+    def _close_client(self, sock: socket.socket) -> None:
+        self._clients.pop(sock, None)
+        with contextlib.suppress(OSError):
+            sock.close()
+
+    def _process_request(self, request: dict[str, Any]) -> dict[str, Any]:
+        if not isinstance(request, dict):
+            raise TypeError("Request must be a JSON object")
+
+        req_id = request.get("id", str(uuid.uuid4()))
+        command = request.get("command")
+        params = request.get("params", {})
+        if not isinstance(command, str) or not command.strip():
+            return {"id": req_id, "success": False, "error": "Missing or invalid command"}
+        if not isinstance(params, dict):
+            return {"id": req_id, "success": False, "error": "Invalid params: expected JSON object"}
+        try:
+            result = self._handler.handle(command, params)
+            return {"id": req_id, "success": True, "result": result}
+        except Exception as exc:
+            logger.error("Command '%s' failed: %s\n%s", command, exc, traceback.format_exc())
+            return {"id": req_id, "success": False, "error": str(exc)}
+
+    @staticmethod
+    def _get_render_window_interactor() -> Any:
+        import paraview  # noqa: PLC0415
+        import paraview.simple as pvs  # noqa: PLC0415
+
+        if not getattr(paraview, "fromGUI", False):
+            raise RuntimeError(
+                "The live GUI bridge must be started from ParaView's Python Shell with Run Script. "
+                "Starting it with 'paraview --script' runs too early in ParaView startup and is not stable."
+            )
+
+        view = pvs.GetActiveViewOrCreate("RenderView")
+        render_window = view.GetRenderWindow()
+        interactor = render_window.GetInteractor()
+        if interactor is None:
+            raise RuntimeError("ParaView render window interactor is not available")
+        return interactor
+
+
+_SERVER: ParaViewGuiBridgeServer | None = None
+
+
+def start_gui_bridge(host: str = HOST, port: int = PORT) -> dict[str, Any]:
+    """Start the bridge inside the current ParaView GUI process."""
+    global _SERVER
+    if _SERVER is not None and _SERVER.is_running:
+        return {
+            "host": _SERVER.host,
+            "port": _SERVER.port,
+            "running": True,
+            "already_running": True,
+        }
+
+    server = ParaViewGuiBridgeServer(host=host, port=port)
+    server.start()
+    _SERVER = server
+    return {
+        "host": server.host,
+        "port": server.port,
+        "running": True,
+        "already_running": False,
+    }
+
+
+def stop_gui_bridge() -> dict[str, Any]:
+    """Stop the bridge started by :func:`start_gui_bridge`."""
+    global _SERVER
+    if _SERVER is None:
+        return {"running": False, "stopped": False}
+
+    host = _SERVER.host
+    port = _SERVER.port
+    _SERVER.stop()
+    _SERVER = None
+    return {"host": host, "port": port, "running": False, "stopped": True}
+
+
+def gui_bridge_status() -> dict[str, Any]:
+    """Return the current GUI bridge status."""
+    if _SERVER is None or not _SERVER.is_running:
+        return {"running": False}
+    return {"host": _SERVER.host, "port": _SERVER.port, "running": True}