Skip to content

Commit b4c984e

Browse files
authored
fix(ci): unbreak main — drop the unused MCP_SERVER_NAME export (#10195)
dead-exports:check, part of test:ci, is red on a clean main, so every open PR inherits the failure and none can go green. Third instance of this class after #9944 and #10109. #10177 added `export const MCP_SERVER_NAME` in src/mcp/server.ts. Both readers live in that same file -- the handshake's serverInfo.name and the analytics property builder -- so the export has no consumer. CHAT_GROUNDING_MCP_SERVER_NAME in the engine is a separate symbol, not this one re-exported. No behaviour change: the constant and both call sites are untouched, and its "one constant so the handshake and the dashboards cannot disagree" rationale still holds. It is simply module-local now. Closes #10194
1 parent f1a0a32 commit b4c984e

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

src/mcp/server.ts

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -859,8 +859,9 @@ export function isMcpAdminEnabled(env: Env): boolean {
859859

860860
/** The MCP `serverInfo.name` this server reports, and the `$mcp_server_name` its analytics carry.
861861
* One constant so the handshake a client sees and the dashboards an operator reads can never
862-
* disagree about what this server is called. */
863-
export const MCP_SERVER_NAME = "loopover";
862+
* disagree about what this server is called. Module-local: both readers (the handshake's serverInfo and
863+
* the analytics property builder) live in this file, and #10177 exported it without a consumer outside it. */
864+
const MCP_SERVER_NAME = "loopover";
864865

865866
export class LoopoverMcp {
866867
private accessScopePromise: Promise<ControlPanelAccessScope> | null = null;

0 commit comments

Comments
 (0)