deployment_trigger

Trigger new deployments for Railway services using a specific commit SHA. Ideal for deploying code changes, applying configuration updates, or rolling back to previous states. Requires project, service, environment, and commit details.

Instructions

[API] Trigger a new deployment for a service

⚡️ Best for: ✓ Deploying code changes ✓ Applying configuration updates ✓ Rolling back to previous states

⚠️ Not for: × Restarting services (use service_restart) × Updating service config (use service_update) × Database changes

→ Prerequisites: service_list

→ Alternatives: service_restart

→ Next steps: deployment_logs, deployment_status

→ Related: variable_set, service_update

Input Schema

Name	Required	Description
`commitSha`	Yes	Specific commit SHA from the Git repository
`environmentId`	Yes	ID of the environment
`projectId`	Yes	ID of the project
`serviceId`	Yes	ID of the service

Input Schema (JSON Schema)

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "additionalProperties": false,
  "properties": {
    "commitSha": {
      "description": "Specific commit SHA from the Git repository",
      "type": "string"
    },
    "environmentId": {
      "description": "ID of the environment",
      "type": "string"
    },
    "projectId": {
      "description": "ID of the project",
      "type": "string"
    },
    "serviceId": {
      "description": "ID of the service",
      "type": "string"
    }
  },
  "required": [
    "projectId",
    "serviceId",
    "environmentId",
    "commitSha"
  ],
  "type": "object"
}

railway-mcp