This release makes GitHub work out of the box and stops the adapter from asking you to approve the same project server again and again. The GitHub preset now signs in with your GitHub CLI login instead of a sign-in flow GitHub doesn't support. Saving direct tools in the MCP panel keeps the approval you already gave, and on Windows an approval holds no matter how the folder path is capitalized. The panel also shows a connected server's tools even when the server won't let them be cached, and MCP sampling now follows your Pi thinking level.
Highlights
- Connecting to GitHub works: the
/mcp-adapter setuppreset signs in withgh auth token. - No more repeated "Allow project MCP server?" prompts after saving direct tools, or when a Windows path is spelled with different capitalization.
- The MCP panel shows a connected server's tools and your saved direct tools, even for GitHub, whose tool list can't be cached.
- MCP sampling uses your Pi thinking level, so servers that sample through a reasoning-only model stop failing.
Need to know
If you added GitHub from the old /mcp-adapter setup preset, remove its github entry and add GitHub again from /mcp-adapter setup. You need the GitHub CLI installed and signed in (gh auth login).
Highlights
- The GitHub preset in
/mcp-adapter setupnow signs in with your GitHub CLI login, so connecting to GitHub works. - Saving direct tools in the MCP panel no longer brings back the "Allow project MCP server?" prompt for a server you already allowed.
- The MCP panel shows a connected server's tools and your saved direct tools, even for servers like GitHub that don't let their tool list be cached.
- MCP sampling uses your Pi thinking level, so servers that sample through a reasoning-only model stop failing.
Fixed
- The GitHub preset in
/mcp-adapter setupnow signs in with your GitHub CLI login (gh auth token). Before, it used MCP OAuth, which GitHub doesn't offer to apps it hasn't registered, so/mcp-auth githubalways failed with "does not support dynamic client registration". Installghand rungh auth loginfirst. If you added the old preset, remove itsgithubentry and add GitHub again from/mcp-adapter setup. Thanks to @Milor123 for #841. - When one config file gives a server a different
urlthan another file that set its headers or token, the adapter still leaves those credentials out so they aren't sent to the new address, but it now tells you at startup which server, which settings and which two files are involved. Before, the credentials disappeared silently and the server failed with sign-in errors. Thanks to @Milor123 for #841. - The MCP panel now lists the tools of a server you already connected to in this session, with your saved direct tools checked, even when the server doesn't let its tool list be cached, as with GitHub. Before, such a server showed "(not cached)" with no tools every time you opened the panel, so direct tools you had saved looked lost. Thanks to @Milor123 for #841.
- Saving direct tools in the MCP panel for a project server you already allowed no longer makes Pi ask "Allow project MCP server?" again on the next start or
/reload. Saving used to change the server's config in a way that cancelled your approval. A server you didn't allow still asks, and so does any other change to the server's config. Thanks to @Milor123 for #841. - Approving a project MCP server now sticks when Pi is started from the same folder spelled with different capitalization, such as
C:\Users\Meandc:\users\meon Windows. Before, each spelling counted as a separate project and asked "Allow project MCP server?" again. An approval saved under a differently capitalized spelling asks once more after this update. Thanks to @Milor123 for #841. - MCP sampling requests now use your current Pi thinking level, so a server that samples through a model that requires reasoning no longer fails with "Reasoning is mandatory for this endpoint and cannot be disabled". Before, sampling always ran with thinking off. On Pi 0.84 and 0.85 sampling still runs with thinking off. Thanks to @bardic for #846.