+1
-1
| { | ||
| "name": "flameox", | ||
| "version": "0.2.3", | ||
| "version": "0.2.4", | ||
| "description": "Print the local flameox MCP stdio setup through uvx", | ||
@@ -5,0 +5,0 @@ "homepage": "https://github.com/morluto/flameox#readme", |
+9
-7
@@ -9,10 +9,12 @@ # flameox | ||
| Setup prints a repo-local stdio MCP launch configuration pinned to the exact | ||
| Flameox release resolved by npm and to Python 3.12. It does not change an MCP | ||
| client registration. Apply the printed command through the client's supported | ||
| MCP management interface. Without explicit `--provider` options, setup does not | ||
| install profilers, optional packages, a persistent managed runtime, or project state. | ||
| The Python server fixes `project_root` at startup and creates `.flameox` only | ||
| after an explicit evidence-preservation request. | ||
| Setup detects supported coding agents, asks which global MCP clients to configure, and writes a | ||
| Python 3.12 `uvx` launcher pinned to the exact Flameox release resolved by npm. It preserves | ||
| unrelated configuration and tells you which clients must restart or reconnect. Use | ||
| `--client codex --yes`, repeated `--client` options, or `--all --yes` for automation, and | ||
| `--dry-run` to inspect the resolved paths without writing them. | ||
| Without explicit `--provider` options, setup does not install profilers, optional packages, a | ||
| persistent managed runtime, or project state. The Python server has no workspace binding. Explicit | ||
| preservation writes to Flameox's user-level data directory. | ||
| For direct CLI use, install or run the Python package with `uv`/`uvx`. |
3667
4.38%20
11.11%