Codex mcp-server command removed: does Sume still work?

Yes. The removal hits the other direction. codex mcp-server made Codex itself an MCP server for other tools to call. Sume is an MCP server that Codex calls, and the changelog says Codex "continues to support connecting to external MCP servers through codex mcp." Nothing about the Sume connection changes.

The removal facts come from the Codex changelog, the Codex MCP page and the App Server page, all read 2026-09-29. Sume's side is in the MCP quickstart.

What exactly did Codex remove?

The changelog has two entries. On 2026-08-24 it deprecated the codex mcp-server command. On 2026-09-05 it announced that the command and the standalone codex-mcp-server binary were removed, and told owners of integrations that launch either one to update them before upgrading Codex.

Which direction does my setup run in?

If a script or another agent launched codex mcp-server so it could call Codex as a tool, that integration breaks and needs the app server. If you use Codex as the client that calls Sume's tools, you configure a server with codex mcp add and never touched the removed command.

The Codex MCP page describes the client side: codex mcp add takes a name and either a stdio command or, for a hosted server, --url. For a server that supports OAuth you then run codex mcp login <server-name>.

codex mcp add sume --url https://mcp.sume.com/mcp
codex mcp login sume
codex mcp list

Do the client settings change too?

No. The same MCP page lists startup_timeout_sec (default 10) and tool_timeout_sec (default 60) as per-server options in config.toml. Those apply to any server you add with codex mcp add, Sume included, and the removal of codex mcp-server does not touch them. A long Sume job is better handled by polling jobs_wait again than by raising the tool timeout, since each wait call returns within about a minute.

Is the app server a drop-in replacement?

Not for production, according to Codex. The changelog says the app-server command "is experimental and isn't supported for production workloads", and the App Server page repeats that for its WebSocket transport. It speaks JSON-RPC 2.0 like MCP does, but it is its own protocol, so moving an integration over is a rewrite of the client, not a flag change.

What should a Sume builder check?

Run codex mcp list and confirm Sume is there. If your CI called codex mcp-server to drive Codex, migrate that piece using the migration guidance linked from the changelog. Sume's own OAuth rules stay the same: the hosted server needs mcp:read, and write tools need the Write toggle at consent, as the OAuth page describes.