logr

it.logrPublished by logr.itOfficial publisherv1.0.0Updated Nov 2, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingKnowledge & Memory

Overview

AI-generated overview

Remote MCP server for logr, letting an assistant search public logr profiles and read their timelines, events and full Markdown context.

What you can do
  • Search public profiles by name, handle, bio or location and get handles for other tools
  • Read a profile's identity card: who they are, current activity, socials and timeline stats
  • List a profile's timeline events newest first, filtered by tag, year, featured or pinned
  • Open a single event in full, including its image, video and link media
  • Keyword-search a profile's timeline by title, body and tags, with all terms required
  • Retrieve the complete Markdown context for a profile, matching the logr://profiles/{username} resource
When to use it
Useful when an assistant needs structured, first-person background on a person or creator who publishes a logr profile, for example to ground answers about their work, history or current projects. It is a read-oriented lookup layer over public portfolios rather than a general web search.
Requirements
A remote Streamable HTTP endpoint at logr.it; no package, environment variable or header is declared. Profiles queried must be public. The README mentions OAuth 2.1 consent for owner write access, but no authentication is declared in the manifest.
Before you install
Only public profile data is intended to be read, but everything returned is third-party content about real people, so treat it as unverified. The registry description mentions owner-authorized writes, which would change profile data; the manifest declares no authentication, so confirm what access is actually granted before connecting. Keyword search is plain text matching, not semantic.

Installation

In SourceWeft

  1. Open logr in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/it.logr%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "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.

Source: README.md at commit 2601c47

Tools

6

find_profiles

Find profiles

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

Parameterslimitqueryrequired

get_profile

Get profile

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

Parametersusernamerequired

get_timeline

Get timeline

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

Parameterstagyearlimitoffsetpinnedfeaturedusernamerequired

get_event

Get event

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

Parametersidrequiredusernamerequired

search_events

Search events

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

Parameterslimitqueryrequiredusernamerequired

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.

Parametersusernamerequired

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.