Skip to main content
Beyond tools, the Rewind MCP server exposes two things you can reference directly: entity resources you @-mention to load a full record, and prompt templates that orchestrate a whole multi-step query for you. Tools are how the model fetches data on its own; resources and prompts are how you hand it a starting point.

Entity resources

Every resource is addressed by a rewind:// URI and returns the full detail record for one entity, fetched live from the API. Each maps to a specific endpoint, so the data matches what the corresponding API reference route returns.
EntityURISource endpoint
Movierewind://movie/{id}/v1/watching/movies/{id}
Showrewind://show/{id}/v1/watching/shows/{id}
Albumrewind://album/{id}/v1/listening/albums/{id}
Artistrewind://artist/{id}/v1/listening/artists/{id}
Vinylrewind://vinyl/{id}/v1/collecting/vinyl/{id}
Physical mediarewind://physical-media/{id}/v1/collecting/media/{id}
Articlerewind://article/{id}/v1/reading/articles/{id}
Highlightrewind://highlight/{id}/v1/reading/highlights/{id}
Activityrewind://activity/{id}/v1/running/activities/{id}
Sync statusrewind://sync/status/v1/health/sync
Year in reviewrewind://{domain}/year/{year}/v1/{domain}/year/{year} (listening, running, watching)
The {id} in each URI is the internal Rewind id, not a Last.fm, TMDB, or Discogs id. You usually get one from a tool result or a search hit rather than typing it by hand.

Reference a resource with @-mention

In a client that supports resource mentions (such as Claude Code), type @rewind: followed by the URI to pull the full record into the conversation:
@rewind://artist/42
That loads the complete artist detail (play count, genre, top albums, top tracks, image metadata, and Apple Music URL) so the model can reason over it directly, without spending a tool call to fetch it.

From a search hit to a full record

The search tool returns resource_link blocks pointing at these URIs. That lets a client drill from a match straight into the full record: search surfaces the candidate, then the resource link resolves to the entity’s rewind:// URI for the complete detail.
The article resource is the canonical way to read past an excerpt. rewind://article/{id} returns the full plain-text body, including for paywalled sources, so the model does not need to fall back to web search or fetch the original URL.

Prompt templates

Prompt templates are pre-written, multi-step instructions the model can run on your behalf. Each one knows which tools to call, in what order, and how to shape the result. Pick one from your client’s prompt menu instead of describing the whole workflow yourself.
PromptArgumentsWhat it does
weekly-summarynoneSummarizes activity across all domains for the past week, organized by domain.
year-in-reviewyearGenerates a comprehensive year-in-review across all domains for the given year.
compare-periodsdomain, period1, period2Compares activity between two time periods for a single domain.
letterboxd-review-drafttitle (optional)Drafts a Letterboxd-style review for a recently watched, rated-but-unreviewed film.
training-reportdays (optional, default 7)Produces a coach-style running report for the last 7 to 14 days.
film-dietperiod (optional, default lifetime)Paints a portrait of your film-watching taste: genre mix, decades, directors, rewatch rate.
find-articledescriptionRecovers a half-remembered article via hybrid plus semantic search, then surfaces related pieces.

How a template runs

A template seeds the conversation with a detailed instruction, then the model executes it using ordinary tools. The training-report prompt, for example, gathers recent runs, lifetime running stats, streak state, and per-mile splits on the longest run, then structures a report with a volume headline, a pace trend, and one concrete suggestion for the week ahead. Templates with optional arguments fall back to sensible defaults: training-report covers 7 days when you do not pass days, film-diet reports on your lifetime when you do not pass period, and letterboxd-review-draft picks your most recent unreviewed watch when you do not pass a title.

find-article and the article resource

find-article is where prompts and resources work together. The template runs a reading search, fetches the rewind://article/{id} resource for the top candidates to read each excerpt, and only claims a match after the excerpt actually supports your description. It is built to refuse to invent connecting facts: if nothing clearly matches, it presents the top few candidates and asks which one you meant.