Railway CLI
The Railway hosting CLI: deploy and manage projects, plus one command that installs Railway skills and MCP for your agents
- 628 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Deploys services and changes production environment variables
- Handles account and project tokens
- Installs from a remote script and updates in the background
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/railway-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Deploys services and changes production environment variables
- Handles account and project tokens
- Installs from a remote script and updates in the background
This is third-party code. Review the repository files before installing.
What it does
The CLI manages Railway projects from the terminal: login, deploys with railway up, and project or account tokens for CI. The railway setup agent command detects installed agents such as Claude Code, Cursor, Codex, OpenCode and GitHub Copilot, installs Railway skills and connects the remote MCP server through railway mcp proxy using the CLI login. You can pick a local GraphQL-backed MCP server instead. Skills update along with the CLI without overwriting local edits. The CLI can also launch cloud agents on dedicated VMs via railway code.
Who it is for. For developers who host apps on Railway and want the agent to deploy and configure services.
Good fit when
- You want Railway wired into every agent on the machine with one command
- The agent should deploy a service or change environment variables
- You need token-based deploys in CI
Not a fit when
- You do not host on Railway
- You cannot install via a curl script or allow background auto-updates
Example request
Deploy this project to Railway and add a DATABASE_URL variableLimitations
Requires a Railway account, and most features are paid. The install script supports macOS, Linux and Windows via WSL; other methods are in the docs. CLI and skill auto-updates are on by default and can be turned off with railway autoupdate disable. Railway availability and payment from Russia are unverified.
How to disable. Uninstall the CLI with bash <(curl -fsSL cli.new) -r, then remove the Railway MCP server from agent configs and the Railway skills from their folders.
FAQ
How does remote MCP differ from local?
By default the remote Railway server is connected through railway mcp proxy using the CLI login. The --local flag installs a local GraphQL-backed server instead.
Can I install only skills or only MCP?
Yes: railway skills --agent claude-code installs skills, railway mcp install --agent cursor connects MCP.
Discussion
No questions or reviews yet.
Related
CLI toolsThe official Railway plugin: the use-railway skill and a hosted MCP server for deploys, variables, domains, logs and tracing from your agent
Self-hosted MCP server for running commands on remote servers over SSH, with tokens and roles
A secure MCP runtime through which an agent operates local machines, servers and containers
An MCP server and CLI that lets an agent query and provision cloud, SaaS and API resources with plain SQL
A self-hosted control center for coding agents: Claude Code, Codex, Copilot, OpenCode and Pi from your phone, desktop and terminal
MCP SSH Manager
mcp-ssh-manager
Managing several SSH connections from Claude Code and Codex: commands, file transfer, databases and backups
README in short
The README covers the install script with or without agent setup, login and CI tokens. The agent section explains railway setup agent, separate commands for skills and MCP, and the local server option. Most of the README is about Railway cloud agents: running Codex, OpenCode and Claude on VMs, connecting from desktop clients and SSH. This CLI replaces the archived railway-mcp-server.