<aside> ✅

Status: Published Last verified: 2026-07-23 — plex_cache_status, server.py tool groups, migration SQL

</aside>

Purpose

Live REST vs Supabase cache vs local API catalog.

Verified

Plex Connect REST ──(live)──▶  plex-mcp tools
       │
       └──(plex-sync / scheduled)──▶ Supabase `plex` schema ──▶ plex_query / part resolution
Local catalog (rest.json + FTS) ──▶ search/describe/list (not ERP row data)

• Live tools: invoke, on-hand-by-part (sums containers), inventory adjustments, whoami, BOM, routing, raw-material trace
• Cache tools: plex_query, plex_cache_status, part number resolution / find / exists
• Local (no network): nomenclature build/decode/suggest
• Cache masters last synced 2026-07-23 ~09:00Z (from plex_cache_status)

Unverified / Needs re-verify

• Exact Windows task name / duration “~53s”
• Full set of endpoints beyond repo SPECS (production-history rows appear in sync_runs)

Links out

• 05 — Supabase read-cache 05 — Supabase read-cache