railway-mcp
by jason-tan-swe
Verified
database_deploy_from_template
[WORKFLOW] Deploy a pre-configured database using Railway's official templates and best practices
⚡️ Best for: ✓ Standard database deployments ✓ Quick setup with security defaults ✓ Common database types (PostgreSQL, MongoDB, Redis)
⚠️ Not for: × Custom database versions × Complex configurations × Unsupported database types
→ Prerequisites: database_list_types
→ Alternatives: service_create_from_image
→ Next steps: variable_list, service_info
→ Related: volume_create, service_update
Input Schema
Name | Required | Description | Default |
---|---|---|---|
environmentId | Yes | Environment ID where the database will be deployed (usually obtained from project_info) | |
name | No | Optional custom name for the database service. Default: {type}-database | |
projectId | Yes | ID of the project where the database will be deployed | |
region | Yes | Region where the database should be deployed, try us-west1 before all other regions | |
type | Yes | Type of database to deploy (e.g., postgresql, mongodb, redis). Use service_create_from_image for other types. |
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