wolfbooklisted
Install: claude install-skill antiamerican-postponer432/chatgpt-for-researchers
# wolfbook — driving the live Wolfram kernel + notebook via MCP
The `mcp__wolfbook__*` tools talk to a **running** Wolfram kernel inside a VS Code window, editing
and evaluating a live `.wb`/`.nb` notebook. This is the opposite end from `wolfram-headless`
(one-shot `wolframscript`): here state persists, cells have stable IDs, and you can
checkpoint/restore.
**Requires** the [Wolfbook](https://wolfbook.app/) extension with the MCP enabled
(`"wolfbook.mcpEnabled": true`); and the server registered with Codex
under `[mcp_servers]` in `~/.codex/config.toml` or the project's `.codex/config.toml`
(see Wolfbook's own docs for the command/endpoint). Run `/mcp` in Codex to confirm the
server is connected and to list its tools; without it, use `wolfram-headless` for `.wls`
runs instead.
## Decision: MCP live kernel vs headless wolframscript
- **Live kernel (MCP)** — interactive work on the project notebook: read/edit/run cells, probe
state, small-to-medium evaluations, debugging, building up definitions incrementally. State is
preserved between calls; `kernelControl` gives real checkpoint/restore.
- **Headless (`wolframscript`, see `wolfram-headless`)** — heavy batch jobs (a big symbolic solve)
that would block or OOM the interactive kernel, or that you want to run in the background and poll
a result file. The live kernel in VS Code *contends for the license seat* with headless jobs —
close/idle the Wolfbook window before a long headless run, or target a worker client.
-