mocop
Browse · Docs · Guide · Analyze

Dayze

MCP server by Dayze · mcp

Public notable_* tools need no API key (free tier). Private life-graph tools need OAuth (Bearer dayze_at_*) or an API key (Bearer dayze_k_*), and only the scopes the owner granted that connection or key (context.read, context.write, context.delete, mail.read, …): tools/list omits the rest, and calling one returns 403 INSUFFICIENT_SCOPE naming the scope. Prefer get_context_pack for a signed-in user life-graph bootstrap; use notable_pack only for the public notable-people catalog. Sleep: log_sleep / get_sleep / get_sleep_summary / update_sleep (pack sleep section is read-only). Person photos: get_person_photos returns inline MCP image attachments. Inventory photos: search_inventory → upload_asset(image_base64, entity_type=inventory, entity_id, role=photo) or upload_asset then attach_asset. Replies owed ("what to reply to X", "I owe X a reply"): create_pending_reply (Inbox → Pending Replies, optional draft), not log_event; get_pending_replies / update_pending_reply / resolve_pending_repl…

Endpoint: https://dayze.com/api/mcp

Verification: observed. Source: crawl.

Capabilities (50)

  • 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
  • get_pending_replies
  • update_pending_reply
  • resolve_pending_reply
  • log_interaction
  • get_memories
  • get_expenses
  • resolve_person
  • get_interactions
  • get_trackers
  • reset_tracker
  • search
  • get_goals
  • create_goal
About · Contact · Privacy