dy-mcp-demo (dy-mcp)
A public demo of a personal-context MCP server that exposes six typed contexts (project, idea, preference, writing_style, skill, general) and twelve tools for managing personal data, with an hourly data reset.
README
dy-mcp-demo
A public, unauthenticated demo of dy-mcp — an MCP personal-context server. Lets you poke at every tool the server exposes without needing to install or configure anything.
Live at: https://demo-mcp.dyuhaus.com
- Open the URL in a browser to see the Editorial-style web companion.
- Or point any MCP-aware client (Claude Desktop, Claude Code, etc.) at
https://demo-mcp.dyuhaus.com/mcp— no auth header required.
The data is invented (a fictional writer-developer named "Alex Quinn") and the whole database resets every hour, so feel free to create, edit, or delete anything. You won't break it.
For the real, password-protected server this is cloned from, see dyuhaus/dy-mcp.
What's the same as dy-mcp?
Everything to do with the MCP protocol and the data model:
- Six typed contexts:
project,idea,preference,writing_style,skill,general. - All 12 tools:
get_personal_context,list_contexts,get_context,add_context,update_context,delete_context,search_contexts,import_project,import_project_section,list_project_files,get_project_file,delete_project_file. - All 7 resources under
context://. - Same SQLite schema, same storage code, same importer, same HTTP routes.
What's different?
- No auth.
/auth/*,/oauth/*,/.well-known/*, session cookies, password bootstrap — all removed./mcpis open. The web UI boots straight into the dashboard. - Hourly reset. A scheduled task wipes the DB and reseeds it with the
fictional persona (see
scripts/seed.ts). - Default port is 7879 so it can run alongside the main dy-mcp on the same machine.
- Web sidebar shows "PUBLIC DEMO" and a "resets hourly" note.
Try it from an MCP client
Claude Code
claude mcp add --transport http dy-mcp-demo https://demo-mcp.dyuhaus.com/mcp
Claude Desktop / any config-file client
{
"mcpServers": {
"dy-mcp-demo": {
"transport": "http",
"url": "https://demo-mcp.dyuhaus.com/mcp"
}
}
}
curl
# list all tools
curl -sS -X POST https://demo-mcp.dyuhaus.com/mcp \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
# call a tool
curl -sS -X POST https://demo-mcp.dyuhaus.com/mcp \
-H "content-type: application/json" \
-H "accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"get_personal_context","arguments":{}}}'
Run the demo locally
npm install
npm run build
npm run seed # wipe + reseed the demo DB
npm run web:build
npm run start:api # http://localhost:7879
The web UI is served at the same port as the API.
Dev loop:
npm run dev:api # backend with tsx watch
npm run web:dev # vite dev server on :5173
HTTP endpoints
| Method | Path | Body / query |
|---|---|---|
| GET | /health |
returns { ok, demo: true, resets_every_minutes, counts } |
| GET | /contexts |
?type=&tag=&parent_id=&limit=&offset= |
| POST | /contexts |
{ type, title, content?, tags?, metadata?, parent_id? } |
| GET | /contexts/:id |
— |
| PATCH | /contexts/:id |
any subset of the add body |
| DELETE | /contexts/:id |
— |
| GET | /search |
?q=&type=&limit= |
| GET | /activity |
?limit= — in-memory ring buffer, 500 entries, newest first |
| GET | /export |
full payload snapshot |
| GET | /tools |
catalog of tools + resources (drives the /Tools page) |
| GET | /contexts/:id/files |
?section= |
| GET | /files/:id |
— |
| DELETE | /files/:id |
— |
| POST | /import/project |
{ path, name?, description?, tags?, include_content?, … } |
| POST | /import/section |
{ path, section_name, parent_project_id?, … } |
| POST | /mcp |
MCP over Streamable HTTP (stateless, single round-trip) |
Hosting
The included scripts/install-demo-task.ps1 registers two Windows scheduled
tasks:
dy-mcp-demo-api— runs the built server on :7879 at boot.dy-mcp-demo-reset— runsscripts/seed.tsevery hour viatsx.
Point a Cloudflare tunnel at http://localhost:7879 under the hostname of
your choice. See CLAUDE.md for the exact commands.
Environment variables
| Variable | Default |
|---|---|
DY_MCP_DB_PATH |
~/.dy-mcp-demo/context.db |
DY_MCP_API_PORT |
7879 |
DY_MCP_API_ORIGIN |
* |
DY_MCP_DEMO_RESET_MIN |
60 (informational) |
DY_MCP_WEB_DIST |
<repo>/web/dist |
VITE_API_BASE_URL |
(same origin) |
License
MIT.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。