logr

it.logr由 logr.it 發布官方發布者v1.0.0更新於 Nov 2, 2026

Query any public logr profile — timelines, events, full context — plus owner-authorized writes.

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取知識與記憶

概覽

AI 產生的概覽

logr 的遠端 MCP 伺服器，讓助理搜尋公開的 logr 個人頁面，並讀取其時間軸、事件與完整 Markdown 內容。

可以做什麼
  • 依姓名、帳號、簡介或地點搜尋公開頁面，並取得供其他工具使用的帳號
  • 讀取頁面的身分卡：身分、目前動態、社群連結與時間軸統計
  • 依時間新到舊列出頁面的時間軸事件，可依標籤、年份、精選或置頂篩選
  • 查看單一事件的完整內容，包含圖片、影片與連結等媒體
  • 依標題、內文與標籤對頁面時間軸做關鍵字搜尋，所有詞都須符合
  • 取得頁面的完整 Markdown 內容，與 logr://profiles/{username} 資源一致
適用情境
當助理需要了解某位在 logr 上發布個人頁面者的背景，例如回答關於其工作、經歷或目前專案的問題時適用。它是對公開個人頁面的唯讀查詢層，而非通用網頁搜尋。
執行需求
遠端 Streamable HTTP 端點 logr.it；未宣告任何套件、環境變數或標頭。所查詢的頁面必須為公開狀態。README 提到擁有者寫入需 OAuth 2.1 授權，但清單中未宣告任何驗證方式。
安裝前請注意
設計上只讀取公開頁面資料，但回傳內容皆為關於真實人物的第三方內容，應視為未經查證。登錄描述提到擁有者授權的寫入操作，會修改頁面資料；而清單未宣告驗證，連線前應確認實際授予的權限。關鍵字搜尋為純文字比對，並非語意搜尋。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 logr，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable，透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式，或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南，先向你展示發布者、端點和登入方式，經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/it.logr%2Fmcp/install.md，並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前，先告訴我它的發布者、端點和登入方式，等我確認。不要把 API 金鑰寫進命令或我會提交的檔案；問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "logr": {
      "type": "http",
      "url": "https://logr.it/mcp"
    }
  }
}

README

logr

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:

  • a timeline at logr.it/you — year-grouped, hover-to-expand, in your choice of 9 palettes × 8 layouts,
  • machine-readable Markdown context any AI agent can ingest — the real moat, and
  • a grounded AI chat widget where visitors ask questions answered strictly from your log.

See ROADMAP.md for what's built and what's next.

Features

  • Multi-user — sign in with Google, claim a handle at /welcome, edit at /dashboard with a live preview.
  • AI import — paste your story, upload a resume (PDF/DOCX), or point at a URL; AI structures it into timeline events you review and confirm before anything is saved.
  • Grounded chat — the visitor chat is prompted with the same complete Markdown context as the public routes, streams via OpenRouter, and is rate-limited. Facts-only: if it's not in your log, it says so.
  • Theming — 9 palettes (incl. dark ink) × 8 layouts (timeline, journal, magazine, terminal, feed, card, centered, polaroid), persisted per profile, previewable live.
  • Pinned events — pin up to 7 events from the dashboard events tab (pins dialog); they replace the "recent" side rail (and the OG image's rail) and are marked in the Markdown context.
  • Media — image upload (S3, or local FS in dev), video/tweet embeds, unfurled link cards, dynamic OG image per profile.

Chat, S3, and Google auth are each feature-gated on their env vars and degrade gracefully when unset.

Routes

RouteWhat
/Marketing landing
/[username]Public timeline (e.g. /koshik)
/[username]/askDedicated, shareable grounded-chat page
/[username]/llms.txtPrimary Markdown context; full unless the profile is oversized
/[username]/llms-full.txtComplete, unabridged Markdown context
/[username].mdClean Markdown counterpart to the public profile
/[username]/llm.txtLegacy-compatible complete context URL
/mcpGlobal MCP server (Streamable HTTP) — agents query any public profile; OAuth-authorized owner writes
/oauth/authorizeOAuth 2.1 consent screen for MCP write access (+ /api/oauth/token, /api/oauth/register, /.well-known/* discovery)
/api/[username]/chatStreaming grounded chat API
/dashboardOwner editor (auth-gated) — profile · events · appearance · import
/welcomeOnboarding — claim a handle, seed your timeline
/loginGoogle sign-in

Tech stack

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.

Running locally

bash
npm installcp .env.example .env     # fill in the values belownpx prisma migrate dev   # applies migrations to your Postgresnpm run db:seed          # loads a demo profile + ~18 eventsnpm 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).

Project structure

design/                     # design handoff — visual source of truth (not shipped)prisma/  schema.prisma             # Profile, User/Account/Session, Event, Media, ChatMessage  seed.ts                   # demo profile + eventssrc/  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.

Domain

Product domain logr.it; portfolios at logr.it/<handle>. Primary agent context lives at logr.it/<handle>/llms.txt, with complete Markdown at logr.it/<handle>/llms-full.txt and logr.it/<handle>.md.

來源：README.md，提交 2601c47

工具

6

find_profiles

Find profiles

Search public logr profiles by name, handle, bio, or location. Returns handles to use with the other tools.

輸入參數limitquery必填

get_profile

Get profile

A profile's identity card: who they are, what they're doing now, socials, and timeline stats.

輸入參數username必填

get_timeline

Get timeline

A profile's timeline events, newest first, optionally filtered by tag, year, featured, or pinned.

輸入參數tagyearlimitoffsetpinnedfeaturedusername必填

get_event

Get event

One timeline event in full, including its media (image/video/link URLs).

輸入參數id必填username必填

search_events

Search events

Keyword search over a profile's timeline (title, body, tags). All terms must match. Plain text matching — no semantic search.

輸入參數limitquery必填username必填

get_context

Get full context

The complete Markdown context for a profile — identity, about, and full timeline with sources. Same content as the logr://profiles/{username} resource, for clients that prefer tools.

輸入參數username必填

版本歷史

1
  1. v1.0.0最新Sep 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。