Agents & MCP

MCP endpoints

Details: /docs/mcp-profiles.

Best method by client

One MCP server, different auth UX. Prefer these paths — then call get_context_pack.

5-minute Quick Start

1. Public pack — no API key:

curl -X POST https://dayze.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"notable_pack","arguments":{"slug":"albert-einstein"}}}'

2. Private context pack — create an API key, share token, or connect via OAuth at Settings → Agent access. Prefer get_context_pack:

curl -X POST https://dayze.com/api/v1/mcp \
  -H 'Authorization: Bearer dayze_k_YOUR_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"tool":"get_context_pack","parameters":{"query":"this week"}}'

# Or share token (get_context_pack | get_life_graph only)
curl -X POST https://dayze.com/api/v1/mcp \
  -H 'Authorization: Bearer dayze_share_YOUR_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"tool":"get_context_pack","parameters":{}}'

Coding agents: fetch https://dayze.com/ai · Machine guide: /AGENTS.md. REST still works: {"tool":"notable_pack","parameters":{"slug":"…"}}

Client Install Configs

Copy-paste configs for major MCP clients. OAuth is auto-discovered via /.well-known/oauth-protected-resource. Every client gets the same tools/list — reads plus writes (log_food, update_food, log_event, update_event, log_favorite_song, update_person). Writes are private by default and each one is attributed to the key or app that made it, in the owner's change history (shown on the record, with Undo for 30 days). Destructive tools are annotated so clients confirm first, and removals are previewed or archived so most can be restored for 30 days. Share tokens stay read-only.

{
  "mcpServers": {
    "dayze": {
      "type": "http",
      "url": "https://dayze.com/api/mcp"
    }
  }
}

{
  "mcpServers": {
    "dayze": {
      "url": "https://dayze.com/api/mcp/key",
      "headers": {
        "Authorization": "Bearer dayze_k_YOUR_KEY"
      }
    }
  }
}

from google.adk.tools.mcp_tool.mcp_toolset import (
    MCPToolset, StreamableHTTPConnectionParams
)

toolset = MCPToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://dayze.com/api/mcp",
    )
)

MCP Prompts

Curated prompts available via prompts/list and prompts/get. Claude and Cursor load these automatically.

# List prompts
curl -X POST https://dayze.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"prompts/list"}'

# Get a prompt
curl -X POST https://dayze.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"prompts/get","params":{"name":"notable_pack","arguments":{"slug":"albert-einstein"}}}'

MCP Resources

Static resources readable via resources/read.

# List resources
curl -X POST https://dayze.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"resources/list"}'

# Read a resource
curl -X POST https://dayze.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":2,"method":"resources/read","params":{"uri":"dayze://docs/agents"}}'

Public vs Private Tools

Public (notable_search, notable_profile, notable_pack, notable_pack_premium, compare_lives): no API key. Search and fetch notable people from the Dayze catalog.

Private: require Authorization: Bearer dayze_k_... with scope context. Read the authenticated user's life graph, events, memories, and more. Writes: update_person, log_food, update_food, log_event, update_event, log_favorite_song (share tokens cannot write).

Discovery URLs

• Agent bootstrap (fetch dayze.com/ai)
• Agent playbook (raw)
• MCP endpoint (Streamable HTTP)
• MCP endpoint (REST)
• Health / readiness
• Well-known discovery
• Server card (Smithery)
• OAuth Protected Resource (RFC 9728)
• OAuth AS Metadata (RFC 8414)
• llms.txt
• AGENTS.md

OAuth 2.1 (Claude / ChatGPT / Cursor)

Dayze supports OAuth 2.1 + PKCE for connector directories. Clients discover the authorization server via RFC 9728 protected-resource metadata and register dynamically (RFC 7591).

Pricing

Public tools need no API key and have a free tier: notable_search, notable_profile, notable_pack are always free, and the others have a free daily allowance per IP address. A valid API key or OAuth token lifts that limit. Private tools come with your Dayze account. See Pricing for plans.

initialize, tools/list, prompts/list, resources/list, and ping are always free.

Directory listings

• Glama — Dayze MCP (claimed · author verified)
• Smithery — polaris/dayze
• Official MCP Registry — com.dayze/life-context
• mcp.so — dayze-mcp

Links

• Privacy Policy
• Terms of Service
• GitHub stub (gohluke/dayze-mcp)
• Life Context API (private beta)
• Health endpoint