variable_copy

[WORKFLOW] Copy variables from one environment to another

⚡️ Best for: ✓ Environment migration ✓ Configuration sharing ✓ Environment duplication

⚠️ Not for: × Single variable updates (use variable_set) × Temporary configuration changes

→ Prerequisites: service_list

→ Alternatives: variable_set

→ Next steps: deployment_trigger, service_restart

→ Related: variable_list, service_update

Input Schema

Name	Required	Description
`overwrite`	No	Whether to overwrite existing variables in the target environment
`projectId`	Yes	ID of the project
`serviceId`	No	ID of the service (optional, if omitted copies shared variables)
`sourceEnvironmentId`	Yes	ID of the source environment (usually obtained from project_info)
`targetEnvironmentId`	Yes	ID of the target environment (usually obtained from project_info)

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "overwrite": {
      "default": false,
      "description": "Whether to overwrite existing variables in the target environment",
      "type": "boolean"
    },
    "projectId": {
      "description": "ID of the project",
      "type": "string"
    },
    "serviceId": {
      "description": "ID of the service (optional, if omitted copies shared variables)",
      "type": "string"
    },
    "sourceEnvironmentId": {
      "description": "ID of the source environment (usually obtained from project_info)",
      "type": "string"
    },
    "targetEnvironmentId": {
      "description": "ID of the target environment (usually obtained from project_info)",
      "type": "string"
    }
  },
  "required": [
    "projectId",
    "sourceEnvironmentId",
    "targetEnvironmentId"
  ],
  "type": "object"
}

railway-mcp

variable_copy

Input Schema

Input Schema (JSON Schema)

Other Tools