deployment_trigger
Trigger new deployments for Railway services to apply code changes, configuration updates, or roll back to previous states using specific commit SHAs.
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
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| projectId | Yes | ID of the project | |
| serviceId | Yes | ID of the service | |
| environmentId | Yes | ID of the environment | |
| commitSha | Yes | Specific commit SHA from the Git repository |
Implementation Reference
- src/tools/deployment.tool.ts:60-62 (handler)The async handler function that executes the deployment_trigger tool logic by calling deploymentService.triggerDeployment.async ({ projectId, serviceId, environmentId, commitSha }) => { return deploymentService.triggerDeployment(projectId, serviceId, environmentId, commitSha); }
- src/tools/deployment.tool.ts:54-59 (schema)Zod schema defining the input parameters for the deployment_trigger tool.{ projectId: z.string().describe("ID of the project"), serviceId: z.string().describe("ID of the service"), environmentId: z.string().describe("ID of the environment"), commitSha: z.string().describe("Specific commit SHA from the Git repository") },
- src/tools/deployment.tool.ts:33-63 (registration)The createTool call that registers the deployment_trigger tool, including its description, schema, and handler."deployment_trigger", formatToolDescription({ type: 'API', description: "Trigger a new deployment for a service", bestFor: [ "Deploying code changes", "Applying configuration updates", "Rolling back to previous states" ], notFor: [ "Restarting services (use service_restart)", "Updating service config (use service_update)", "Database changes" ], relations: { prerequisites: ["service_list"], nextSteps: ["deployment_logs", "deployment_status"], alternatives: ["service_restart"], related: ["variable_set", "service_update"] } }), { projectId: z.string().describe("ID of the project"), serviceId: z.string().describe("ID of the service"), environmentId: z.string().describe("ID of the environment"), commitSha: z.string().describe("Specific commit SHA from the Git repository") }, async ({ projectId, serviceId, environmentId, commitSha }) => { return deploymentService.triggerDeployment(projectId, serviceId, environmentId, commitSha); } ),
- src/tools/index.ts:32-36 (registration)Registration of all tools, including deployment_trigger from deploymentTools, with the MCP server.allTools.forEach((tool) => { server.tool( ...tool ); });
- src/types.ts:209-213 (schema)TypeScript interface defining the DeploymentTriggerInput used in the deployment repository.export interface DeploymentTriggerInput { commitSha?: string; environmentId: string; serviceId: string; }