# Codex CLI 0.170.0 adds experimental support for same-named MCP servers across environments

> Codex CLI 0.170.0 adds experimental support for using MCP servers with identical names in different environments without conflicts.

- Status: official (From the company, authors or authority themselves, with a link to their own page.)
- Topic: Products
- Published: 2026-11-18T03:45:39+00:00
- Updated: 2026-11-18T04:09:39.952449+00:00
- Web page: https://ai-news.ikangai.com/story/codex-cli-0-170-0-adds-experimental-support-for-same-named-mcp-servers-across-en/
- Seen in: Codex CLI releases
- Change: capability (New capability)
- Applies to: Codex CLI 0.170.0, multi_environment_mcp

## What changed

Identically named MCP servers in different environments are now kept separate instead of colliding, behind the multi_environment_mcp feature flag.

Codex CLI 0.170.0 adds experimental support for running identically named MCP servers in different environments, so two servers sharing a name no longer collide. The release notes list the change under New Features with the pull request reference #60905. The changelog entry for that pull request reads "Keep same-named MCP servers separate across environments."

The problem being fixed is one of identity. According to the pull request description, MCP servers discovered on different executors can share a name. Resolving them by name alone exposed only one of them and prevented tools and resources from being addressed independently. The change instead carries exact McpServerKey identities through catalogs, connections, tool calls, resources and approval tracking. Environment-scoped tools receive stable namespaces derived from their environment.

The pull request also changes how resources and permissions are handled. Scoped resource listings now include an environment_id, and resource requests accept it. The environment_id is required for environment-owned servers when multiple environments are selected. Server ownership is preserved through hooks, and scoped elicitation review uses the permissions of the environment that owns the server. These behaviors sit behind a feature flag. The description says the disabled-by-default multi_environment_mcp feature is what exposes environment-scoped servers, including multiple installations of the same plugin. Such servers are therefore exposed only when that feature is enabled.

The pull request description lists its testing as coverage for same-named servers across environments, independent calls and approvals, resource selection, plugin discovery, and rejection of hook changes to the tool environment. The pull request page includes no benchmarks or rollout timeline, and the release notes do not say when the flag is expected to become the default.

The same release contains several unrelated changes, including WebRTC negotiation for realtime voice calls in the TUI and refreshable authentication headers for OpenTelemetry HTTP exporters. The notes list those separately, and they are not part of the MCP change.

## Why it matters

Teams that run the same MCP server setup in several environments can avoid name collisions, but the feature is experimental and may change.

## What you can do

Teams using MCP servers across several environments can trial the experimental setting, while avoiding reliance on it in production until it stabilises.

## Original source

- [Release 0.170.0 · openai/codex · GitHub](https://github.com/openai/codex/releases/tag/rust-v0.170.0)
- [Keep same-named MCP servers separate across environments by copyberry(bot) · Pull Request #60905 · openai/codex · GitHub](https://github.com/openai/codex/pull/60905)

---

AI wrote this summary from the sources listed, and nobody reviewed it individually before publication. Check the original source before you rely on it.

Cite as: IKANGAI AI News, "Codex CLI 0.170.0 adds experimental support for same-named MCP servers across environments", 2026-11-18, https://ai-news.ikangai.com/story/codex-cli-0-170-0-adds-experimental-support-for-same-named-mcp-servers-across-en/
