Search everything...

Stats

Actions

Available In

mimirs

Name: mimirs
Author: thewinci

By TheWinci

Persist and retrieve project context across AI coding sessions using semantic search, AST-aware chunking, dependency graphs, and conversation history — enabling agents to rebuild mental models, trace bugs, assess change impact, and resume work without re-deriving context.

npx claudepluginhub thewinci/mimirs --plugin mimirs

Popularity

Stars

Top 25%

Med: 0·Avg: 284

Installs

Med: 0·Avg: 1

Forks

Top 25%

Med: 0·Avg: 36

Health & Quality

Maintenance

Top 25%

Excellent10.0/10

Med: 7/10·Avg: 7.4/10

Community

42%

Med: 42%·Avg: 42.1%

What's Inside

Skills11

catch-up

/catch-up

Get oriented on a project's current state when starting or resuming work — what's changed, what's in flight, and the recent decisions. Use at the start of a session, when returning to a repo after a break, or when asked "where were we" or "what's the status".

debug

/debug

Trace a bug, error, or regression to its root cause. Use when investigating a failure, a stack trace, unexpected behavior, or "why does X happen".

doc-gaps

/doc-gaps

Find what's underdocumented or hard to retrieve in a project — the topics people search for but don't find. Use when improving docs or the wiki, or when asked what's missing or poorly covered.

explore

/explore

Build an accurate mental model of an unfamiliar codebase, feature, or area before changing it — where it lives, how it connects, what it does, and why. Use when asked how something works, where something is, when onboarding to a repo, or before editing code you don't know. For a cross-cutting question that needs answering from many sources, use research instead.

handoff

/handoff

Wrap up a work session so the next session (or another agent) can pick up cleanly — what was done, what's in flight, what to watch out for. Use when ending a session, switching tasks, or asked to hand off, wrap up, or save state for later.

Hooks1

Event Hooks

File writes

3 hooks across 3 events

MCP Servers1

mimirs

Stats

Version1.7.0

LanguageTypeScript

Stars24

Forks2

MaintenanceExcellent

LicenseApache-2.0

Last CommitJun 13, 2026

AddedMar 28, 2026

Actions

View on GitHub View README Plugin Marketplace JSON Homepage

Own this plugin?

Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).

Available In

mimirs24

Safety Signals

Caution

Modifies files

Hook triggers on file write and edit operations

README

MIMIRS

Named after Mímir, the Norse god of wisdom and knowledge.

Persistent project memory for AI coding agents. One command to set up, nothing to maintain.

Your agent starts every session blind — guessing filenames, grepping for keywords, burning context on irrelevant files, and forgetting everything you discussed yesterday.

On one real project, a typical prompt was burning 380K tokens and ~12 seconds end-to-end.

After indexing with mimirs: 91K tokens, ~3 seconds — a 76% drop on that codebase. Your numbers will vary with repo size, query, and model.

No API keys. No cloud. No Docker.
Just bun and SQLite.

Semantic Search · Auto-generated Wiki
Cross-session Memory · Dependency Graphs · Annotations

Works with: Claude Code · Cursor · Windsurf · JetBrains (Junie) · GitHub Copilot · any MCP client

mimirs: index a repo, then search, read, and find affected tests — from the terminal

Quick start

1. Prerequisites

Bun (curl -fsSL https://bun.sh/install | bash) and, on macOS, a modern SQLite — Apple's bundled one doesn't support extensions:

brew install sqlite

Linux and Windows ship with a compatible SQLite already.

2. Set up your editor (automatic)

bunx mimirs init --ide claude   # or: cursor, windsurf, copilot, jetbrains, all

This creates the MCP server config, editor rules, .mimirs/config.json, and .gitignore entry. Run with --ide all to set up every supported editor at once.

init covers Claude Code, Cursor, Windsurf, Copilot, and JetBrains (Junie). For everything else — Codex, Zed, custom clients — copy one of the snippets below.

3. Set up your editor (manual reference)

The mimirs MCP server runs over stdio. Every client needs the same three things: a command (bunx), args (["mimirs@latest", "serve"]), and a RAG_PROJECT_DIR env var pointing at your project root.

Claude Code — .mcp.json in project root

{
  "mcpServers": {
    "mimirs": {
      "command": "bunx",
      "args": ["mimirs@latest", "serve"],
      "env": {
        "RAG_PROJECT_DIR": "/absolute/path/to/your/project"
      }
    }
  }
}

Cursor — .cursor/mcp.json in project root

{
  "mcpServers": {
    "mimirs": {
      "command": "bunx",
      "args": ["mimirs@latest", "serve"],
      "env": {
        "RAG_PROJECT_DIR": "/absolute/path/to/your/project"
      }
    }
  }
}

Windsurf — ~/.codeium/windsurf/mcp_config.json (global)

Windsurf reads MCP servers from your home directory, not the project. JetBrains plugin variant uses ~/.codeium/mcp_config.json.

{
  "mcpServers": {
    "mimirs": {
      "command": "bunx",
      "args": ["mimirs@latest", "serve"],
      "env": {
        "RAG_PROJECT_DIR": "/absolute/path/to/your/project"
      }
    }
  }
}

JetBrains (Junie) — .junie/mcp.json in project root

{
  "mcpServers": {
    "mimirs": {
      "command": "bunx",
      "args": ["mimirs@latest", "serve"],
      "env": {
        "RAG_PROJECT_DIR": "/absolute/path/to/your/project"
      }
    }
  }
}

GitHub Copilot — .vscode/mcp.json in project root

VS Code's Copilot uses a servers map (not mcpServers) and a type field.

{
  "servers": {
    "mimirs": {
      "type": "stdio",
      "command": "bunx",
      "args": ["mimirs@latest", "serve"],
      "env": {
        "RAG_PROJECT_DIR": "/absolute/path/to/your/project"
      }
    }
  }
}

Codex — ~/.codex/config.toml (global)

Codex uses TOML, not JSON, and reads from ~/.codex/config.toml. One block per project — pick a unique table name if you wire up multiple repos (mimirs-frontend, mimirs-api, etc).

[mcp_servers.mimirs]
command = "bunx"
args = ["mimirs@latest", "serve"]
env = { RAG_PROJECT_DIR = "/absolute/path/to/your/project" }

View full README on GitHub

mimirs

Popularity

Health & Quality

What's Inside

Confidence

README

MIMIRS

No API keys. No cloud. No Docker.
Just bun and SQLite.

Semantic Search · Auto-generated Wiki
Cross-session Memory · Dependency Graphs · Annotations

Quick start

1. Prerequisites

2. Set up your editor (automatic)

3. Set up your editor (manual reference)

Similar Plugins

claude-turbo-search

alcove

memctl

openltm

Basemind

harness-mem

MIMIRS

No API keys. No cloud. No Docker.
Just bun and SQLite.

Semantic Search · Auto-generated Wiki
Cross-session Memory · Dependency Graphs · Annotations

Quick start

1. Prerequisites

2. Set up your editor (automatic)

3. Set up your editor (manual reference)

Similar Plugins

claude-turbo-search

alcove

memctl

openltm

Basemind

harness-mem

Popularity

Health & Quality

mimirs

Popularity

Health & Quality

What's Inside

Confidence

README

MIMIRS

No API keys. No cloud. No Docker.Just bun and SQLite.

Semantic Search · Auto-generated Wiki Cross-session Memory · Dependency Graphs · Annotations

Quick start

1. Prerequisites

2. Set up your editor (automatic)

3. Set up your editor (manual reference)

Similar Plugins

claude-turbo-search

alcove

memctl

openltm

Basemind

harness-mem

MIMIRS

No API keys. No cloud. No Docker.Just bun and SQLite.

Semantic Search · Auto-generated Wiki Cross-session Memory · Dependency Graphs · Annotations

Quick start

1. Prerequisites

2. Set up your editor (automatic)

3. Set up your editor (manual reference)

Similar Plugins

claude-turbo-search

alcove

memctl

openltm

Basemind

harness-mem

Popularity

Health & Quality

No API keys. No cloud. No Docker.
Just bun and SQLite.

Semantic Search · Auto-generated Wiki
Cross-session Memory · Dependency Graphs · Annotations

No API keys. No cloud. No Docker.
Just bun and SQLite.

Semantic Search · Auto-generated Wiki
Cross-session Memory · Dependency Graphs · Annotations