commit_life_update — Dayze — Life Context MCP Tool
commit_life_update
(commit life update) is one of 129 tools on the
Dayze — Life Context
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call commit_life_update from your client
- Claude Code Dayze — Life Context commit_life_update run in your project directory
- Claude Desktop Dayze — Life Context commit_life_update ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Dayze — Life Context commit_life_update ~/.cursor/mcp.json
- VS Code Dayze — Life Context commit_life_update .vscode/mcp.json
- Zed Dayze — Life Context commit_life_update ~/.config/zed/settings.json
- Windsurf Dayze — Life Context commit_life_update ~/.codeium/windsurf/mcp_config.json
- Cline Dayze — Life Context commit_life_update ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Dayze — Life Context commit_life_update ~/.gemini/settings.json
- Grok Dayze — Life Context commit_life_update .mcp.json (in your project root)
- ChatGPT Dayze — Life Context commit_life_update Settings → Connectors → Advanced → Developer mode
- Claude.ai Dayze — Life Context commit_life_update Settings → Connectors → Add custom connector
- LangChain Dayze — Life Context commit_life_update pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http life-context https://dayze.com/api/mcpOther tools on this server
- notable_search
- notable_profile
- notable_pack
- notable_pack_premium
- compare_lives
- get_life_context
- get_context_pack
- get_life_graph
- get_person_neighborhood
- get_events
- get_people
- update_person
- update_notable
- log_food
- update_food
- delete_food
- log_event
- update_event
- delete_event
- log_favorite_song
- get_memories
- get_expenses
- resolve_person
- get_person_aliases
- get_person_transactions
- get_money_between_people
- get_person_interactions
- get_interactions
- explain_fact
- list_clarifications
- get_trackers
- reset_tracker
- search
- search_gmail
- list_gmail_accounts
- read_gmail_message
- read_gmail_attachment
- log_sleep
- get_sleep
- get_sleep_summary
- update_sleep
- resolve_place
- get_places
- get_place
- create_place
- update_place
- get_place_visits
- get_location_history
- log_place_visit
- get_location_context
- get_current_states
- propose_life_update
- update_current_location
- get_trips
- get_residences
- get_trip
- get_travel_history
- get_countries_visited
- get_cities_visited
- log_travel
- create_person
- merge_people
- score_people_duplicates
- link_people
- get_person_connections
- unlink_people
- set_primary_person_name
- update_person_identity
- add_person_alias
- remove_person_alias
- update_person_alias
- audit_people
- merge_people_preview
- undo_contact_change
- update_people_link
- get_people_links
- classify_contact
- convert_contact_entity
- find_identity_candidates
- normalize_people_preview
- normalize_people_apply
- start_people_cleanup
- get_people_cleanup_result
- dismiss_clarification
- resolve_clarification
- bulk_dismiss_clarifications
- link_entities
- get_entity_links
- add_inventory_item
- get_inventory
- get_inventory_item
- update_inventory_item
- archive_inventory_item
- search_inventory
- add_inventory_valuation
- get_inventory_valuations
- link_inventory_person
- upload_asset
- get_asset
- update_asset
- archive_asset
- upload_photo
- attach_asset
- get_entity_assets
- log_expense
- log_transaction
- import_venmo_gmail
- import_uber_gmail
- log_income
- update_expense
- record_purchase
- record_sale
- get_transactions
- search_transactions
- search_photos
- get_photo
- get_photos_for_event
- get_person_photos
- get_photos_for_place
- cleanup_preview
- cleanup_apply
- archive_event
- archive_expense
- archive_trip
- restore_event
- restore_expense
- restore_trip
- restore_cleanup
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.