ragnarok

Name: ragnarok
Author: freyr

by freyrversion 1.1.0i★ –iRuns on your computer

Registry nameio.github.freyr/ragnarok

Install

Overview

Description from the maker (original English)

Local RAG search over Obsidian vaults: SQLite hybrid search with local Ollama embeddings.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: RAGNAROK_HOME

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "ragnarok": {
      "command": "uvx",
      "args": [
        "ragnarok-mcp",
        "serve"
      ],
      "env": {
        "RAGNAROK_HOME": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add ragnarok --env RAGNAROK_HOME=your-value -- uvx ragnarok-mcp serve

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "ragnarok": {
      "command": "uvx",
      "args": [
        "ragnarok-mcp",
        "serve"
      ],
      "env": {
        "RAGNAROK_HOME": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "ragnarok": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "ragnarok-mcp",
        "serve"
      ],
      "env": {
        "RAGNAROK_HOME": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

RAGNAROK_HOME env
The folder that holds config.toml, data/ and logs/. Default: ~/.ragnarok.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account freyr, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7259 servers in this category
Published to the registry more recently than 96% of the other 7259 servers in this category
Basic checks equal to or better than 100% of the other 7259 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is ragnarok safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.1.0) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

ragnarok

Local RAG search over Obsidian vaults for Claude Code.

ragnarok indexes the Markdown notes of one or more Obsidian vaults on your computer. A local MCP server gives Claude Code search tools over the index. No note leaves the computer: the embeddings come from a local Ollama model, and the index is one SQLite file.

Features

Hybrid search. Each query runs a dense search (embeddings in sqlite-vec) and a keyword search (SQLite FTS5 with BM25). Reciprocal rank fusion joins the two lists. The unit of rank is the note, with its best section.
Heading chunks. The splitter cuts each note at its headings and joins very short sections.
Metadata from frontmatter or path. Each note gets a vault, a project, an area, a type, a status and ticket keys. The frontmatter gives these values first. For a note without them, path rules in the configuration give them.
Project search. find_projects finds the earlier projects that a prompt continues or resembles, also when the prompt does not name the project. list_project gives all notes of a project.
Always current. Each tool call first scans the vaults for changed notes (usually less than 100 ms) and embeds them. There is no watcher process.
Private notes. Notes under the configured private paths are in the index, but the server does not return them. Only the user can open them, with allow_private = true in the configuration.
Credential redaction. The indexer and open_note replace literal passwords, tokens and keys with [REDACTED]. The vault files do not change.
Frontmatter backfill. ragnarok backfill propose writes a proposal of the missing frontmatter keys for a vault. ragnarok backfill export writes a JSON file with the title and the first lines of each public note that needs a description (credentials removed). Claude writes the descriptions into one or more JSON files, {path: {"description": "...", "type": "..."}}. ragnarok backfill merge ... puts them into the proposal, removes credentials, reports each description of more than 25 words and each row with no description, and replaces a default type with a valid type from Claude. You examine the proposal, then ragnarok backfill apply makes a backup archive of the vault and adds only the missing keys.
Evaluation. ragnarok eval compares grep, keyword, dense and hybrid search on your own question sets. ragnarok eval agent compares a Claude Code agent with grep and an agent with the MCP tools.
One-command setup. ragnarok init installs the model and the index, and registers the MCP server in Claude Code when the Claude Code plugin does not give it. ragnarok doctor checks the setup.

Requirements

macOS with Homebrew. The setup uses brew services for Ollama.
Ollama: brew install ollama.
Claude Code.
uv: brew install uv. uv installs Python 3.12. setup.sh installs uv if it is missing.

Setup

ragnarok is on PyPI as ragnarok-mcp and in the MCP Registry as io.github.freyr/ragnarok.

With the Claude Code plugin (no clone)

In Claude Code:

/plugin marketplace add freyr/ragnarok-claude-plugin

/plugin install ragnarok@ragnarok

Then in a terminal:

uvx ragnarok-mcp init

The plugin starts the server with uvx ragnarok-mcp serve and adds the search guidance to each session. The home folder is ~/.ragnarok. To use a different folder, set RAGNAROK_HOME in the env of ~/.claude/settings.json and in your shell.

From a checkout

git clone https://github.com/freyr/ragnarok.git

cd ragnarok ./setup.sh # installs uv if needed, then runs ragnarok init

The checkout is the home folder.

What init does

ragnarok init does six steps. It skips each step that is already done:

It writes config.toml from config.example.toml. It asks for the vault root, the folder that holds your vault folders, and adds each subfolder as a vault.
It checks that Ollama is installed.
It runs Ollama as a login service with brew services start ollama (it asks first). If Ollama runs outside brew services, for example ollama serve in a terminal, init stops it and starts the service.
It pulls the embedding model.
It builds the index. A vault with 1,500 notes takes approximately 12 minutes on an Apple Silicon Mac.
When the plugin ragnarok gives the MCP server, it removes a registration at the user scope (it asks first). Else it registers the MCP server ragnarok in Claude Code at the user scope (it asks before it replaces another registration).

Restart Claude Code after step 6. ragnarok doctor checks the same six parts and prints the fix for each failure.

Before step 5, examine config.toml: remove a folder that is not a vault, and add your private paths. A later change of the configuration applies at the next ragnarok index or MCP tool call, with no restart.

Use in Claude Code

The server gives six tools:

Tool	What it does
`search`	Hybrid search over the notes. Filters: vault, project, area, type, archived.
`find_projects`	The projects that match a prompt, with the summary and the matching notes of each project.
`list_project`	All notes of one project.
`open_projects`	The open projects (`state: in-progress` and `paused` by default), grouped by state, newest update first.
`open_note`	The text of a note or of one section, with its links and backlinks. A note of more than 4,000 words gives an outline: each section with its heading path, words and first sentence.
`find_by_jira`	The notes that contain a ticket key, for example `ABC-123`.

The plugin adds the guidance below to each session itself, with the plugin tool names mcp__plugin_ragnarok_ragnarok__*. Without the plugin, Claude Code loads MCP tools on demand. To make Claude use them before grep, add a short instruction to your ~/.claude/CLAUDE.md file, for example:

## Finding notes: ragnarok first

The ragnarok MCP server indexes my Obsidian vaults. Use it before Grep or Glob whenever you look for notes, earlier work or context:

find_projects: the prompt continues or resembles earlier work and names no project. Then call list_project on the best match (look at the top 3).
search: facts, decisions, how something was done. Filters: vault, project, area, type.
open_note: read a note or one section, with its links and backlinks. A long note gives its outline first; open the section you need by heading.
open_projects: which projects are in progress or paused.
find_by_jira: a ticket key such as OPS-77.

The tools are deferred. Load them in one call before the first use: ToolSearch with select:mcp__ragnarok__search,mcp__ragnarok__find_projects,mcp__ragnarok__list_project,mcp__ragnarok__open_projects,mcp__ragnarok__open_note,mcp__ragnarok__find_by_jira.

If the tools are absent (for example on a computer without ragnarok), fall back to Grep and say so. Results can be unrelated: read the text before you rely on it, and cite note paths. Private notes are refused by design; do not work around the refusal with Read or Grep.

Adapting to your vaults

docs/vault-requirements.md tells how a vault must look to get the most from ragnarok: headings, project folders, SUMMARY.md, frontmatter and private folders.

The default path rules expect / / /note.md. If your vaults look different, the repo skill .claude/skills/adapt-vault/ guides Claude Code through the changes. Open Claude Code in the checkout and ask it to adapt ragnarok to your vaults. The skill:

runs ragnarok survey on each vault;
agrees the private folders with you, before any other change and before a new vault goes into vaults;
writes the path rules into config.toml, checked with ragnarok inspect;
runs the frontmatter backfill, if you agree, with your review before apply;
writes a small evaluation set from your notes and runs ragnarok eval mechanical;
adds the guidance above to your ~/.claude/CLAUDE.md, after it asks you.

It changes only config.toml and adds frontmatter keys. It never moves, renames or deletes a note or a folder.

Configuration

config.toml is in the home folder. A relative path in it is relative to the home folder. config.example.toml explains each key. The most important keys:

Key	What
`root`, `vaults`	The folder that holds the vaults, and the vault folders to index.
`[vault_paths]`	The folder of a vault that is not in `root`, for example `kb = "~/code/kb"`. A note key stays `/` .
`private_patterns`	Glob patterns of private notes, for example `"Notes/Journal/**"`.
`model`, `dimension`	The Ollama embedding model and its vector size. A change needs `ragnarok index --rebuild`.
`min_words`, `max_words`	The chunk size limits of the splitter. A change needs `ragnarok index --rebuild`.
`project_markers`	A folder that holds one of these files is a project folder (default `DRIVERS.md`, `SUMMARY.md`).
`jira_prefixes`	The ticket prefixes that `find_by_jira` knows.
`[vault_rules. ]`	The path rules of one vault: which folder gives the area and the project.

Note metadata

ragnarok reads these frontmatter keys. Each key is optional:

---

project: heating-upgrade # the project slug; default: from the path rules area: home # a wide subject; default: from the path rules type: plan # drivers, summary, research, spec, plan, brainstorm, review, decision,

guide, reference, meeting, log, template or note

status: active # active or archived; a note in an _archive folder, or in a project

whose SUMMARY.md has state: superseded or abandoned, is archived; state: done is current

description: One sentence about the note, which improves find_projects. jira: [ABC-123] # ticket keys, in addition to the keys in the text

Without frontmatter, the path rules give the metadata. The default rules work for a vault with the layout / / /note.md. For a different layout, add a [vault_rules. ] table. Use ragnarok inspect to see the metadata of a note.

Commands

Command	What it does
`ragnarok init`	Sets up this computer (see Setup).
`ragnarok doctor`	Checks the setup.
`ragnarok index [--rebuild]`	Adds, changes and removes notes in the index. After a change of the path rules, the private paths or the markers, it derives the metadata of all notes again, with no new embeddings. When a `.md` marker file is added or removed, it does the same for the notes under the folder of that file. `--rebuild` is needed only after a change of `model`, `dimension`, `min_words` or `max_words`.
`ragnarok status`	Shows the size and the state of the index.
`ragnarok search " "`	Searches from the terminal.
`ragnarok inspect ...`	Shows the metadata of notes.
`ragnarok chunks ... \	--stats`	Shows the chunks of notes, or the totals.
`ragnarok serve`	Runs the MCP server on stdio. Claude Code starts it.
`ragnarok backfill propose\	export\	merge\	apply [file...]`	Proposes, describes and applies missing frontmatter keys. The order is `propose`, `export`, Claude writes descriptions, `merge ...`, you examine the proposal, `apply`.

| ragnarok survey [--json] | Prints the folders, frontmatter keys, marker files, name patterns and ticket prefixes of a vault folder. Run it before

Only the beginning is shown; read the rest in the repo

ragnarok

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

ragnarok

Features

Requirements

Setup

With the Claude Code plugin (no clone)

From a checkout

What init does

Use in Claude Code

Adapting to your vaults

Configuration

Note metadata

guide, reference, meeting, log, template or note

whose SUMMARY.md has state: superseded or abandoned, is archived; state: done is current

Commands