1.3.12
Connect the servers that would not connect
MCP servers that sign you in through your browser now work, Supabase among them — it could not be connected at all before. The ones that still cannot connect tell you why, Padar only asks for a token where a server actually wants one, and the servers your Claude Code plugins already have are one tick from being imported.
New
- DesktopSign in to MCP servers that register themselves, Supabase among them. Press Connect and authorize in your browser — no token to find and paste.
Improved
- DesktopThe MCP list is there in a conversation even when nothing loaded, and says that the list is read once when a conversation starts — so a server you have just added arrives on the next one.
- DesktopA server that cannot connect says what went wrong instead of showing a number. In a teammate's workspace, their servers are labelled as theirs rather than as yours.
- DesktopDeclaring a server that no workspace could run warns you first — a command that is not there, an address that only exists on your own machine, a value your shell sets that a workspace has no way to know.
- EngineServers that run on bun work in a workspace. They had no way to run at all before.
Fixed
- DesktopPadar asks for a token only where a server wants one. A server that needs no credential used to show an empty field for one anyway, which read as something you had forgotten to fill in.
- DesktopA server that needs signing in now says so about itself. Beside a list of names, in an app you are already signed in to, "needs sign-in" looked like it meant you.
- DesktopImporting finds every server your plugins declare. Supabase's was missed completely, so the easiest way to add it was the one that did not work.