How to connect Railway to Codex

1. 1. Enable Railway in Metorial

   In your Metorial portal, enable the Railway MCP server and sign in with the account that owns the data. Access stays governed by your team policies.

2. 2. Add the server and sign in

   The Codex CLI, IDE extension and ChatGPT desktop app share this config.

   Copy

   codex mcp add metorial --url <your-magic-mcp-url>
   codex mcp login metorial

3. 3. Check the connection

   Type /mcp in Codex to see Metorial and its Railway tools.

• List Environments: List all environments in a Railway project (e.g., production, staging).
• List Deployments: List deployments for a service in a specific environment.
• Create Environment: Create a new environment in a Railway project.
• Update Volume: Rename a persistent storage volume.
• Delete Environment: Permanently delete an environment from a Railway project.
• Rollback Deployment: Roll back a service to a previous deployment.
• Delete Domain: Remove a domain from a Railway service.
• Get Service: Retrieve detailed information about a Railway service, including its environment-specific configuration (build settings, deploy settings, replicas, etc.) when an environment ID is…
• Cancel Deployment: Cancel an in-progress deployment.
• Create Project: Create a new Railway project.
• Update Service: Update a Railway service's metadata (name, icon) and environment-specific settings (build command, start command, replicas, region, health check, etc.).
• Set Variables: Create or update one or more environment variables for a service, or shared variables for an environment when serviceId is omitted.
• Get Domains: List all domains (both Railway-provided and custom) for a service in a specific environment.
• Delete Project: Permanently delete a Railway project and all its services, environments, and deployments.
• Trigger Deployment: Trigger a new deployment for a service in a specific environment.
• And 33 more on the Railway MCP server page.

• Limit which Railway tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
• Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
• Type /mcp in the composer to see the connected servers.
• Override the approval behavior for a single Railway tool with tools.<tool>.approval_mode.

Metorial is listed but tools are missing

Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.

Metorial times out at startup

Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.

Long tool calls fail after a minute

The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.