VS Code 1.140 multi-folder sessions: where to put the Sume MCP entry
VS Code 1.140 lets each chat use its own folder or worktree, and reads MCP servers from a global file or a workspace .mcp.json. Put Sume in the global one.
Put the Sume MCP entry in the global file, $COPILOT_HOME/mcp-config.json (or ~/.copilot/mcp-config.json), when you use VS Code 1.140 multi-folder sessions. Per the release notes each chat can use its own folder or worktree, and a workspace .mcp.json belongs to one workspace root. A global entry gives every chat one Sume connection without copying a file into each folder.
The VS Code facts are from the 1.140 release notes, published September 30, 2026 and read 2026-10-01. The notes do not say how a workspace .mcp.json is resolved across several folders, so the global file is the choice that does not depend on it.
What are multi-folder sessions?
Experimental in 1.140: the notes say they let you coordinate related work across repositories or isolated worktrees in one session, and that each chat uses its folder for its terminal, tasks, changes, pull request and Agent merge state. The point is isolation between chats.
Which two places can hold the MCP entry?
The release notes name two portable destinations, and the MCP: Add Server flow can write to either.
| Location | Scope | Good for Sume? |
|---|---|---|
$COPILOT_HOME/mcp-config.json | Global, all workspaces | Yes: one entry for every chat |
.mcp.json at the workspace root | One workspace | Only if every repo needs the same entry |
What does the Sume entry say?
The URL is the hosted endpoint, https://mcp.sume.com/mcp, from the quickstart. Use OAuth for interactive work; the consent page on the MCP host grants mcp:read and, if you turn Write on, mcp:write. For an API key, send it as a bearer or x-api-key header and keep it out of a workspace file that gets committed.
Why not commit a .mcp.json with the key?
An API-key session sees Sume's full tool set, paid tools included, per OAuth and API keys, and the docs say to rotate a key that shows up in logs or chat history. A workspace file travels with the repository. The global file stays on your machine. A repo can safely hold the URL only, with each developer signing in over OAuth.
Sources
Related posts
More in Integrations
- VS Code remote delegation: whose Sume credit is used?
VS Code 1.140's remote delegation tools are off by default and normal approvals still apply. Sume spend follows the credential the session connects with.
- Zapier action timeout at 30 seconds: use Sume webhook mode
Zapier actions time out at 30 seconds, so submit Sume jobs with mode webhook: the call returns a job id at once and Sume posts the result to your URL later.
- Zapier Catch Hook 404 when the Zap is off: Sume webhook retries
A turned-off Zap now returns 404 to Catch Hook. For a Sume job that is a failed delivery attempt: it retries up to 10 times, then redeliver or poll recovers.
- Zapier Functions shut down Sept 1: move media calls to Sume async
Zapier Functions stopped running on 2026-09-01. Move a media-API step to Code by Zapier and submit a Sume job async or by webhook instead of waiting on it.
Written by Sume