Traveler memory & MCP
Subjects, lessons, and thin MCP tools — memory and reflection, not itinerary planning.
Alcove holds subject memory across trip repos for your account. The public trip template only stores opaque traveler ids.
Subjects
A subject is a traveler profile in Alcove: identity you choose to store, preferences you approve, and lessons from postmortems. Trip YAML references subjects by id — it does not embed the profile.
A party of two on one trip does not automatically impose that pair’s constraints on a later solo trip.
Reflection (postmortem)
After a journey (or a meaningful segment), use MCP for a conversational postmortem. Alcove may propose lessons. A human approves or rejects each one. Approved lessons become part of subject memory for later trips.
Do not write those lessons into the public trip template by default.
What MCP is for
| Allowed | Not allowed |
|---|---|
| Connect / account context | Itinerary edits |
| Subject CRUD | Replacing GitHub as the planning client |
| Reflection: propose → approve/reject lessons | Auto-applying lessons to main |
Plan in the trip repo with your GitHub agent plugin. Use MCP when you need memory that should outlive one repository.
Tool names and arguments: MCP tool reference.