Developer tools
Railway for AI agents.
Managed auth, ready-made tools.
List projects and services, read deployment logs, redeploy and set variables in Railway on behalf of each of your users.
About Railway
With the Railway connector, your agent works in each user’s own Railway account. It can list projects and services, check recent deployments and their logs, redeploy a service and set an environment variable, using only the tools your project allows.
Railway is a cloud platform for deploying apps, databases and services from code.
Tools
What your agent can do in Railway.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Railway connection.
-
List projects
Readrailway_list_projectsList the user's Railway projects.
-
List services
Readrailway_list_servicesList the services in a project.
-
List deployments
Readrailway_list_deploymentsList recent deployments of a service with their status.
-
Get deployment logs
Readrailway_get_deployment_logsRead the build or runtime logs of a deployment.
-
Redeploy
Writerailway_redeploy_deploymentRedeploy an existing deployment.
-
Restart a deployment
Writerailway_restart_deploymentRestart a running deployment.
-
Set a variable
Writerailway_upsert_variableCreate or update an environment variable for a service.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Railway, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Let the agent read deployments and logs, and switch off
railway_upsert_variableso it can never change an environment variable. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use, for example deployments and logs but not variables. A call outside them is refused.
Get started
Connect Railway
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Railway
Each end user authorizes their own Railway account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Railway account, once. const connection = await agent200 .user("user_123") .connect("railway"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Railway tools
Name the user, the model and the tools. The model decides which Railway tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Why did the last deploy of my API fail", tools: ["railway"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on Railway's own sign-in page. You never see or store their Railway password.
-
What access is requested
The scopes the connection needs, such as reading projects, reading deployments or managing services, listed on Railway's authorization screen. Users can remove the app later from their Railway account settings.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Railway connector and how to use it.
Connector: Railway, through Agent200. In code: "railway". What it does: List projects and services, read deployment logs, redeploy and set variables in Railway on behalf of each of your users. Page: https://www.agent200.com/connectors/railway/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Railway's own page, through the authorization link Agent200 returns. Never ask a user for a Railway password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: railway_list_projects, railway_list_services, railway_list_deployments, railway_get_deployment_logs. Write tools: railway_redeploy_deployment, railway_restart_deployment, railway_upsert_variable. Name "railway" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/connectors/railway/framework/claude/ https://www.agent200.com/connectors/railway/framework/chatgpt/ https://www.agent200.com/connectors/railway/framework/claude-code/ https://www.agent200.com/connectors/railway/framework/muse/ https://www.agent200.com/connectors/railway/framework/grok-bot/ https://www.agent200.com/connectors/railway/framework/openai-dots/ https://www.agent200.com/connectors/railway/framework/claude-duet/ https://www.agent200.com/connectors/railway/framework/hermes-agent/ https://www.agent200.com/connectors/railway/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /connectors/railway.md
Guides
Use Railway with the AI you build on.
Step-by-step setup for Railway with a specific model, assistant or agent framework.
-
Railway + Claude
How to connect Railway to Claude
-
Railway + ChatGPT
How to connect Railway to ChatGPT
-
Railway + Claude Code
How to connect Railway to Claude Code
-
Railway + Muse
How to connect Railway to Muse
-
Railway + Grok Bot
How to connect Railway to Grok Bot
-
Railway + OpenAI Dots
How to connect Railway to OpenAI Dots
-
Railway + Claude Duet
How to connect Railway to Claude Duet
-
Railway + Hermes Agent
How to connect Railway to Hermes Agent
-
Railway + OpenClaw
How to connect Railway to OpenClaw
FAQ
Railway and Agent200, answered.
Who handles the Railway OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Railway.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Railway connection, never another user's. It cannot reach anything the user or Railway has not authorized.
Can I limit what my agent can do in Railway?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.