Skip to content

MCP server version strings are hardcoded and stale (0.5.2 / 0.6.0 vs 0.7.1) #23

Description

@vincentvella

Problem. The version advertised to MCP clients is hardcoded and out of date:

  • src/mcpServer.ts:12buildMcpServer(name = "devloop-mcp", version = "0.5.2")
  • src/daemonClient.ts:64,67 — Client/Server both version: "0.6.0"

package.json is at 0.7.1, so every connecting MCP client (and the daemon bridge) sees a wrong, stale server version.

Proposed. Import the real version once and use it everywhere:

import pkg from "../package.json" with { type: "json" };
// buildMcpServer(name = "devloop-mcp", version = pkg.version)

Thread it through daemonClient.ts too. Optionally add a tiny assertion in the smoke/selftest that the advertised version equals package.json's, so it can't drift again.

Affected: src/mcpServer.ts, src/daemonClient.ts.

Filed from the weekly repo audit (verified against current source).

Metadata

Metadata

Assignees

Labels

tech-debtCode health / refactor / debt

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions