Issues with MCP Servers

Hi Daniel, I wanted to report a few issues with MCP servers that I noticed.

1. Authentication seems to be required much more often than with other clients. I can especially compare it with Raycast AI Chat. In Raycast, I never had to log in again to reauthenticate their HTTP MCP. For BoltAI, it is necessary quite regularly. For Notion, it is extreme. You have to log in again after 30 minutes or one hour. It seems like only the access token from the JWT is being used, and once it expires, the refresh token is not used to obtain a new one.

2. For some MCP servers, the authentication workflow doesn’t work at all. One newer example I noticed is TickTick. https://help.ticktick.com/articles/7438129581631995904 It should work, but you simply get an authentication error after logging in and allowing the connection in the browser. Maybe that’s related to the fact that you can’t add URL-only MCPs like TickTick’s in Notion. You have to add at least one slash after the domain so the Add button becomes active and clickable.