The MCP client shipped a built-in tool-list cache. It fought the package's thin, app-owns-storage philosophy and added a per-user cache-scoping footgun. It also kept getting more awkward as the OAuth work landed: the API for configuring it grew weirder the more cases it tried to cover. In practice most apps don't need to cache the tools list at all, and the ones that do already have a cache they trust. So this hands caching back to the application. The package just gives you a correct tools list, and you store it however you like.

Before, you configured caching through the package:

Mcp::registerClient('github', fn () => Client::web($url), cacheTtl: 3600, scope: fn () => auth()->id());
$tools = Mcp::client('github')->tools();   // RegisteredClient wrapper, cached for you
Mcp::client('github')->flushCache();

After, registration is just a name and a factory, and the tools list is a plain value you can cache directly:

Mcp::registerClient('github', fn () => Client::web($url));

// no cache: just fetch
$tools = Mcp::client('github')->tools();

// app-owned cache: the tools list is plain data, so cache it as-is under your own key
$tools = Cache::remember('mcp:github:tools', 3600, fn () => Mcp::client('github')->tools());