Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Life context for agents: get_context_pack + public notable packs. x402 + OAuth.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://dayze.com/api/mcp在终端中运行这条命令
claude mcp add --transport http life-context https://dayze.com/api/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"life-context": {
"url": "https://dayze.com/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"life-context": {
"type": "http",
"url": "https://dayze.com/api/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://dayze.com/api/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 dayze.com 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.28.0)于2个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, Detailing Manager
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Connect your auto detailing studio's tasks, cars, clients and revenue to Claude or ChatGPT.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Dayze gives connected AI tools Life Context: your people, plans and memories in a private, correctable record.
After you sign in, get_context_pack hands your AI the signed-in user's context (who matters, this week's plans, recent memories) over the Model Context Protocol (MCP). The public notable-people catalog (notable_*) is a separate feature and never touches your private record.
ChatGPT + iPhone first. Capture people, plans and moments in Dayze on your iPhone, then connect ChatGPT and ask about your own life. Cursor, Codex, Claude and other MCP clients use the same hosted endpoint.
Listed on LightNow: https://lightnow.ai/servers/com.dayze/life-context
Dayze starts with the people in your life. Ask *"When did I last see Maya, and what's next with her?"* and your AI can:
resolve_person / get_people against your private Dayze Contacts.get_person_interactions returns the events, places and notes connected to that person.explain_fact returns the source behind a claim, so the answer is traceable rather than guessed.update_person, merge_people and the other write tools fix the record, so the next answer is right.These four steps use the full endpoint (https://dayze.com/api/mcp). ChatGPT's compact profile is read-only: get_context_pack, get_people_context, get_events, search_dayze and related context reads, with corrections made in Dayze itself.
https://dayze.com/api/mcp?tools_profile=compactMore detail: README-CHATGPT.md · https://dayze.com/docs/agents
This repo is also a Claude Code plugin and its own marketplace (.claude-plugin/). The plugin adds the hosted Dayze MCP server and the dayze-life-context skill.
claude plugin marketplace add gohluke/dayze-mcp
claude plugin install dayze@dayze claude mcp login plugin:dayze:dayze
The last command opens Dayze sign-in in your browser (OAuth). In a session you can use /mcp → plugin:dayze:dayze → Authenticate instead. No API key.
Then ask: "Use Dayze to pull my context pack for this week."
To point the plugin at a different Dayze connector URL, set DAYZE_MCP_URL in the env block of ~/.claude/settings.json and sign in again. The default is https://dayze.com/api/mcp.
Local development: claude --plugin-dir /path/to/dayze-mcp.
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_*.
Cursor Marketplace: https://github.com/gohluke/dayze-mcp submitted 2026-09-19, in review (see PUBLISH.md). The ChatGPT custom connector works today; the ChatGPT Apps Directory listing is in review.
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 |
# 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"}'
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"}}'
The last call uses the public notable-people catalog. Timeline events include day_number (e.g. Einstein’s Nobel = Day 15,580).
get_context_pack, Contacts, events, memories): OAuth dayze_at_… (recommended) or Bearer dayze_k_…, scope contextnotable_* tools: no login (see public tool pricing)/api/mcp (initialize, tools/list, tools/call)/api/mcp?tools_profile=compact (read-only subset)/api/v1/mcp (GET capabilities, POST {tool, parameters})/api/mcp returns discovery JSON (200); SSE sessions are not available on Netlify serverlesslife-context · mcp · model-context-protocol · personal-crm · relationship-intelligence · chatgpt · ai-agents · notable-people
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).
["npm install"]["node", "./server.mjs"]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).
This applies only to the public notable-people catalog, not to your private Life Context.
notable_* calls have a free tier. After it, the server may answer 402 Payment Required using x402 (USDC on Base).notable_search $0.01, notable_pack $0.05).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.