temps-mcp-setup

# Temps MCP Setup Temps serves MCP (Model Context Protocol) directly from the `temps` binary itself (ADR-039, `crates/temps-mcp-server`) -- there is no separate package to install or keep up to date. The MCP endpoint calls the same service layer as the REST API, so it cannot drift from it the way the old standalone `@temps-sdk/mcp` npm package did (removed in PR #355 for exactly that reason -- do not reinstall it or point a client at it). Installer wizard lives in `apps/temps-cli/src/commands/mcp/` (`bunx @temps-sdk/cli mcp add|remove|status`). ## 1. Enable the MCP server (operator, one-time per instance) Off by default (`AppSettings.mcp_server.enabled = false`), so a fresh install never exposes it unconfigured. Turn it on as an admin: ```bash bunx @temps-sdk/cli mcp enable ``` If you're not logged in yet, `mcp enable` offers to run the device-flow login inline (see [Auth model, precisely](#2-configure-your-ai-client-per-user-per-client) below) -- no separate `temps login` step required first. `mcp enable` does the same GET-modify-PUT round-trip against `/api/settings` the handler requires (it takes the **full** `AppSettings` object, not a partial patch), merging onto whatever is already fetched so it can never clobber another admin's settings. `mcp disable` reverses it. Verify it took effect, or check status any time without re-running enable: ```bash bunx @temps-sdk/cli mcp status # "This instance: <check> enabled (http://localhost:8080)" or "<bullet> disabled (......