VS Code 1.141 shows discovered MCP servers: where is the Sume entry?
VS Code 1.141 (Oct 7, 2026) lists MCP servers found outside your mcp.json in the Customizations editor. Check there for Sume's URL and the credential it uses.
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.
| Question | Where to look | What a correct answer is |
|---|---|---|
| Which URL does the entry call? | Customizations editor, MCP Servers | https://mcp.sume.com/mcp |
| Is the transport HTTP? | Entry type | Streamable HTTP; Sume's docs say not to use SSE |
| Which credential does it use? | Ask the agent to call mcp_health | OAuth token or API key, reported by the health tool |
| Which tools can it see? | Ask the agent to call tools_list | Read-only tools for mcp:read; write and paid tools need mcp:write or an API key |
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.
Sources
Related posts
More in Integrations
- Zed 1.23.2 optional MCP fields fix: read Sume's tools_schema anyway
Zed 1.23.2 fixed OpenAI model calls to MCP servers that treated optional fields as required. For Sume, tools_schema shows which fields are required.
- Airtable counts failed runs too: a 100-item Sume batch on Free
Airtable counts a run each time a trigger fires, even if actions fail. If each of 100 Sume deliveries triggers one, the Free plan's 100 monthly runs are gone.
- Airtable Free has no Run a script action: start Sume runs elsewhere
Airtable says Run a script is not available on Free. Start Sume Format runs from a service you control, and let Airtable receive results as plain records.
- Airtable keeps run history 2 weeks on Free: store your Sume receipts
Airtable run history lasts 2 weeks on Free, 3 years on Enterprise. Save the Sume run id and output URL in the record so a holiday audit does not depend on it.
Written by Sume