All servers / Notes / Nebula Notebook MCP server
Nebula Notebook MCP server
MCP server for Nebula Notebook — lets agents (Claude Code, Codex, etc.) read, edit, and execute notebooks on a running Nebula server
Tested by ConnectATDScore 90 out of 100. Tested 2026-11-18 on package version 0.4.108. Package: nebula-notebook-mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (4.4 seconds including download)
- Tools offered: 37
- Last published: 2026-11-18
- Weekly downloads (npm): 1,781
- License: MIT · Direct dependencies: 5
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
read_notebook7 of 7 parameters describedRead all cells from a notebook. Formats: "content" (full code, no outputs), "detailed" (full code + inline images, default), "placeholder" (full code + text placeholders for images, recommended for Gemini). Outputs are truncated (100 lines regular, 200 lines errors). MCP: call connect_server first (see connect_server for workflow).
read_cell3 of 3 parameters describedRead a specific cell content and metadata (not outputs). Use read_output to get outputs. MCP: call connect_server first (see connect_server for workflow).
read_output12 of 12 parameters describedRead cell outputs. By default waits for completion or max_wait timeout (returns once). Set wait_for_completion=false to return as soon as new output appears. Regular outputs truncated to 100 lines, errors get 200 lines. Use save_to_file=true for complete output. MCP: call connect_server first (see connect_server for workflow).
insert_cell5 of 5 parameters describedInsert a new cell into the notebook. Use position=-1 or omit to append at end. MCP: call connect_server first (see connect_server for workflow).
update_cell4 of 4 parameters describedUpdate an existing cell by its stable ID. Can update content and/or type. MCP: call connect_server first (see connect_server for workflow).
delete_cell3 of 3 parameters describedDelete a cell from a notebook MCP: call connect_server first (see connect_server for workflow).
clear_notebook1 of 1 parameter describedClear all cells from a notebook. MCP: call connect_server first (see connect_server for workflow).
create_notebook4 of 4 parameters describedCreate a new empty notebook. If the notebook is open in the browser UI, it will attempt to open the new notebook in a new tab. MCP: call connect_server first (see connect_server for workflow).
move_cell5 of 5 parameters describedMove a cell from one position to another. Supports two modes: by index (from_index, to_index) or by ID (cell_id with after_cell_id or to_index=-1 for start). MCP: call connect_server first (see connect_server for workflow).
duplicate_cell2 of 2 parameters describedDuplicate a cell, inserting the copy immediately after the original MCP: call connect_server first (see connect_server for workflow).
search_cells4 of 4 parameters describedSearch notebook cells by keyword. Can search in cell source code and optionally in outputs. MCP: call connect_server first (see connect_server for workflow).
update_metadata3 of 3 parameters describedUpdate cell metadata (id, type, scrolled, scrolledHeight). Validates against schema. MCP: call connect_server first (see connect_server for workflow).
connect_server1 of 1 parameter describedConnect to a Nebula server. REQUIRED: call this once at the start of every MCP session before any other tool call. base_url is required; the server does not assume a default. All subsequent operations will use this connection. RECOMMENDED WORKFLOW: 1. connect_server (required at session start) 2. For each response: start_agent_session → operations → end_agent_session start_agent_session is required for notebook mutations; read-only operations do not require it.
start_agent_session5 of 5 parameters describedStart an agent session for notebook write operations. Always call end_agent_session when done. Sessions are COLLABORATIVE by default: the user can keep editing while you work. Your destructive writes (update_cell, delete_cell, …) are protected by per-cell optimistic concurrency — if the user changed a cell after you last read it, the write is rejected with the current content so you can re-apply your intent. Address cells by id (indices shift when the user edits), and re-read cells you haven't read recently. Pass exclusive=true only for large multi-cell refactors that need atomicity: it locks the UI read-only for the duration (the legacy behavior). Prefer collaborative sessions otherwise. See connect_server for required MCP workflow. This call validates that the notebook path exists; it will error if the path is wrong or missing. IMPORTANT: Call this at the START of each response before any notebook operations, and call end_agent_session at the END of each response. This ensures the notebook is only locked while you're actively working on it. Example flow for each response: start_agent_session → insert_cell/update_cell/execute_cell/etc → end_agent_session FORCE OPTION (use only with explicit user permission): If a previous agent session was not properly ended (e.g., due to a crash or timeout), the notebook may remain locked. Use force=true ONLY when the user explicitly asks you to "force" or "steal" the lock. This will forcibly end any existing session and start a new one. MCP: call connect_server first (see connect_server for workflow).
end_agent_session1 of 1 parameter describedEnd an agent session, unlocking the notebook for user edits. Always call this at the END of each response after completing all notebook operations. IMPORTANT: Always call this before finishing your response, even if operations failed. This ensures the notebook is unlocked for the user. MCP: call connect_server first (see connect_server for workflow).
delete_cells2 of 2 parameters describedDelete multiple cells by ID in a single operation. More efficient than multiple single deletes. MCP: call connect_server first (see connect_server for workflow).
insert_cells3 of 3 parameters describedInsert multiple cells at a position in a single operation. More efficient than multiple single inserts. MCP: call connect_server first (see connect_server for workflow).
clear_outputs2 of 2 parameters describedClear outputs from cells without re-executing. If no cell_ids provided, clears all cell outputs. Useful for cleanup before sharing notebooks. MCP: call connect_server first (see connect_server for workflow).
list_kernelsno parametersList available kernel specifications with display names (includes version info) MCP: call connect_server first (see connect_server for workflow).
kernel_start1 of 1 parameter describedStart a new kernel session for the active notebook (requires start_agent_session) MCP: call connect_server first (see connect_server for workflow).
kernel_stopno parametersStop and shutdown the active notebook kernel (requires start_agent_session) MCP: call connect_server first (see connect_server for workflow).
kernel_restartno parametersRestart the active notebook kernel (clears all variables, requires start_agent_session) MCP: call connect_server first (see connect_server for workflow).
kernel_interruptno parametersInterrupt execution in the active notebook kernel (requires start_agent_session) MCP: call connect_server first (see connect_server for workflow).
execute_cell8 of 8 parameters describedExecute a notebook cell and return its output. Outputs are truncated by default (100 lines, 10000 chars). Outputs are saved incrementally during execution. Requires an active kernel session. For long-running cells: If execution exceeds max_wait, returns with status="busy" and partial output. Use read_output with max_wait to poll for more output. Set max_wait=0 for immediate "background" execution (returns right away, poll with read_output). MCP: call connect_server first (see connect_server for workflow).
read_file1 of 1 parameter describedRead the contents of a text file from the server. Returns file content as string. For .ipynb notebooks, returns JSON string; .py/.qmd notebooks are plain text. MCP: call connect_server first (see connect_server for workflow).
write_file2 of 2 parameters describedWrite content to a file on the server. Creates the file and parent directories if they do not exist. Overwrites existing file. MCP: call connect_server first (see connect_server for workflow).
list_directory1 of 1 parameter describedList contents of a directory on the server. Returns file and directory names with types. MCP: call connect_server first (see connect_server for workflow).
delete_file1 of 1 parameter describedDelete a file or directory from the server. Directories are deleted recursively. MCP: call connect_server first (see connect_server for workflow).
rename_file2 of 2 parameters describedRename or move a file or directory on the server. MCP: call connect_server first (see connect_server for workflow).
download_file2 of 2 parameters describedDownload a file from the server to a local path. Supports both text and binary files. MCP: call connect_server first (see connect_server for workflow).
upload_file3 of 3 parameters describedUpload a local file to the server. Supports both text and binary files. Fails if the destination file already exists unless on_conflict says otherwise. MCP: call connect_server first (see connect_server for workflow).
compute_statusno parametersCheck whether scheduler-backed cluster compute (allocations) is available on this Nebula server. Returns enabled + scheduler name. Call this before any other compute tool — the feature is absent on servers without a scheduler (e.g. laptops). MCP: call connect_server first (see connect_server for workflow).
list_compute_queuesno parametersList cluster partitions and QoS with live load: idle/total CPUs, idle GPUs by type, queue backlog (pending/running jobs), and which partitions/QoS the user may submit to. Use it to pick a partition before request_allocation. MCP: call connect_server first (see connect_server for workflow).
request_allocation11 of 11 parameters describedRequest a compute allocation from the cluster scheduler. Allocations consume REAL cluster resources — only request one when the user's task actually needs it, request modest sizes, and cancel_allocation when done. Set wait_for_active=true to block until the allocation is usable (state=active), then bind a notebook with use_allocation. MCP: call connect_server first (see connect_server for workflow).
list_allocationsno parametersList compute allocations on the server with state (pending/running/active/ended/failed/cancelled), resources, and the serverId/node once active. MCP: call connect_server first (see connect_server for workflow).
cancel_allocation1 of 1 parameter describedCancel a compute allocation and free its cluster nodes. Cancel allocations you created once the task completes; never cancel allocations you did not create. MCP: call connect_server first (see connect_server for workflow).
use_allocation3 of 3 parameters describedBind a notebook's kernels to an active compute allocation: starts (or reuses) the notebook's kernel on the allocation's server and saves it as the notebook's kernel preference. After this, execute_cell on that notebook runs on the allocation. Requires the allocation to be state=active. MCP: call connect_server first (see connect_server for workflow).
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.