Dayze MCP

Life Context for AI agents — reference Life Context Protocol (get_context_pack) plus public notable-people packs.

Listed on LightNow: https://lightnow.ai/servers/com.dayze/life-context

Cursor / Grok Bot

This repo is a Cursor Plugin (v1.33.0): .cursor-plugin/plugin.json, skills/dayze-life-context/, URL-only root mcp.json, plus Codex/ChatGPT metadata in .codex-plugin/ and .mcp.json.

Dayze Contacts is the private CRM. Advertised MCP names stay get_people, create_person, update_person, resolve_person (stable). Call aliases get_contacts / create_contact / update_contact / resolve_contact work on the hosted server. Public People stays notable_*.

Publish to Cursor Marketplace: submit https://github.com/gohluke/dayze-mcp at https://cursor.com/marketplace/publish (see PUBLISH.md). ChatGPT plugin is already live.

Until marketplace review lands, test locally:

mkdir -p ~/.cursor/plugins/local
ln -s /path/to/dayze-mcp ~/.cursor/plugins/local/dayze

Reload Cursor (Developer: Reload Window), open Customize, and click Connect. Sign in to Dayze in the browser. Do not paste an API key — Cursor discovers OAuth from RFC 9728. Same Connect flow for Cursor desktop, Cursor web, and Grok Bot.

Docs: https://dayze.com/docs/agents

Website	https://dayze.com
Agents docs	https://dayze.com/docs/agents
Streamable HTTP	https://dayze.com/api/mcp
REST MCP	https://dayze.com/api/mcp
Discovery	https://dayze.com/.well-known/mcp.json
Server card	https://dayze.com/.well-known/mcp/server-card.json
OpenAPI	https://dayze.com/openapi.json
OAuth PRM	https://dayze.com/.well-known/oauth-protected-resource
OAuth AS	https://dayze.com/.well-known/oauth-authorization-server
x402scan	https://www.x402scan.com/recipient/0x4DeE3CDA6cb33b1f7A29dE1385B192F802AE3EDa/resources

Pitch

Dayze is a pay-per-call people + life-in-days API for AI agents — notable packs with day-of-life numbers, similar people, and birthday peers. Public notable_* tools need no API key; USDC on Base via x402 after the free tier.

Quick try

# Streamable HTTP (JSON-RPC)
curl -X POST https://dayze.com/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1.0"}}}'

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

# REST (compat)
curl https://dayze.com/api/mcp

curl -X POST https://dayze.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"tool":"notable_pack","parameters":{"slug":"albert-einstein"}}'

Timeline events include day_number (e.g. Einstein’s Nobel = Day 15,580).

Auth

• Public notable_* tools: no login (x402 after free tier)
• Private life-graph tools: Bearer dayze_k_… or OAuth dayze_at_…
• OAuth 2.1 + PKCE + DCR for Claude / ChatGPT / Gemini agents — see https://dayze.com/docs/agents

Transport

• Streamable HTTP JSON-RPC at /api/mcp (initialize, tools/list, tools/call)
• REST MCP-compatible at /api/v1/mcp (GET capabilities, POST {tool, parameters})
• GET /api/mcp returns discovery JSON (200); SSE sessions are not available on Netlify serverless

Tags

mcp · x402 · ai-agents · notable-people · life-in-days · knowledge-api · base · usdc

Glama install / Make Release

Dayze MCP is hosted at https://dayze.com/api/mcp. This repo ships a local stdio adapter (server.mjs) so Glama can build/scan without putting a URL in CMD (Glama rejects remote endpoints in CMD arguments).

1. Open https://glama.ai/mcp/servers/gohluke/dayze-mcp/admin/dockerfile
2. Build steps: ["npm install"]
3. CMD arguments: ["node", "./server.mjs"]
4. Click Build → wait for green → Build & Release (1.6.2)

If Glama keeps checking out an old commit, use build steps: ["git fetch origin && git checkout origin/main", "npm install"]

Prefer connecting clients directly to https://dayze.com/api/mcp (Streamable HTTP + OAuth).

License

Documentation and listing metadata in this repo: MIT. The Dayze product and API remain proprietary; this repo exists so directories can index a public GitHub URL.