Claude Code list_changed and reconnect: refresh Sume tools

Claude Code refreshes a server's tools when it receives a list_changed notification, and you can reconnect from /mcp to pick up changes sooner. Sume's docs do not say the hosted server sends that notification, so after changing consent, call tools_list to see what the session really offers.

Claude Code behavior is from its MCP page; Sume behavior from MCP tools and gates and the quickstart, read 2026-09-30.

What does Claude Code say it does?

The page says Claude Code supports list_changed and refreshes capabilities from that server automatically. It also says to reconnect from /mcp to pick up changes sooner.

Why would Sume's tool list change?

Because visibility depends on the session. The docs say mcp:read sessions see read-only tools, while mcp:write sessions see mutating and paid tools. The tools_list tool returns the list visible to the current session, so a read-only session and a write session show different lists.

How do I pick up a consent change?

Run the login again, turn Write on at the consent page, then reconnect. The quickstart shows the two commands to connect: claude mcp add --transport http sume https://mcp.sume.com/mcp and claude mcp login sume. Then ask Claude to call mcp_health and tools_list.

claude mcp login sume
# in Claude Code:
# /mcp   -> reconnect the sume server
# ask: call tools_list and list the paid tools you can see

What if the paid tools are still missing?

Write was probably left off on the consent page, where the toggle defaults off. Grant mcp:write, or use an API-key session. There is no mcp:paid scope.

Is a refreshed list the same as a new grant?

No. A refresh re-reads what the server offers to the token you already hold. A token issued with only mcp:read still sees read-only tools after any refresh. Write access comes from the consent step, so the fix for missing paid tools is a new login with Write on, or an API-key session, not a longer wait for a notification.