codex_mcp_interface.md documents app-server RPCs under mcp-server

What happened?

codex-rs/docs/codex_mcp_interface.md appears to document the app-server RPC surface while identifying the server binary as codex mcp-server / codex-mcp-server.

Examples from the doc:

• codex-rs/docs/codex_mcp_interface.md lists the server binary as codex mcp-server.
• The same document then lists app-server-style RPCs such as thread/start, turn/start, account/read, config/read, model/list, and others.
• It also says the types live in app-server-protocol and are consumed by the app server implementation.

However, the current codex mcp-server implementation appears to expose MCP tools such as codex and codex-reply through tools/list, while custom JSON-RPC requests are handled as method-not-found. The thread/* and turn/* APIs are documented under the app-server README.

Expected behavior

The documentation should clearly distinguish the codex mcp-server MCP tool surface from the codex app-server RPC surface, or point users to the correct server command for the listed thread/*, turn/*, account, config, and model APIs.

Additional context

I searched open issues and PRs for terms including codex_mcp_interface, thread/start, mcp-server, and app-server, and did not find an existing open item that appears to cover this specific doc mismatch.