Codex 0.160.1 remote stdio MCP fix: does it affect Sume?

Codex 0.160.1 preserves SYSTEMROOT, TEMP and TMP for remote stdio MCP launches on Windows hosts. Sume's hosted MCP is HTTP, so no process is launched.

3 min readSume
All posts

No. The Codex 0.160.1 fix is about remote stdio MCP servers: it preserves SYSTEMROOT, TEMP and TMP when a launch happens on a Windows host. Sume's hosted server is a streamable HTTP endpoint at https://mcp.sume.com/mcp, so Codex does not start a process for it and has no environment to inherit.

Why the difference matters

A stdio server is a child process. Anything it needs from the OS, like temp directories, comes from the environment the launcher passes down. That is the failure the release addresses. An HTTP server is just a URL plus a login, so the failure class does not apply.

If a Windows setup still fails with Sume

Look at the connection and sign-in instead: the URL, the OAuth login for the configured server name, and the scope you granted. The quickstart says the client discovers Sume's protected-resource metadata from the MCP endpoint and is sent to https://mcp.sume.com/oauth/authorize, then on to the consent page.

One thing is easy to confuse: Sume has no local stdio server to launch. Do not configure a stdio entry for Sume. Use the URL.

Stdio versus Sume hosted MCP, read 2026-10-07
QuestionRemote stdio serverSume hosted MCP
TransportChild processStreamable HTTP
Needs SYSTEMROOT, TEMP, TMPYes, from the launcherNo process
AuthWhatever the server doesOAuth (mcp:read, optional mcp:write) or API key
Entry in configcommand and argsURL only

Sources

Related posts

More in Developers

All Developers posts

Written by Sume