Resolve and pin dependencies

veryfront__resolve_project_dependencies

Requires project.files.write.

Access

No external-service connection is required. Use a Veryfront credential with access to the requested resources.

Call type: Can change resources.

Arguments

FieldTypeRequiredDescription and constraints
project_referencestringNoProject UUID or slug. May be omitted when connected through a project-scoped MCP endpoint. Minimum length: 1.
branchstringNoBranch UUID or name; omit for main. 1-255 characters without surrounding whitespace. Minimum length: 1. Maximum length: 255.
specifiersstring[]Yes1-100 npm specifiers of 1-200 characters: bare name, exact version or semver range. Pin exact versions in package.json after adding imports or packages.
expected_declarationsobjectNoObserved declarations; at most 100 entries of up to 200 characters. Every requested package must be present; null means absent. Changed declarations are skipped.
confirmbooleanYesMust be true to confirm writing resolved pins to package.json.

Example request

Send this JSON-RPC request through an initialized MCP client. Replace sample identifiers and values before calling the tool. See MCP client setup.

json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "veryfront__resolve_project_dependencies",
    "arguments": {
      "specifiers": [
        "example"
      ],
      "confirm": true
    }
  }
}

Result

The published output shape is summarized below. Inspect both the MCP response content and isError when handling a call.

FieldTypeRequiredDescription and constraints
pinsobjectYesSuccessfully resolved exact pins, including existing pins. Existing exact pins remain unchanged. Unknown packages and registry failures are omitted without failing the batch. A requested package absent from both pins and skipped was not resolved or written.
persistedbooleanYesTrue when eligible pins were persisted or no eligible write was needed. False means persistence failed; pins retain intended values for retry.
skippedobjectYesPackages skipped because their current declaration differs from the supplied snapshot. The skip reason is declaration_changed.

Full schemas

json
{
  "type": "object",
  "properties": {
    "project_reference": {
      "type": "string",
      "minLength": 1,
      "description": "Project UUID or slug. May be omitted when connected through a project-scoped MCP endpoint."
    },
    "branch": {
      "type": "string",
      "minLength": 1,
      "maxLength": 255,
      "description": "Branch UUID or name; omit for main. 1-255 characters without surrounding whitespace."
    },
    "specifiers": {
      "type": "array",
      "items": {
        "type": "string",
        "minLength": 1,
        "maxLength": 200,
        "description": "One specifier item supplied to the tool."
      },
      "minItems": 1,
      "maxItems": 100,
      "description": "1-100 npm specifiers of 1-200 characters: bare name, exact version or semver range. Pin exact versions in package.json after adding imports or packages."
    },
    "expected_declarations": {
      "description": "Observed declarations; at most 100 entries of up to 200 characters. Every requested package must be present; null means absent. Changed declarations are skipped.",
      "type": "object",
      "maxProperties": 100,
      "additionalProperties": {
        "type": [
          "string",
          "null"
        ],
        "maxLength": 200,
        "description": "Additional structured values supplied to the tool."
      }
    },
    "confirm": {
      "type": "boolean",
      "description": "Must be true to confirm writing resolved pins to package.json."
    }
  },
  "required": [
    "specifiers",
    "confirm"
  ],
  "additionalProperties": false,
  "description": "Arguments for the resolve_project_dependencies tool.",
  "$schema": "http://json-schema.org/draft-07/schema#"
}
json
{
  "type": "object",
  "properties": {
    "pins": {
      "description": "Successfully resolved exact pins, including existing pins. Existing exact pins remain unchanged. Unknown packages and registry failures are omitted without failing the batch. A requested package absent from both pins and skipped was not resolved or written.",
      "type": "object",
      "additionalProperties": {
        "type": "string",
        "description": "Additional structured values returned by the tool."
      }
    },
    "persisted": {
      "type": "boolean",
      "description": "True when eligible pins were persisted or no eligible write was needed. False means persistence failed; pins retain intended values for retry."
    },
    "skipped": {
      "description": "Packages skipped because their current declaration differs from the supplied snapshot. The skip reason is declaration_changed.",
      "type": "object",
      "additionalProperties": {
        "type": "string",
        "enum": [
          "declaration_changed"
        ],
        "description": "Additional structured values returned by the tool."
      }
    }
  },
  "required": [
    "pins",
    "persisted",
    "skipped"
  ],
  "additionalProperties": false,
  "description": "Structured result returned by the resolve_project_dependencies tool.",
  "$schema": "http://json-schema.org/draft-07/schema#"
}