railway-mcp
by jason-tan-swe
Verified
deployment_trigger
[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 | Default |
---|---|---|---|
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)
You must be authenticated.
Other Tools
- configure_api_token
- database_deploy_from_template
- database_list_types
- deployment_list
- deployment_logs
- deployment_status
- deployment_trigger
- domain_check
- domain_create
- domain_delete
- domain_list
- domain_update
- list_service_variables
- project_create
- project_delete
- project_environments
- project_info
- project_list
- service_create_from_image
- service_create_from_repo
- service_delete
- service_info
- service_list
- service_restart
- service_update
- tcp_proxy_create
- tcp_proxy_delete
- tcp_proxy_list
- variable_bulk_set
- variable_copy
- variable_delete
- variable_set
- volume_create
- volume_delete
- volume_list
- volume_update