npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@remem/mcp-server

v1.0.2

Published

An MCP server for logging daily activities, generating reports, and long-term reflection.

Downloads

495

Readme

Remem

Log your day. Generate reports. Reflect anytime.

npm version License: MIT Node.js

日本語


Overview

Remem is a local-first MCP (Model Context Protocol) server that captures your daily activities, generates structured reports, and preserves summaries for long-term reflection.

  • 📝 Log — Record your work, decisions, and memos throughout the day
  • 📊 Generate — Create daily reports from your activity logs
  • 💾 Reflect — Review past entries weeks or months later
  • 🔒 Local storage — Everything stored in SQLite

Quick Start

Add Remem to your Claude Desktop configuration:

{
  "mcpServers": {
    "remem": {
      "command": "npx",
      "args": ["-y", "@remem/mcp-server"]
    }
  }
}

| OS | Path | |----|------| | macOS | ~/Library/Application Support/Claude/claude_desktop_config.json | | Windows | %APPDATA%\Claude\claude_desktop_config.json |


Features

| Feature | Description | |---------|-------------| | Activity Logging | Record work, decisions, memos, and approvals as you go | | Smart Reports | Generate daily reports with customizable templates | | Long-term Memory | Summaries are preserved indefinitely for future reflection | | Auto Cleanup | Detailed logs expire after configurable days (default: 30) | | Multi-language | Automatically adapts to your system language (EN/JA) | | Privacy First | All data stored locally in ~/.remem/remem.db |


Tools

Remem provides the following MCP tools:

log

Record an activity to the database.

Type: work | decision | memo | approval
Content: Description of the activity

prepare_report

Gather logs and prepare data for AI to generate a daily report.

save_summary

Save the generated report summary to long-term storage.

get_history

Retrieve past summaries for reflection (default: last 6 months).

configure

Update server settings like retention_days or default_template.

get_config

View current server configuration.


How It Works

┌─────────────────────────────────────────────────────────────┐
│                        Your Day                             │
├─────────────────────────────────────────────────────────────┤
│  9:00  "Reviewed PR #123"           → log(work, ...)       │
│ 11:00  "Decided to use Kysely"      → log(decision, ...)   │
│ 15:00  "Approved deployment"        → log(approval, ...)   │
│ 18:00  "Generate today's report"    → prepare_report()     │
│         AI writes report            → save_summary()       │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│                    ~/.remem/remem.db                        │
├─────────────────────────────────────────────────────────────┤
│  activities (expires after 30 days)                        │
│  daily_summaries (permanent)                               │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│                   6 Months Later                            │
├─────────────────────────────────────────────────────────────┤
│  "What did I work on last quarter?"                        │
│  → get_history(months: 6)                                  │
│  → AI summarizes your growth and achievements              │
└─────────────────────────────────────────────────────────────┘

Configuration

| Key | Default | Description | |-----|---------|-------------| | retention_days | 30 | Days to keep detailed activity logs | | default_template | (built-in) | Markdown template for daily reports |

Configure via the configure tool or edit ~/.remem/remem.db directly.


Development

# Clone the repository
git clone https://github.com/remem-mcp/remem.git
cd remem

# Install dependencies
npm install

# Build
npm run build

# Run tests
npm test

# Run locally
node build/index.js

Tech Stack

  • Runtime: Node.js 24+
  • Language: TypeScript
  • Database: SQLite (via Kysely + better-sqlite3)
  • Protocol: MCP SDK
  • i18n: i18next
  • Testing: Vitest

Roadmap

  • [ ] Web UI for browsing history
  • [ ] Export to Markdown/PDF
  • [ ] Team sync via cloud storage
  • [ ] More languages (zh, ko, es, ...)
  • [ ] VS Code extension integration

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes using Conventional Commits
  4. Push to the branch (git push origin feature/amazing-feature)
  5. Open a Pull Request

Commit Message Format

This project follows Conventional Commits. Please use the following format:

<type>: <description>

[optional body]

Types: feat, fix, docs, style, refactor, test, chore

Examples:

feat: add weekly summary generation
fix: correct date parsing in prepare_report
docs: update installation instructions

License

MIT © Remem Contributors


⬆ Back to Top