lemmego / cli / 39477266515

61%

push

github

Wire the MCP server into the scaffold, registered outside production only

A new project is now agent-ready without hand-editing providers.go:
`lemmego new` registers &mcp.Provider{} and `lemmego mcp:install`
configures the editor.

On by default, with --mcp=false to opt out, because the point of it is
that a project works with an agent before anybody configures anything.
The cost was measured rather than assumed — 6 modules, 27 packages and
2.4MB on a 64.7MB binary, so about 3.8% — which is nothing like the
weight that made lemmego/log standard-library-only.

**Registered only outside production.** The provider serves this
application's configuration and database to whatever starts it. It is
stdio-only, so this is not a hole being closed — it is not reachable
over the network — but a production binary should not carry a command
that reads the database, and the guard says so where somebody will read
it. Verified on a real binary: `mcp:serve` is listed with
APP_ENV=development and absent with APP_ENV=production.

LoadProviders returns a variable now rather than a literal, which is
what makes a conditional provider expressible at all.

Last in the order, because it reports on everything the providers above
register — the connection, the session store, the health checks — and
listed earlier it would resolve nothing.

The compile gate covers both branches: the three database-session
configurations enable it, and frontrestapi explicitly does not, so the
omitted branch is compiled too. Probed by breaking the registration and
confirming exactly those three fail.

Also pins api v0.7.2, which fixes a HealthChecker deadlock that two
concurrent MCP tool calls hit, and mcp v0.1.4.

_scaffold/VERSION 2.15.0 -> 2.16.0.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

12 of 61 new or added lines in 4 files covered. (19.67%)

1286 of 2189 relevant lines covered (58.75%)

47.37 hits per line