Dayze — Life Context
OnlineLife context for agents: get_context_pack + public notable packs. x402 + OAuth.
What it can do: 42 tools
search_toolsread-onlyDiscover Dayze MCP tools outside the core default expert listing. Returns matching opt-in tools with their toolset and how to enable them (URL ?toolsets=, tools/list params, or tools.* connection scopes). Call with no quget_context_packread-onlyLife Context pack for one Dayze account (`account` names it — with more than one Dayze connection, say which account you are answering from): identity, pulse, people, next actions, memories, quizzes, recent consented plaget_eventsread-onlyAuthenticated user's calendar events. Prefer explicit from/to (YYYY-MM-DD). Shortcuts: today|week|month|year (calendar year)|decade. Browsing noise excluded by default. Records carry inspect_url (their Dayze page): citeget_peopleread-onlyList or search the authenticated user's Dayze Contacts (private CRM; table people). query matches literal substrings of name, slug, email, occupation or context tags (no fuzzy fallback). context_tags requires all exact tupdate_personEdit one owned contact. Omit to keep; lists replace. Read before adding. request_id retries safely; change_id supports undo. ($0.10; API key required)log_foodMUTATES the authenticated user Food Diary and calendar. Use when they ate or drank — do not store this as a chat memory. Supports dish_items for multiple named dishes with optional price and rating. Example: “I had Mee Pupdate_foodMUTATES one owned Food Diary row by food_id. Same fields as log_food; omitted stay. dish_items replaces the full dish list. A dish/notes correction never creates another Finance row. expense_id null unlinks. Unknown/othelog_eventMUTATES the calendar (non-food events, tasks, sleep). Replies owed ('what to reply to X') go to create_pending_reply. Woke at X: end_time. Requires title+date. No-date task: use create_todo with no date, never log_eventupdate_eventMUTATES one existing calendar event the authenticated user owns. Required: event_id (UUID). Optional patch (same fields as log_event): title, date / event_date, time / event_time, end_date, end_time, location, descriptiolog_momentSave a past story or memory as a private moment. Plans go to log_event; a touchpoint with a contact to log_interaction. Requires title, and moment_date (YYYY-MM-DD, YYYY-MM or YYYY; alias date) unless event_id is given.update_momentPatch one owned moment by moment_id (from log_moment); fields left out are untouched. It stays private. Requires moment_id. Patchable: title, description, moment_date, moment_date_precision, end_date, moment_type, locaticreate_pending_replyPending Replies (Inbox): save a reply the user owes someone, e.g. 'what to reply to X', 'I owe X a reply'. Use this, not log_event or a task. Optional draft (the reply text), summary (one line in your own words; never thget_pending_repliesread-onlyPending Replies (Inbox): the replies the user owes ('who do I owe a reply?'), newest first, or one by reply_id. status: unsent (default; pending + snoozed), sent, dismissed, all. Filter by person_name or person_id. Eachupdate_pending_replyPending Replies: change one reply by reply_id: its draft (replaces; null clears), summary, channel, category, received_at, person (person_id, or person_name linked only on one match), source, or status pending (reopen /resolve_pending_replyPending Replies: mark a reply done: sent (default; the user replied, logged privately in the contact's history) or dismissed. Dayze sends nothing. By reply_id, or person_name / person_id when that person has exactly onelog_interactionContacts: log that the user was in touch with a contact ('I replied to Vadim', 'called Mum'): kind message, call, meeting, note, check_in or thought_of. Private to the owner. person_id (an owned contact) or person_name (get_memoriesread-onlyAuthenticated user memories from Dayze Agent. Pass query for semantic/keyword retrieval. Prefer search for event-first trip and calendar titles. Requires OAuth or a supported scoped credential. ($0.10; API key required)get_expensesread-onlyCashflow totals at Finance FX. Use period all for all-time requests, never year. Requires OAuth or scoped credentials. ($0.10; API key required)resolve_personread-onlyResolve a nickname or surface name to a Dayze Contacts row via person_aliases → exact name → slug → unique substring. Returns avatar_url, photo_count, has_photos, and photos[{url,is_primary}] preview; use get_person_photget_interactionsread-onlyBounded graph read over life_updates (PHI-54/61): traverse interaction → person/event/expense/place with source/confidence on every hop. When life_update edges are missing, projects hops from CRM interactions, event_peopget_trackersread-onlyAuthenticated user live trackers only; expired countdowns and inactive streaks are omitted. Sobriety/streak trackers remain visible at day 0 after a reset. Merges event-backed trackers with the trackers table when presenreset_trackerPreview first, 30-day undo. Resets a sobriety/streak tracker for the authenticated user (sets current value to 0 and restarts the clock). Prefer tracker_id from get_trackers, or tracker_title fuzzy match; optional reset_searchread-onlySearch the authenticated user life graph. Optional from/to (aliases start/end) are inclusive account-local civil dates on every search route; either bound may be used alone. Dated semantic and keyword records use event dget_goalsread-onlyRead your owned life goals and progress. goal_id selects one; status defaults active, all includes completed goals. Each goal carries a computed progress object: kind, percent, this period, change on the previous period,create_goalCreate a life goal the user explicitly wants to track. Not a calendar event or streak tracker. Numeric goals are totals that build up and need target_value and target_unit; rate goals are a number per calendar month thatupdate_goalPatch one owned goal by goal_id from get_goals. Set current_value to absolute progress, not a delta. On a rate goal current_value is this month's number and replaces the last one. Omitted fields remain unchanged. Never screate_trackerStart a tracker for the user: title, tracker_type streak, sobriety, countdown or counter, start_date (default today), target_date for a countdown, target_days, emoji. Private. To reset one use reset_tracker. ($0.10; APIlog_sleepSleep: log overnight or nap. Cross-midnight OK (e.g. 14:00→03:00 = 13h / 780m). ($0.10; API key required)get_sleepread-onlySleep: list typed sleep/nap records with duration_minutes. ($0.05; API key required)get_sleep_summaryread-onlySleep: day/week/month totals and averages. ($0.05; API key required)update_sleepSleep: patch an existing sleep record by sleep_id. ($0.10; API key required)create_personAdd a Dayze Contacts record, birthday included (YYYY-MM-DD, YYYY-MM, YYYY, or MM-DD if year unknown); checks duplicates first. An existing contact comes back unchanged with its person_id, not_applied (the fields you sentget_birthdaysread-onlyWhose birthday is coming up or was just missed: the user's contacts with a birthday in a window (days_back before and days_ahead after today, 30 each, or from/to), in the account timezone. upcoming (days_until) and recenupload_photoUpload a photo to a Life Graph entity you have (event, expense, place, person, inventory, …). Accepts image_base64, url, or ChatGPT file object `image` ({download_url, file_id}). Normally re-encodes as WebP; original_prelog_expenseCreate an outgoing expense only. For money received (Venmo/Cash App/PayPal/Zelle) use log_transaction with direction=from and type=income. Lending a contact cash: category "IOU lend" + person_id (one call creates the IOUlog_transactionIncome/expense/transfer. from+income = received. IOU repayment/lend need category + person_id (direction from/to). Invoice: iou_type invoice. Open-IOU income needs not_iou_repayment=true. Unknown person_id errors; changelog_incomeRecord money received (Stripe, refunds, payroll, Venmo). log_transaction with type income and direction from already set (pass neither). Use external_id for Stripe/Gmail idempotency. A contact paying back an IOU: categorget_person_photosread-onlyRead a contact avatar and gallery as inline MCP images with per-asset render status. Avatar comes first. Use offset to page through photos (up to six per call); never paste raw image URLs into chat. ($0.10; API key requiget_momentsread-onlyList owned Moments by date, title, type, tag, person or place. Stable moment_id and inspect_url for each. ($0.05; API key required)search_momentsread-onlySearch only owned Moment stories and titles within an optional date range. Returns stable moment_ids. ($0.05; API key required)
…and 2 more.
Connect it
claude mcp add --transport http dayze-life-context https://dayze.com/api/mcpSettings → Connectors → Add custom connector
URL: https://dayze.com/api/mcp{
"mcpServers": {
"dayze-life-context": {
"url": "https://dayze.com/api/mcp"
}
}
}{
"servers": {
"dayze-life-context": {
"type": "http",
"url": "https://dayze.com/api/mcp"
}
}
}Questions
What does Dayze — Life Context do?
Life context for agents: get_context_pack + public notable packs. x402 + OAuth. It exposes 42 tools to AI assistants.
What tools does Dayze — Life Context provide?
42 tools, including search_tools, get_context_pack, get_events, get_people, update_person, log_food, update_food, log_event, update_event, log_moment, update_moment, create_pending_reply….
How do I connect Dayze — Life Context to Claude, ChatGPT or Cursor?
Add the remote MCP endpoint https://dayze.com/api/mcp as a custom connector or MCP server. Copy-paste setup is on this page.
Does Dayze — Life Context require an account or API key?
No sign-in was needed to list its tools. Individual tools may still need an account or API key.
Is Dayze — Life Context online?
As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.
Who publishes Dayze — Life Context?
dayze.com. The official MCP Registry verified that the publisher controls this domain before accepting the listing.
Similar in Cloud & DevOps
-
CloudflareOnlineOfficialPopular
Cloudflare MCP servers
-
Google ComputeOnlineOfficialPopular
Provides capabilities that let LLM agents perform a range of infrastructure management tasks.
-
Google ContainerOnlineOfficialPopular
Provides read access to your GKE and Kubernetes resources.
-
Google ComposerOnlineOfficialPopular
Interact with your Google Cloud Composer resources using natural language commands.
-
Google BigtableadminOnlineOfficialPopular
Interact with your Google Bigtable resources using natural language commands.
-
Google DatastreamOnlineOfficialPopular
Interact with your Google Cloud Datastream resources using natural language commands.