Skip to main content
Glama
ajegorovs

marimo-inspect

by ajegorovs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to marimo-inspect

No user-submitted related servers found.

    Related Servers

    • marimo-mcp

      Vladisluv12
      F
      license
      A
      quality
      D
      maintenance
      Auto-discovers running marimo notebooks and exposes tools for reading, editing, and running cells via MCP, supporting both HTTP and VS Code backends.
      10
      -

    • jupyter-vscode-mcp

      hadiproz
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes Jupyter notebook operations as MCP tools over plain HTTP, allowing AI agents to explore, edit, run, and debug notebooks in a live VS Code session using local or remote kernels.
      2
      MIT

    • python-devtools

      holo-q
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables live runtime inspection of any Python application, allowing MCP clients to query state, evaluate expressions, inspect objects, and read source code while the app runs.
      -

    • jupyter-interactive-mcp

      tsundokum
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives any MCP-compatible LLM client full control over a live JupyterLab instance.
      MIT

    • jupyter-notebook-mcp

      g0g5
      F
      license
      Not graded
      quality
      D
      maintenance
      A FastMCP server for loading, editing, searching, and saving Jupyter notebooks (.ipynb) through MCP tools. It maintains a single active notebook session with live cell indices that update as cells are inserted or removed.
      -

    • notebook-edit

      tmlksu
      F
      license
      A
      quality
      B
      maintenance
      MCP server for structural editing of Jupyter notebook cells (list, read, insert, edit, patch, delete, move) without kernel execution.
      10
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation4/5

    The 14 tools generally have distinct purposes, but get_cell_map, get_cell_data, and get_cell_outputs all involve retrieving cell information and could be confused by an agent unfamiliar with the subtle differences. The descriptions do clarify the differences (preview vs full data vs outputs), so it's mostly distinct.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (get_*, list_*, create_*, edit_*, run_*, delete_*, set_*), with no deviations. The naming is predictable and readable.

    Tool Count5/5

    The server has 14 tools, which is well within the typical 3-15 range for a well-scoped MCP server. Each tool appears to earn its place by covering a specific operation in notebook inspection and manipulation.

    Completeness4/5

    The toolset covers a broad range of notebook operations (cell CRUD, execution, outputs, errors, linting, variables, dependency graph, UI interaction, session management), but some potential gaps exist, such as creating or deleting notebooks, managing files, or deeper kernel operations. It is largely complete for inspection and basic editing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources