Node connectorMCP-first

Node runtime inspection as a first-class connector

Node is a public debugging and diagnostics connector for remote V8 inspection, runtime evaluation, breakpoints, tracing, and process-level analysis.

attachtraceprofileevaluate

See connector reference Browse connectors

The runtime oscilloscope

Terminal green, V8 trace lines, memory contours, and debugger breakpoints for the culture of backend diagnosis and process introspection.

A runtime oscilloscope for JavaScript processes: call stacks, workers, traces, heaps, and live evaluation arranged like a diagnostic console.

Identity

Node makes the running process legible without forcing backend work through browser metaphors.

A Node process is not a page. It is a living runtime with workers, memory pressure, exceptions, performance cliffs, and code paths that only make sense when inspected while they run.

This connector gives agents a debugger-shaped relationship with that runtime: attach, observe, evaluate, trace, and explain what the process is actually doing.

State

live process

Signal

traces and heaps

Loop

attach, pause, inspect

Best for

Attaching to Node or V8 runtimes for diagnostics and debugging.

Runtime evaluation, tracing, profiling, breakpoints, and process inspection.

Agent workflows that need code-runtime visibility alongside other connector work.

Runtime model

Connects to active Node and V8 processes as a dedicated debugging runtime.

Separates process discovery, connection management, and runtime inspection from the browser connector surface.

Keeps backend runtime work first-class instead of forcing everything through browser metaphors.

Auth model

Use the Node connector with the same account and auth model as other Scout public connectors.

Keep Node debugging separate from browser or system automation unless the workflow truly spans those boundaries.

Treat the connector as a targeted runtime surface for inspection and diagnostics, not as a generic replacement for deployment tooling.

Capability atlas

A compact map of what this connector can do.

Node exposes 20 commands across 2 capability groups. The full reference stays close, while this page keeps the connector's runtime shape easy to understand.

Session

Discover processes, attach, detach, and inspect active debugger connections.

node-connectnode-connectionsnode-disconnectnode-discover

Debug

Drive breakpoints, console inspection, evaluation, profiling, memory inspection, tracing, workers, and runtime diagnostics.

node-breakpointnode-consolenode-debuggernode-evaluatenode-exceptionsnode-injectnode-instrumentnode-memory+8 more

Connection

Add the connector deliberately.

Add the hosted connector endpoint your MCP client needs. Each public connector stays separate so agent permissions and runtime boundaries remain explicit.

SnippetJSON

{
  "mcpServers": {
    "scout-node": {
      "type": "http",
      "url": "https://mcp.scout.i.ng/node"
    }
  }
}

Keep connector boundaries intentional

Dedicated connector pages should make capability boundaries memorable before the agent ever receives tools.

Browse all connectors Back to docs reference