Can only pull logs starting from most recent and can't go back further

[J8K0B]

Firstly: love the railway-mcp. Thank you for building this useful tool!

I've been using wiht Claude Code and it has been phenomenal in managing and maintaining my railway backend.

When trying to review error logs I run into an issue where I can't go back to older logs. The tool seems to be forced to start from the latest logs and comb through them to move further back, but the way the MCP tool is operating there is no way to just "jump" back 500, 1000, or more rows or to a specific time. This mean you have to consume ALL of the tokens between now and whatever period you're going back to. Depending on the verbosity of your console and debugging you may not get any further back than a few minutes before the LLM agent chokes on the context/tokens.

If there were a way to query logs by time or jump that would be excellent. If I have some downtime I may take a crack at it myself, in which case I will report back.

Thank you!

[jason-tan-swe]

Hey! Really glad you're enjoying using it (especially with Claude Code as I've never tested it with that!)

As for your issue, I do see that and you made a good observation. I'm currently battling the flu and finishing up my last semester of school (and will be vacationing for 2 weeks afterwards - think end of April). I do have some time between April 1 - 15 to tackle this, however, if you've gotten to it yourself feel free to contribute!

I've tried to detail the contributing as much as I can to add new features but I do think you just need to add onto the existing functionality of the logging tool. All the best and feel free to ask me any questions!

[ndneighbor]

Hi there, Angelo from Railway here, let us know if we can help out with providing the proper API endpoints to get you the log ranges of which you need.

[J8K0B]

Thanks guys! Really appreciate the work you put into this Jason.
Hope you feel better soon, get lots of rest and don't push yourself too hard --best of luck with the last semester!

I'm just finishing-up a couple of time-sensitive projects but once I've got those tidied-up I'll take a look here and see what I might be able to adjust. Angelo, those endpoints would be awesome. As noted in the initial report, the issue is that the current design only allows the MCP to pull ALL of the logs, starting from just now and working its way back. It doesn't permit me to either choose a specific time (e.g. 22:00:00), or a relative time (e.g. 3 hours ago), or to select/skip by # of logs (e.g. only pull most recent logs rows 500-700, etc,). I haven't yet had a chance to take a deeper peek at Jason's repo here to see what might need to be adjusted to facilitate, so that will be my first step.