pluto pair
- Repo stars 301
- Author repo marketplace
- Domain
- AI
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @aiskillstore · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Write / modify
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Pluto Pair
Use the `pluto-pair` MCP server when a task involves Pluto.jl notebook state or controls.
If the user has a Pluto browser window open, prefer live attach first:
- `pluto_discover_servers` to check local Pluto servers, especially port 1234.
- `pluto_attach_session` to attach to a notebook already running in that visible server.
- `pluto_open_visible` to open a notebook in the visible server and attach to it.
Live attached sessions update the same notebook the user sees in their browser.
Use headless tools for isolated checks, CI-like validation, exports, or untrusted/static previews:
- `pluto_list_notebooks` to discover notebook files.
- `pluto_open_notebook` to open and execute a trusted notebook. Execution is the default; pass `execution_allowed=false` only for untrusted preview.
- `pluto_list_bonds` to inspect `@bind` variables.
- `pluto_set_bonds` to set bound values and trigger Pluto reactivity.
- `pluto_read_state` to summarize code, outputs, errors, logs, and bonds.
- `pluto_export_html` to write a rendered HTML export.
- `pluto_close_notebook` when finished. On live attached sessions, this only detaches and does not shut down the user's Pluto notebook.
Use browser automation only for visual smoke checks or screenshots.
Sections and files
Listed in source order.
sections -> → → → → →
terms -> Use the pluto-pair MCP server when a task involves Pluto.jl notebook state or controls. · - plutodiscoverservers to check local Pluto servers, especially port 1234. · Live attached sessions update the same notebook the user sees in their browser. · - plutolistnotebooks to discover notebook files. · Use browser automation only for visual smoke checks or screenshots.
files/cmd -> pluto-pair · pluto_discover_servers · pluto_attach_session · pluto_open_visible · pluto_list_notebooks · pluto_open_notebook · execution_allowed=false · pluto_list_bonds
body sha256 -> 7b9fb6b502b9
Use the
pluto-pairMCP server when a task involves Pluto.jl notebook state or controls.If the user has a Pluto browser window open, prefer live attach first:
pluto_discover_serversto check local Pluto servers, especially port 1234. -pluto_attach_sessionto attach to a notebook already running in that visible server. -pluto_open_visibleto open a notebook in the visible server and attach to it.Live attached sessions update the same notebook the user sees in their browser.
Use headless tools for isolated checks, CI-like validation, exports, or untrusted/static previews: