Dayze MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notable_search | Search the public Dayze notable-people catalog by name, occupation, or slug. Use when you need to find a person before fetching a pack. Example slug: albert-einstein. ($0.01) |
| notable_profileA | Full notable-person profile JSON by slug. Use for bio, timeline, and metadata without similar people or life-in-days context. Example slug: taylor-swift. ($0.02) |
| notable_pack | Knowledge pack: profile + life-in-days + similar people + birthday peers (+ quality / upgrade hint). Timeline events include day_number. Best starting point for agent context. Example slug: albert-einstein. ($0.05) |
| notable_pack_premiumA | S-tier guaranteed pack (score≥85, timeline≥8, image, embedding). Errors if below bar. Use when you need high-quality, complete notable context. Example slug: elon-musk. ($0.10) |
| get_life_contextA | Get the authenticated user's current life context — identity, today's events, mood, inner circle, and social edges. Prefer get_context_pack for a full session bootstrap. Requires API key. ($0.15; API key required) |
| get_context_pack | Life Context Protocol (LCP) reference pack for a Dayze user: identity + who matters (edges) + week calendar + semantic/recent memories. Includes protocol.version. Optional query focuses memories. Requires API key or share token. Spec: https://dayze.com/docs/life-context ($0.20; API key required) |
| get_life_graph | Life-graph export: people nodes + person_connections edges. Optional event–people links. Requires API key. ($0.25; API key required) |
| get_person_neighborhoodA | Subgraph around one person_id — profile plus all declared connections. Requires API key. ($0.15; API key required) |
| get_events | User calendar events (range: today|week|month|year|decade). Requires API key. ($0.10; API key required) |
| get_peopleA | List user CRM people (flat list). Each row includes contact_origin (personal|online|imported). Requires API key. ($0.10; API key required) |
| get_memories | User memories from Dayze Agent. Pass query for semantic retrieval; omit for recent chronological. Requires API key. ($0.10; API key required) |
| get_expensesB | List user expenses / cashflow summary. Requires API key. ($0.10; API key required) |
| get_trackersA | List user trackers / habits / streaks. Requires API key. ($0.10; API key required) |
| searchA | Semantic search across the authenticated user life graph (events, people, memories). Requires API key. ($0.15; API key required) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gohluke/dayze-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server