feat(mcp): default new agent installs to the remote CLI proxy - #1094
Merged
Conversation
Non-interactive setup (`railway setup agent -y`, agents.sh, install --agents) and bare `railway mcp install` now configure `railway mcp proxy` by default. Keep `--remote` as a compatibility alias, add `--local` to opt back into the in-process server, and leave bare `railway mcp` unchanged for existing configs.
Pass --remote on non-interactive agents setup when the binary supports it so older CLIs still land on the proxy. Clarify --remote/--oauth/--local help text, warn when --remote is ignored with --oauth, and start the interactive MCP picker on the Remote default.
Collaborator
Author
|
Follow-up commit addresses the open pressure-test items on the CLI side:
Mono |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
railway mcp proxy→mcp.railway.com, auth viarailway login):railway setup agent -y/ non-TTY setuprailway mcp install(no flags)curl -fsSL agents.railway.com | sh/install.sh --agents--local→ old in-processrailway mcp--oauth→ plainhttps://mcp.railway.com(editor OAuth)--remotekept as a compatibility alias of the new defaultsetup agent/mcp install, their railway entry is updated to the proxy. That migration-on-rerun is intentional for this phase.railway mcpstill runs the local server. Users who never re-run setup/install keep local until the later runtime default flip.Why
Canary the remote-proxy path on new installs and voluntary re-runs before flipping bare
railway mcpfor everyone.Test plan
cargo test commands::setup::testscargo test from_flags_defaults_to_remote_proxycargo test mcp_install_subcommandcargo test setup_agent_subcommand$HOME:railway setup agent -ywritesargs: ["mcp","proxy"]mcp install/setup agent -ymigrates to proxyrailway mcp install --localstill writes localargs: ["mcp"]--localconflicts with--remote/--oauth