food/deploy/food.tomflux.xyz.nginx, branch mcp-api

nginx: match the MCP location with or without a trailing slash

2026-06-23T20:50:31+00:00

claude.ai strips the trailing slash from the connector URL, so a location of /mcp// missed and fell to the 301 catch-all. Use a regex (^/mcp//?(.*)$) that matches both and normalises onto the FastMCP root. Co-Authored-By: Claude Opus 4.8

nginx: 404 the .well-known/ OAuth probes for the MCP connector

2026-06-23T20:41:41+00:00

claude.ai's custom-connector flow probes /.well-known/oauth-* during setup. The catch-all 301 -> /app/ made those return the Kitchen login page (200), so claude.ai mistook it for an OAuth sign-in service, tried Dynamic Client Registration, and failed. Returning 404 makes it treat the server as authless and connect. Co-Authored-By: Claude Opus 4.8

Phase 3b: FastMCP "ai service" for claude.ai cooking mode

2026-06-23T20:16:30+00:00

A standalone MCP server (no Django import) exposing 7 tools over Streamable HTTP, backed by the Django REST API via the caine token. - mcp_server/: client.py (httpx wrapper over /api/), server.py (the tools + FastMCP app + main), __main__.py, tests.py. - Tools: get_pantry, set_item_state, add_to_pantry, what_can_i_cook, get_recipes, log_cook (suggests, never mutates), create_meta_recipe (brainstorm -> commit). Each description says when to call it. - deploy/food-mcp.service: systemd unit (own process, runs .venv python -m mcp_server, loads /var/lib/food/.env). - deploy/food.tomflux.xyz.nginx: current config + an authless /mcp// location proxying to 127.0.0.1:8765 (the URL secret is the credential; SSE-friendly buffering/timeout). - pyproject: [dependency-groups] mcp = [fastmcp, httpx]; deploy with `uv sync --group mcp`. Verified: 7 tools register on fastmcp 3.x, run() accepts transport/ host/port/path, 6 FoodClient unit tests pass (httpx MockTransport). Co-Authored-By: Claude Opus 4.8