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

**Follow the repository's Node.js version.** Turn follow mode on or off for a row, at its `revision`: with it on, each deployment switches the row to the Node.js major its repository asks for (.nvmrc, engines.node and the like) when that major is offered and supported, never an end-of-life one. Scope: write.

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

## When to use it

Turn follow mode on or off at the row's `revision`. With it on, each deployment switches the row to the Node.js major its repository asks for (`.nvmrc`, `engines.node` and the like) when that major is offered and supported, never an end-of-life one. Only the switch changes.

## Inputs

- `site_id` (integer, ≥ 1, required)
- `revision` (integer, ≥ 0, required)
- `enabled` (boolean, required)

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "enabled": {
      "description": "true to follow the repository, false to keep the chosen major.",
      "type": "boolean"
    },
    "revision": {
      "description": "From corestack_node_runtime_get; stale when the row changed since.",
      "minimum": 0,
      "type": "integer"
    },
    "site_id": {
      "description": "The row: the site or one of its environments.",
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "site_id",
    "revision",
    "enabled"
  ],
  "type": "object"
}
```

## Refusals

- `runtime_not_adopted`: the row is not on the new runtime yet.
- `stale`, `runtime_locked`: as corestack_node_version_change.
- `managed_elsewhere` (message: "This site is managed by another control panel"): another control panel manages this site, so use that control panel for it. This is refused before anything else about the site, as in the Control Panel and the API. Nothing was done.
- 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_follow_repository_set",
  "arguments": {
    "site_id": 4211,
    "revision": 7,
    "enabled": true
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_node_follow_repository_set with site_id 4211, revision 7, enabled true. (Follow the repository's Node.js version.) Tell me what it returned.
```

## The same task elsewhere

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