Integration · Automate and collaborate

Railway and Meteor AI agents

Connect Railway to a Met: check projects, services, deploys, status, logs and feature flags with Railway's official MCP.

Book a demo See every integration

How does Railway connect to Meteor?

With the Railway ready connector, your Met uses Railway's official MCP server with the permissions the admin authorizes through OAuth, and only sees the workspaces and projects chosen when authorizing. It lists your projects, services and deployments, checks the live status of an environment and pulls build, deploy and HTTP logs, so it can tell you on WhatsApp why a service went down. Redeploying, creating projects and deployments, publishing artifacts, changing or deleting feature flags and handing requests to Railway's agent start turned off until the admin turns them on in Connections.

What it automates

What a Meteor Met does with Railway

Answer why a service went down

When you ask on WhatsApp what happened to your API or your site, the Met checks the environment status, lists the latest deployments and reads the build and deploy logs to tell you where it failed.

Redeploy when needed

Redeploying starts turned off. If the admin turns it on in Connections, the Met redeploys the service you name. That deploy reaches the environment where the service runs.

Turn a feature on or off with a feature flag

Changing a feature flag starts turned off. If the admin turns it on, the Met changes the value of a project feature flag, for example to switch on the new checkout. Railway needs admin permissions for that.

Hand a long problem to Railway's agent

If the admin turns on railway_agent, which starts turned off, the Met hands a multi-step diagnosis to Railway's agent, which can inspect services, diagnose failures and apply configuration changes on your behalf.

16 tools

Everything your Met can ask Railway for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`whoami`	Shows the Railway account that authorized the connection.
`list_projects`	Lists the Railway projects the connection can access.
`create_project`	Creates a new project in your Railway account. Starts turned off.
`list_services`	Lists the services in a Railway project.
`list_deployments`	Lists the deployments of your services on Railway.
`get_status`	Checks the live status of a Railway environment.
`get_logs`	Pulls build, deploy and HTTP logs to debug a service.
`redeploy`	Redeploys a service. Railway counts it among the destructive actions to review. Starts turned off.
`accept_deploy`	Commits the staged changes and deploys them. Railway marks it as destructive. Starts turned off.
`create_deployment`	Creates a new deployment on Railway. Starts turned off.
`deploy_artifact`	Deploys an artifact, such as a static page or a diagram, to a public URL with Railway Functions. Starts turned off.
`list_feature_flags`	Lists the feature flags of a Railway project.
`get_feature_flag`	Returns a feature flag of a Railway project.
`set_feature_flag`	Changes the value of a project's feature flag. Needs admin permissions in Railway. Starts turned off.
`delete_feature_flag`	Deletes a project's feature flag. Needs admin permissions in Railway and starts turned off.
`railway_agent`	Hands a natural-language request to Railway's agent for multi-step tasks, such as analyzing logs, debugging or configuring services. Starts turned off.

The limits

What the Railway integration does NOT do

We would rather say it here than have you find out during rollout.

It does not delete services, domains or volumes. Those tools belong to Railway's local server, which Met does not use; the hosted server only has feature flag deletion, which starts turned off.
It does not ask you for confirmation in the chat before redeploying, creating a project or changing a feature flag. Those actions start turned off; if the admin turns them on in Connections, the Met runs them.
It does not control step by step what Railway's agent does. railway_agent, which starts turned off, hands over the whole request, and that agent can apply configuration changes on your behalf.
It does not see more than you authorized. With OAuth you choose which workspaces and projects the connection can use, and Railway does not accept project tokens.
It does not pay your Railway plan. Whatever the Met creates or deploys runs on your account; Meteor does not resell the service.

Before you start

What you need to connect Railway

1

A Railway account with your projects

The account your team deploys with on Railway. When authorizing, you choose which workspaces and projects the Met can see.
2

Connect it in Met

In Met, open Connections → Railway → Connect. A Railway window opens so you sign in and authorize Met. Then the admin chooses which actions stay on.

Frequently asked questions

Questions about Railway and Meteor

Redeploying starts turned off. If the admin turns it on, the Met runs it when the conversation leads there; there is no confirmation step in the chat. If you do not want it to redeploy, leave it off in Connections.

It is a bridge to Railway's infrastructure agent. It takes a natural-language request and handles multi-step tasks, such as analyzing logs or configuring a service, with your account's permissions.

Yes. The connection's tokens are short-lived and can be revoked from your Railway account settings, besides disconnecting the connector in Met.

You do, with your Railway account and plan. Meteor does not resell Railway: the connector uses your company's account.

Step by step