railway-domain

davila7's avatarfrom davila7

Add, view, or remove domains for Railway services. Use when user wants to add a domain, generate a railway domain, check current domains, get the URL for a service, or remove a domain.

⭐15.4kstars🔀1.3kforks📁View on GitHub🕐Updated Jan 11, 2026⬇️1downloads

When & Why to Use This Skill

This Claude skill facilitates efficient domain management for Railway services, allowing users to programmatically add, view, or remove both Railway-provided and custom domains. It simplifies the deployment workflow by generating necessary DNS records and providing instant access to service URLs, ensuring seamless connectivity for cloud-hosted applications.

Use Cases

  • Automated URL Generation: Quickly generate a default railway.app domain for new service deployments to enable immediate public access and testing.
  • Custom Domain Configuration: Streamline the process of linking professional branded domains by retrieving required CNAME and DNS records automatically for manual provider setup.
  • Infrastructure Auditing: Retrieve a comprehensive list of all active domains and networking configurations associated with specific environments or services.
  • Domain Cleanup: Easily remove deprecated or incorrect domain mappings to maintain infrastructure hygiene and prevent routing conflicts.
namerailway-domain
descriptionAdd, view, or remove domains for Railway services. Use when user wants to add a domain, generate a railway domain, check current domains, get the URL for a service, or remove a domain.
version1.0.0
authorRailway
licenseMIT
tags[Railway, Domain, DNS, URL, Custom Domain, Infrastructure]
dependencies[railway-cli]
allowed-toolsBash(railway:*)

Railway Domain Management

Add, view, or remove domains for Railway services.

When to Use

  • User asks to "add a domain", "generate a domain", "get a URL"
  • User wants to add a custom domain
  • User asks "what's the URL for my service"
  • User wants to remove a domain

Add Railway Domain

Generate a railway-provided domain (max 1 per service):

railway domain --json

For a specific service:

railway domain --json --service backend

Response

Returns the generated domain URL. Service must have a deployment.

Add Custom Domain

railway domain example.com --json

Response

Returns required DNS records:

{
  "domain": "example.com",
  "dnsRecords": [
    { "type": "CNAME", "host": "@", "value": "..." }
  ]
}

Tell user to add these records to their DNS provider.

Read Current Domains

Use railway-environment skill to see configured domains, or query directly:

query domains($envId: String!) {
  environment(id: $envId) {
    config(decryptVariables: false)
  }
}

Domains are in config.services.<serviceId>.networking:

  • serviceDomains - Railway-provided domains
  • customDomains - User-provided domains

Remove Domain

Use railway-environment skill to remove domains:

Remove custom domain

{
  "services": {
    "<serviceId>": {
      "networking": {
        "customDomains": { "<domainId>": null }
      }
    }
  }
}

Remove railway domain

{
  "services": {
    "<serviceId>": {
      "networking": {
        "serviceDomains": { "<domainId>": null }
      }
    }
  }
}

Then use railway-environment skill to apply and commit the change.

CLI Options

Flag Description
[DOMAIN] Custom domain to add (omit for railway domain)
-p, --port <PORT> Port to connect
-s, --service <NAME> Target service (defaults to linked)
--json JSON output

Composability

  • Read domains: Use railway-environment skill
  • Remove domains: Use railway-environment skill
  • Apply removal: Use railway-environment skill
  • Check service: Use railway-service skill

Error Handling

No Service Linked

No service linked. Use --service flag or run `railway service` to select one.

Domain Already Exists

Service already has a railway-provided domain. Maximum 1 per service.

No Deployment

Service has no deployment. Deploy first with `railway up`.

Invalid Domain

Invalid domain format. Use a valid domain like "example.com" or "api.example.com".