Skip to main content
Glama
rreusser

Observable Notebook Kit Debug MCP Server

by rreusser
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Observable Notebook Kit Debug MCP Server

No user-submitted related servers found.

    Related Servers

    • threejs-devtools-mcp

      shotarodriguez
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect a running Three.js or React Three Fiber scene in the browser, preview material, shader, light and camera edits live, and turn approved changes into ready-to-paste source code. Also supports website performance audits, video frame capture, and Playwright/Puppeteer test hooks.
      197 npm
      MIT

    • threejs-devtools-mcp

      charlottelundberg
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect, live-preview, and debug Three.js and React Three Fiber scenes in a running browser, then convert the changes they keep into ready-to-paste code. Also supports website performance audits, video frame capture, and Playwright/Puppeteer test integration without modifying the project.
      197 npm
      MIT

    • threejs-devtools-mcp

      ChalermchaiFernandez4464
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect and live-edit Three.js scenes in the browser — objects, materials, shaders, textures, lights, animation, performance and memory — then turn those previewed changes into ready-to-paste code. It also supports website audits, video frame capture, and Playwright/Puppeteer test workflows.
      197 npm
      MIT

    • browser-devtools-mcp

      David-chinese-wei
      A
      license
      B
      quality
      B
      maintenance
      Lets an AI assistant inspect a running Google Chrome or Microsoft Edge browser over the Chrome DevTools Protocol, reading console output, network traffic, DOM snapshots, errors, performance metrics, storage, and screenshots. It also supports live event subscriptions, screen-frame streaming, and one-shot export of everything into an offline-readable archive such as HAR, CSV, and a self-contained HTML report.
      36
      0
      1
      MIT

    • threejs-devtools-mcp

      priyatamkoc99663
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect Three.js scenes in real time, experiment with live previews of changes to materials, shaders, lights and cameras, and convert those changes into ready-to-paste vanilla Three.js or React Three Fiber code. Also supports website performance audits, video frame capture, and Playwright helpers with zero project changes.
      197 npm
      MIT
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A3.6/5.0

    Scored across 20 tools

    Disambiguation4/5

    Tools are largely purpose-specific: value retrieval is split into single/bulk/metadata/list, and evaluation is split into browser vs runtime contexts. A few boundaries require care—GetErrors vs GetConsoleMessages both surface errors, and GetValues with no names overlaps with ListValues—but descriptions clarify intended usage.

    Naming Consistency4/5

    Most tools follow a PascalCase VerbNoun pattern (ListNotebooks, GetValue, SetInputValue, SendKeys). Exceptions break the pattern: Refresh and Navigate are bare verbs, while BrowserEval/RuntimeEval and MouseClick/Drag/Wheel/Hover put the context or object before the action, making the convention less predictable.

    Tool Count3/5

    20 tools is at the high end for a debugger and feels slightly heavy, with multiple value-retrieval variants and five input-simulation tools. The breadth is defensible because the server covers runtime state, DOM inspection, and mouse/keyboard interaction, but it is borderline rather than clearly well-scoped.

    Completeness4/5

    The server covers the main notebook debugging loop: discover/connect notebooks, inspect runtime values and dependencies, read console/errors, manipulate inputs, and simulate interactions. Obvious gaps such as a dedicated screenshot or wait-for-condition tool are workaroundable via BrowserEval/RuntimeEval, but they are minor omissions.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources