{"version":"2.1.268","anchor":"mcp-ui-shows-a-resolved-display-endpoint-instead-of-raw-comm","canonical_anchor":"mcp-ui-shows-a-resolved-display-endpoint-instead-of-raw-comm","heading":"MCP server screens show a resolved endpoint instead of the raw command","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/mcp-ui-shows-a-resolved-display-endpoint-instead-of-raw-comm","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### MCP server screens show a resolved endpoint instead of the raw command\n\nSettings screens for MCP servers now display a resolved displayEndpoint rather than the raw config command\n\n**What**\n\nThe Settings screens for MCP (Model Context Protocol) servers now compute a `displayEndpoint` value for each server, covering stdio, sse, http, and claudeai-proxy connection types. This is used across the server status\/detail panel, the tools-list screen, and the individual tool-detail screen.\n\n- The server detail panel now only shows a \"Command:\" row when the resolved endpoint actually differs from the raw command written in the config, showing the resolved endpoint in that case instead of the literal config string.\n\n- The tools-list and tool-detail screens now also receive this computed `displayEndpoint` value as part of the server information passed to them.\n\n**Why**\n\nRaw config commands can be less meaningful than the actual resolved connection endpoint. Showing the resolved endpoint (and only showing a separate command line when it adds information) makes it easier to understand what an MCP server actually connects to.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}