Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者提供的说明(英文原文)
Query any public logr profile — timelines, events, full context — plus owner-authorized writes.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://logr.it/mcp在终端中运行这条命令
claude mcp add --transport http logr https://logr.it/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"logr": {
"url": "https://logr.it/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"logr": {
"type": "http",
"url": "https://logr.it/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://logr.it/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 logr.it 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于3个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Spec Driven Development, Remote Desktop Commander, AvaHR
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ 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.
Read hiring data and create inactive assessment and questionnaire drafts for human review.
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
A personal portfolio + AI context layer. Most people have a LinkedIn. Nobody has a structured, machine-readable, queryable version of their story that works with any AI tool. logr fills that gap — an editorial life-log that is beautiful for humans to read and structured for AI to query.
You log your story once. It becomes three things:
logr.it/you — year-grouped, hover-to-expand, in your choice of 9 palettes × 8 layouts,See [ROADMAP.md](ROADMAP.md) for what's built and what's next.
/welcome, edit at /dashboard with a live preview.ink) × 8 layouts (timeline, journal, magazine, terminal, feed, card, centered, polaroid), persisted per profile, previewable live.Chat, S3, and Google auth are each feature-gated on their env vars and degrade gracefully when unset.
| Route | What |
|---|---|
/ | Marketing landing |
/[username] | Public timeline (e.g. /koshik) |
/[username]/ask | Dedicated, shareable grounded-chat page |
/[username]/llms.txt | Primary Markdown context; full unless the profile is oversized |
/[username]/llms-full.txt | Complete, unabridged Markdown context |
/[username].md | Clean Markdown counterpart to the public profile |
/[username]/llm.txt | Legacy-compatible complete context URL |
/mcp | Global MCP server (Streamable HTTP) — agents query any public profile; OAuth-authorized owner writes |
/oauth/authorize | OAuth 2.1 consent screen for MCP write access (+ /api/oauth/token, /api/oauth/register, /.well-known/* discovery) |
/api/[username]/chat | Streaming grounded chat API |
/dashboard | Owner editor (auth-gated) — profile · events · appearance · import |
/welcome | Onboarding — claim a handle, seed your timeline |
/login | Google sign-in |
Next.js 16 (App Router) · React 19 · TypeScript · Postgres (Supabase) + Prisma 6 · Auth.js (NextAuth v5, Google OAuth) · Vercel AI SDK via OpenRouter · AWS S3 (local FS in dev) · Tailwind v4 + scoped CSS driven by theme tokens · Source Serif 4 + JetBrains Mono · Vercel.
npm install
cp .env.example .env # fill in the values below npx prisma migrate dev # applies migrations to your Postgres npm run db:seed # loads a demo profile + ~18 events npm run dev # http://localhost:3000
.env (see .env.example for details):
DATABASE_URL / DIRECT_URL — Supabase Postgres; transaction pooler (:6543, ?pgbouncer=true) for runtime, session (:5432) for prisma migrate.AUTH_SECRET + AUTH_GOOGLE_ID / AUTH_GOOGLE_SECRET — Google sign-in for /dashboard and onboarding.OPENROUTER_API_KEY — optional; enables the visitor chat + AI import (OPENROUTER_MODEL to override the default model).ANTHROPIC_API_KEY — optional alternative to OpenRouter; calls the Anthropic API directly and wins when both are set (ANTHROPIC_MODEL, default claude-haiku-4-5).AWS_* — optional; S3 image storage (falls back to ./public/uploads).design/ # design handoff — visual source of truth (not shipped)
prisma/ schema.prisma # Profile, User/Account/Session, Event, Media, ChatMessage seed.ts # demo profile + events src/ auth.ts # NextAuth (Google + Prisma adapter) app/ page.tsx # marketing landing [username]/page.tsx # public timeline (SSR) [username]/llms.txt/route.ts # primary machine-readable context [username]/opengraph-image.tsx dashboard/page.tsx # owner editor (auth-gated) welcome/page.tsx # onboarding / handle claim api/[username]/chat/route.ts# streaming grounded chat api/upload/route.ts # image upload components/ Portfolio.tsx, ChatWidget.tsx, ShareModal.tsx, ... admin/ # dashboard: forms, theme editor, events, import dialogs onboarding/, marketing/, ui/ lib/ actions.ts # all server actions chat.ts, narrate.ts, import.ts, llmtxt.ts, profile.ts, theme.ts, storage.ts, ...
JSON-shaped fields (socials, theme, event link) are stored as serialized strings so the schema stays portable. Outbound fetches of user-supplied URLs go through the SSRF-guarded client in lib/import.ts.
Product domain logr.it; portfolios at logr.it/ . Primary agent context lives at logr.it/ /llms.txt, with complete Markdown at logr.it/ /llms-full.txt and logr.it/ .md.