VS Code 1.138 Codex and MCP tools: one Sume server entry
VS Code 1.138 lets Codex use VS Code's built-in, extension and MCP tools. Add Sume as one remote MCP server at mcp.sume.com and verify with tools_list.
VS Code 1.138 says the Codex harness can use the full set of VS Code tools, including built-in, extension and MCP tools. Sume is a remote MCP server, so the one entry to add is the remote URL https://mcp.sume.com/mcp; then call tools_list from Codex to verify it sees the tools. The notes do not say which config file Codex reads there, so confirm that in your own setup.
The VS Code facts are from its 1.138 release notes; the Sume steps from the MCP quickstart, read 2026-10-01.
What does VS Code 1.138 say about Codex?
The notes describe an expanded Codex harness: continue sessions between the ChatGPT app and VS Code, choose between Copilot and ChatGPT subscriptions, and use VS Code tools. Under that last item they name built-in, extension and MCP tools. The page I read does not give a Sume-specific setup, so treat the rest below as Sume's own docs applied to it.
What do I add for Sume?
Sume's docs describe a remote MCP server entry and say the same URL works in Cursor, Claude Code, Codex and other remote MCP clients. The Cursor example in the quickstart is a mcpServers entry with a url; check your client's own config schema for the exact shape before pasting it.
| Item | Value |
|---|---|
| Remote URL | https://mcp.sume.com/mcp |
| Transport | Streamable HTTP MCP server |
| Sign-in | OAuth through the client; default scope is mcp:read |
| Verify | Call tools_list once; mcp_health also works |
How do I check that Codex sees the tools?
Ask the agent to call tools_list and summarize the result. The docs note that live ids use underscores and dotted aliases also work. If you only see read tools, the session has mcp:read; turn Write on at consent for mcp:write, or use an API-key session. Step-by-step VS Code setup is in Sume in VS Code via MCP.
Do I need one entry per client?
Sume does not require it: the endpoint is the same. Whether Codex in VS Code reads VS Code's MCP list or its own Codex config is a client question; confirm with tools_list in the session you actually use.
Sources
Related posts
More in Integrations
- 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.
- 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.
- VS Code 1.140 session authorization server: what Sume issues
VS Code 1.140 proposes a field naming the authorization server behind a session. For Sume, that server is the MCP origin, mcp.sume.com.
- 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.
Written by Sume