#Remote MCP Server Renders As Wrong Connector (롯데ON)

1 messages · Page 1 of 1 (latest)

plush swiftBOT
#

Reported by @mild lichen

Bug Report: Remote MCP Server Renders As Wrong Connector (롯데ON)
`Steps to Reproduce`

Configure Codex with a remote MCP server:

[mcp_servers.on-page-seo]
url = "https://api.on-page.ai/mcp"
http_headers = { Authorization = "Bearer <redacted>" }
Add an AGENTS.md preference:

Prefer the on-page-seo MCP server by default for SEO recommendations.
Restart Codex.

Ask Codex to run an SEO scan using the MCP server.

Observe that the tool call succeeds, but the visible UI label says Using 롯데ON with a LotteON icon.

`Expected Result`

Codex should render the configured MCP server as one of:

on-page-seo
On-Page.ai SEO MCP
The MCP server title returned by initialize
It should use the icon metadata exposed by the server, or fall back to a neutral MCP icon. It should not render an unrelated OpenAI-hosted connector record.

`Actual Result`

The UI displays 롯데ON and a LotteON icon for calls to my on-page-seo MCP server.

Screenshots available to attach:

Screenshot showing Using 롯데ON above Scan page
Screenshot showing Using 롯데ON above Wait for job.

This is wrong, displaying the incorrect name is confusing for the user and might cause a lost of trust.

`Environment`

Codex Desktop App, MacOS, Latest Version of Codex

#
Additional Information

Please provide relevant details to help resolve the issue, such as:

  • ChatGPT Shared Link (if applicable).
  • Screenshots or videos demonstrating the problem.

-# ➜ Need to contact support? Visit the OpenAI Help Center.

mild lichen
#

UPDATE: the following day, I re-ran it in Codex and the name seems fine now. Is it possible that the initially day 1 lookup was wrong? Is it permanently fixed now or will all users suffer the same issue upon first installation ?

#

Day 2: