---
title: "corestack_node_runtime_get"
url: https://docs.corefinity.com/mcp/tools/corestack_node_runtime_get
type: tool
last_updated: 2026-11-13
feature: node-runtime
related:
  - https://docs.corefinity.com/api/reference/runtime/get-node-runtime.md
  - https://docs.corefinity.com/guides/sites/software-and-services/node-js.md
---
# corestack_node_runtime_get

**Node.js configuration.** A row's whole Node.js card: the major and exact version, the majors it may move to and what each needs acknowledged, its global packages with their pinned versions and install state, follow mode, the repository's requirement, caches, any change in flight, and `revision`, the token the Node.js writes need. Scope: read.

- Scope: `read`
- Runs as a task: no

## When to use it

Read a row's Node.js card before changing anything: the major and exact version with its support status, the majors it may move to and what each needs acknowledged, its global npm packages with their pinned versions, install state, errors and last check, hand-installed packages, follow mode and the repository's requirement, caches and memory, any change in flight or refused, and `revision`, the token every Node.js write sends back. A row not yet on the new runtime reads Node.js 16 with no packages. `refresh: true` re-reads the running site's report first.

## Inputs

- `site_id` (integer, ≥ 1, required): the site or one of its environments.
- `refresh` (boolean): re-read the pod's Node.js report first; needs commands switched on.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "refresh": {
      "default": false,
      "description": "Re-read the running site's Node.js report first (needs commands switched on).",
      "type": "boolean"
    },
    "site_id": {
      "description": "The row: the site or one of its environments.",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id"
  ],
  "type": "object"
}
```

## Refusals

- `switched_off`: with `refresh`, commands are switched off; read without it.
- `not_running`: with `refresh`, the site is not running.
- The refusals every tool can answer: `invalid_arguments`, `tenant_mismatch`, `scope_required`, `pin_refused`, `rate_limited`, `temporarily_unavailable`, `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_node_runtime_get",
  "arguments": {
    "site_id": 4211
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_node_runtime_get with site_id 4211. (Node.js configuration.) Tell me what it returned.
```

## The same task elsewhere

- Endpoint: [GET /api/corestack/sites/{site}/node-runtime](https://docs.corefinity.com/api/reference/runtime/get-node-runtime.md)
- Guide: [Node.js configuration](https://docs.corefinity.com/guides/sites/software-and-services/node-js.md)
