Railway

Railway MCP integration

Pulls the runtime logs behind a failing deploy, reports environment status, changes build and deploy settings, and audits tokens and integrations.

18actions available

Three actions you can hand over today

Every action runs live through MCP. Nothing to build, nothing to maintain.

  • Get deployment logs

    Lyro retrieves the runtime logs for a deployment and reads them back in context. Whoever reported the outage sees what actually failed instead of waiting for someone to open the dashboard.

  • Get github pr info

    Lyro looks up the GitHub pull request tied to a Railway service. The change behind a given deploy is identified in the conversation, so a rollback decision is made against the real diff.

  • Create plugin

    Lyro creates a new plugin on the project you name. A database or cache is provisioned as part of the conversation rather than queued behind a platform-team request.

See all 18 actions

How businesses use Railway + Lyro

Each card is one request a support team gets, and the Railway actions Lyro runs to close it.

  • Get to the log line behind a failing deploy

    Lyro pulls a deployment's runtime logs newest first, reads the environment to see which service instances are running and how their latest deployments ended, and checks the linked pull request.

    Get Deployment LogsGet EnvironmentGet GitHub PR Info
  • Change how a service builds and runs

    Lyro updates a service instance's start and build commands, root directory, healthcheck, replicas, region, restart policy, or cron schedule, and adjusts project-level PR deploy settings.

    Update Service InstanceUpdate ProjectCreate Plugin
  • Clean up infrastructure nobody is using

    Lyro removes an environment variable, a persistent volume, or an entire workspace, each of which is irreversible, so these run only once a human has confirmed the target.

    Delete VariableDelete VolumeDelete Workspace
  • Audit what is connected to the account

    Lyro lists the API tokens with their names and creation dates, the connected integrations such as GitHub, GitLab, or Vercel, and the trusted domains that let people join the workspace uninvited.

    List API TokensList Integration AuthsList Railway Trusted Domains

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Railway actions it has and picks the ones a request needs.

  1. 01

    Connect Railway

    Authorize the Railway account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.

  2. 02

    Tell your agent what you need

    Describe the job the way you would hand it to a teammate. Lyro maps it to the Railway actions that close it and chains as many as the request needs.

  3. 03

    Watch it work

    The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.

    Get started free
Railway · Lyro

Everything else about Railway

Setup, permissions, and the limits of what Lyro can do inside Railway.

  • No. List GitHub Writable Scopes explicitly requires account-level authentication and will not run on a workspace or project token, so Lyro needs the right credential for that one. Project-scoped work such as Get Deployment Logs and Update Service Instance runs fine on the project's own credentials.

Every action available in Railway

All 18 actions your agent can call on Railway, straight from the live MCP connection.

  • Create plugin

    Creates a new plugin in Railway for the specified project.

  • Delete variable

    Delete a Railway environment variable.

  • Delete volume

    Permanently delete a persistent volume and all its associated data from Railway.

  • Delete workspace

    Delete a Railway workspace and all data associated with it.

  • Disconnect discord account

    Disconnects the authenticated user's Railway account from Discord.

  • Get deployment logs

    Retrieve runtime logs for a deployment.

  • Get environment

    Get details of a specific Railway environment by its ID, including service instances and deployment information.

  • Get github pr info

    Get information for a GitHub pull request associated with a Railway service.

  • Get user kickback earnings

    Get the total kickback earnings for the authenticated Railway user.

  • List API tokens

    Retrieve all API tokens for the authenticated user from Railway.

  • List environment patches

    Retrieve all patches for a Railway environment using the GraphQL API.

  • List github repos

    Retrieve a list of GitHub repositories that Railway has access to.

  • List github writable scopes

    Retrieve the list of GitHub scopes the user has installed the installation to.

  • List integration auths

    Retrieve all integration auths for the authenticated user from Railway.

  • List notification deliveries

    Retrieve notification deliveries for the authenticated user.

  • List railway trusted domains

    Fetch all trusted domains for the authenticated Railway workspace.

  • Update project

    Update project settings and configuration on Railway.

  • Update service instance

    Update build/deploy settings for a service in a specific environment on Railway.

Ready to connect Railway?

Authorize the account and your agent has all 18 actions from the first conversation.

Support agent working at a laptop next to the Lyro mascot