Wolfbook MCP Feedback
What Worked Well
- Once the MCP server was correctly configured, the Wolfbook tool namespace appeared and was callable from Codex.
wolfbook_list_clients clearly showed the connected VS Code client and the open not.wb notebook.- Kernel evaluation worked reliably through
wolfbook_evaluateExpression.
- Symbol lookup worked well through
wolfbook_lookupSymbol.
- File operations worked cleanly through
wolfbook_fileOps.
- Wolfram graphics evaluation returned a graphics result successfully.
Configuration Friction
- The MCP config initially used
command = "node", but Codex could not resolve node from PATH.
- Using the absolute Node path fixed that ambiguity:
command = "C:\\Program Files\\nodejs\\node.exe"
- The config also needed an explicit
enabled = true line restored.
- It would be helpful if Wolfbook or Codex surfaced MCP startup failures more directly, especially when the command cannot be found.
Notebook Editing Issue
- Kernel and file-level tools worked, but notebook cell insertion failed with:
No active notebook editor.
- This happened even though
wolfbook_list_clients and wolfbook_getNotebookContext could see not.wb.
- Directly writing the
.wb file through wolfbook_fileOps succeeded, but VS Code appeared to keep an older in-memory notebook state.
Suggested Improvements
- Add a diagnostic command that reports whether Wolfbook's editor bridge, kernel bridge, and file bridge are each available.
- Make
No active notebook editor more actionable by saying which VS Code editor state is required.
- Consider allowing
wolfbook_insertCells to target an open notebook by path even when the editor is not focused.
- Provide a safe notebook reload/sync operation after direct
.wb file writes.
- Include the resolved MCP command and startup stderr in a debug/status tool so configuration issues are easier to diagnose.
Wolfbook MCP Feedback
What Worked Well
wolfbook_list_clientsclearly showed the connected VS Code client and the opennot.wbnotebook.wolfbook_evaluateExpression.wolfbook_lookupSymbol.wolfbook_fileOps.Configuration Friction
command = "node", but Codex could not resolvenodefrom PATH.enabled = trueline restored.Notebook Editing Issue
wolfbook_list_clientsandwolfbook_getNotebookContextcould seenot.wb..wbfile throughwolfbook_fileOpssucceeded, but VS Code appeared to keep an older in-memory notebook state.Suggested Improvements
No active notebook editormore actionable by saying which VS Code editor state is required.wolfbook_insertCellsto target an open notebook by path even when the editor is not focused..wbfile writes.