Pulls the runtime logs behind a failing deploy, reports environment status, changes build and deploy settings, and audits tokens and integrations.
18actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro 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.
Ayro 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.
Ayro 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.
Each card is one request a support team gets, and the Railway actions Ayro runs to close it.
Ayro 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.
Ayro 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.
Ayro 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.
Ayro 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.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Railway actions it has and picks the ones a request needs.
Authorize the Railway account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Railway actions that close it and chains as many as the request needs.
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 freeRailway · Ayro
What can you do in Railway without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro 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 Ayro 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.
All 18 actions your agent can call on Railway, straight from the live MCP connection.
Creates a new plugin in Railway for the specified project.
Delete a Railway environment variable.
Permanently delete a persistent volume and all its associated data from Railway.
Delete a Railway workspace and all data associated with it.
Disconnects the authenticated user's Railway account from Discord.
Retrieve runtime logs for a deployment.
Get details of a specific Railway environment by its ID, including service instances and deployment information.
Get information for a GitHub pull request associated with a Railway service.
Get the total kickback earnings for the authenticated Railway user.
Retrieve all API tokens for the authenticated user from Railway.
Retrieve all patches for a Railway environment using the GraphQL API.
Retrieve a list of GitHub repositories that Railway has access to.
Retrieve the list of GitHub scopes the user has installed the installation to.
Retrieve all integration auths for the authenticated user from Railway.
Retrieve notification deliveries for the authenticated user.
Fetch all trusted domains for the authenticated Railway workspace.
Update project settings and configuration on Railway.
Update build/deploy settings for a service in a specific environment on Railway.
Same connection, same setup. Pick the next one your team already uses.
Checks channel presence, publishes realtime and batch messages, sends push notifications, and maintains the Ably device registry.
Reads Bubble records by ID, creates them singly or in bulk, triggers your backend API workflows, and patches or deletes records that are wrong.
Reports what deployed and what is queued, summarises what a release contains, aborts a bad deployment, and stands new projects up against their servers.
Searches Hacker News discussions, resolves ranked story IDs into readable items, and reads Ask HN, Show HN, job, and user feeds.
Issues credentials over OpenID4VC and DIDComm, raises verification requests, maintains credential templates, and manages DIDComm connections.
Checks API health, lists organization certificates and projects, and reads the signing policies the connected user can submit against.

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