railway-mcp

by jason-tan-swe
Verified

domain_create

[API] Create a new domain for a service

⚡️ Best for: ✓ Setting up custom domains ✓ Configuring service endpoints ✓ Adding HTTPS endpoints

⚠️ Not for: × TCP proxy setup (use tcp_proxy_create) × Internal service communication

→ Prerequisites: service_list, domain_check

→ Alternatives: tcp_proxy_create

→ Next steps: domain_update

→ Related: service_info, domain_list

Input Schema

NameRequiredDescriptionDefault
domainNoCustom domain name (optional, as railway will generate one for you and is generally better to leave it up to railway to generate one. There's usually no need to specify this and there are no use cases for overriding it.)
environmentIdYesID of the environment
serviceIdYesID of the service
suffixNoSuffix for the domain (optional, railway will generate one for you and is generally better to leave it up to railway to generate one.)
targetPortNoTarget port for the domain (optional, as railway will use the default port for the service and detect it automatically.)

Input Schema (JSON Schema)

{ "$schema": "http://json-schema.org/draft-07/schema#", "additionalProperties": false, "properties": { "domain": { "description": "Custom domain name (optional, as railway will generate one for you and is generally better to leave it up to railway to generate one. There's usually no need to specify this and there are no use cases for overriding it.)", "type": "string" }, "environmentId": { "description": "ID of the environment", "type": "string" }, "serviceId": { "description": "ID of the service", "type": "string" }, "suffix": { "description": "Suffix for the domain (optional, railway will generate one for you and is generally better to leave it up to railway to generate one.)", "type": "string" }, "targetPort": { "description": "Target port for the domain (optional, as railway will use the default port for the service and detect it automatically.)", "type": "number" } }, "required": [ "environmentId", "serviceId" ], "type": "object" }