I have to reconnect the MCP almost every morning (or maybe almost every second). Is there a reason the access tokens are that short-lived? It would be okay if the refresh process actually worked, but it does not seem to.
Maybe it’s a problem with Claude.ai or so, just wanted to point at it.
Hi @bjoern.wolf, thanks for flagging this — I’ll dig into it. Access tokens are issued with a 7-day TTL and refresh tokens with 30 days, so there’s something else going on that I’m missing. I’ll circle back as soon as I have a fix. Sorry for the inconvenience in the meantime.
Hi @bjoern.wolf, that should be fixed now. We were losing OAuth state on every restart of the MCP service, which is why you (and everyone else) kept getting kicked back to the Tempo sign-in screen. I’ve moved that state to durable storage so it now survives restarts and redeploys. Sessions are looking stable post-deploy on my end. Could you try reconnecting once and then leave it for a day? You shouldn’t have to re-authorize again.
If i am not totally wrong the integration now also shows permissions in Claude. Before that it was just a blank info page. But maybe I am also wrong in that
Interesting — I’ve been able to see the list of permissions for each tool for a while. I like that you can now set preferences for all of them at once, but for some reason it still asks if you want to allow the tool to run in the chat sometimes.