Liveness check — package version, runtime mode, and indexed resource count.

Readiness check — storage backend, effective retrieval mode, and index counts.

Reports what the server can actually do right now: which backend is open, whether vector and hybrid search are available, which embedding provider is configured, and how many resources, chunks, and embeddings are indexed. Never returns credentials; database URLs are redacted.

Browse and filter indexed frontend resources (components, patterns, libraries). Supports category/kind, framework, style/tags, license, accessibility, animation, maturity, source_id, limit, and offset. Returns paginated items with provenance.

Search frontend knowledge chunks. Uses BM25 on the SQLite backend and hybrid full-text + pgvector retrieval when PostgreSQL and an embedding provider are configured. Pass query plus optional filters (kind, framework, tags, source_id), limit, and detail_level (brief|standard|full). Returns scores, per-branch ranks, the retrieval mode actually used, citations, and provenance.

Fetch a normalized FrontendResource by id (resource id string, e.g. motion:motion-library), related sanitized documentation chunks, and license/attribution. Parameter name is id.

Compare frontend options by id or name. Primary parameter: options (list of ids/names). Deprecated alias: resources. Separates facts from inferences; never claims unverified compatibility.

Recommend a frontend stack from requirements, target_framework, constraints, aesthetics, accessibility, and performance. Returns recommendation, trade-offs, incompatibilities, plan, sources, with facts vs inferences.

Find components/patterns for an intent string (hero, pricing, navbar, dashboard, onboarding, microinteraction, scroll animation, …) with optional framework filter.

Find animation patterns for a query/use-case. Includes cost notes, accessibility, and prefers-reduced-motion support when known from indexed notes; cites sources.

Build an implementation brief from product_description + constraints: stack, components, motion system, suggested design tokens, responsive behavior, and acceptance criteria. Inferences are marked clearly.