Support remote MCP servers

The following works for me

[mcp_servers.server-name]
command = "npx"
args = ["mcp-remote", "<remote_ip:port>", "--header", "<header>"]

@samarth-gupta can you provide a working example for an actual remote MCP, such as the official github MCP?

@nick-youngblut DeepWiki is a very popular remote MCP. It supports sse and http transport.

https://docs.devin.ai/work-with-devin/deepwiki-mcp#deepwiki-mcp-server

The following works for me [...] npx mcp-remote ...

From the mcp-remote github.

Note: this is a working proof-of-concept but should be considered experimental.

I'm unwilling to use experimental NPM packages in light of the recent supply chain attacks.

+1, not having out-of-the-box support for remote mcp servers e.g. streamable-http is a huge gap.

Codex should support remote mcp servers natively without relying on external libraries or scripts.

Most of the servers we're working on are now remote HTTP servers. Hopefully this is added soon!

Also seeking native support for remote mcp servers. Thank you!

yes please i'm going crazy trying to find/build workarounds. also https://github.com/openai/codex/issues/3666 would be nice.

https://github.com/openai/codex/commit/3a1be084f911badd12a1fd1c1c6ca1b6c14eaa03

looks like something is brewing

Wild that this isn't supported yet—throwing in my +1

Support for remote MCP is available at some level now: https://github.com/openai/codex/blob/main/docs/config.md#streamable-http

in ~/.codex/settings.toml I can now do this and it works

[mcp_servers.deepwiki]
url = "https://mcp.deepwiki.com/mcp"
enabled = true

Is this still not supported yet? I tried adding a streamable HTTP MCP with OAuth as an authentication method. It's odd that it connects properly, but doesn't display any supported tools. Anyone facing the same issue?

Some MCP servers (e.g., Asana MCP v2) require specifying a client ID and client secret and do not support dynamic client registration (DCR). I don’t think Codex currently provides a way to configure this (please correct me if I’m wrong).

As a workaround, I’m proxying the MCP connection via mcp-remote.

[mcp_servers.asana]
command = "npx"
args = [
  "-y",
  "mcp-remote",
  "https://mcp.asana.com/v2/mcp",
  "--static-oauth-client-info",
  "@<path-to-your-client-info.json>",
]
startup_timeout_sec = 60

client-info.json:

{
  "client_id": "...",
  "client_secret": "..."
}

It would be great to have an official method in Codex to support this use case.

As of 2026-03-11, Codex supports remote MCP servers: https://developers.openai.com/codex/mcp#supported-mcp-features

However, Codex does _not_ support the Client ID Metadata Documents client registration mechanism. This is the issue that @rayjasson98 brought up above, and is also a blocker for the Slack MCP:

We do not support SSE-based connections or Dynamic Client Registration at this time.

at https://apilabs.ai we are publishing remote MCP server and would like to integrate with Codex like claude desktop.

Closing as resolved: remote MCP servers are supported. The remaining OAuth registration limitation is tracked in #13200.