a month ago
I feel like I have to reconnect my railway mcp >1x daily in claude code TUI. anyone have a workaround?
3 Replies
a month ago
If you're using the remote MCP server (mcp.railway.com), OAuth access tokens are short-lived (1 hour) and the client may not always refresh them seamlessly, which causes the disconnects. Switching to the local MCP server avoids this since it shares the CLI's persistent authentication. You can set it up by running railway mcp install --agent claude-code (without --remote).
Status changed to Awaiting User Response Railway • about 1 month ago
24 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 24 days ago
20 days ago
nobody else noticing this? it happens with codex too.
Status changed to Awaiting Railway Response Railway • 20 days ago
19 days ago
This affects the remote MCP server (mcp.railway.com), whose access tokens last one hour and aren't always refreshed cleanly by the client, which is why the same thing shows up in Codex. The local MCP server avoids it because it rides your CLI's persistent login. Run railway mcp install --agent claude-code without --remote and the daily reconnect goes away. See the MCP docs.
Status changed to Awaiting User Response Railway • 19 days ago
12 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 12 days ago