VS Code 1.141 shows discovered MCP servers: where is the Sume entry?

In VS Code 1.141 you can see every MCP server the editor knows about, including Sume, in the Customizations editor: run "Chat: Open Customizations" and pick MCP Servers. The release notes of October 7, 2026 add a Preview feature that shows servers discovered outside your workspace mcp.json, from plugins, extensions and built-in integrations, so you no longer need "MCP: List Servers" to find them.

What changed

The VS Code facts come from the VS Code release notes (read 2026-10-07). The release notes do not say what the list shows about credentials, so this post only covers what you can check on the Sume side.

Check the entry

When a Sume entry shows up and you did not write it, the question is which URL and which credential it carries. The table separates what the editor tells you from what Sume tells you.

Duplicates

A server that arrives through a plugin or extension may not be the one you configured by hand. Two entries pointing at Sume with different credentials give two different tool lists, and an agent can pick either. Keep one entry per credential and name them clearly, for example one read-only OAuth entry and one API-key entry you use for batch work.

Unknown entries

Remove an entry you do not recognize before you sign in to it. If an API key sits in an entry or in chat history, the Sume docs say to rotate it from the dashboard. An MCP OAuth token is not a Sume API key, and the two should not be swapped.

Spend rules do not change

Sume's paid calls need an idempotency_key however the entry was added, and dry_run plus max_spend_usd apply to every session. The quickstart shows the JSON entry to use if you prefer to write it yourself.