ragnarok
Related Servers
Alternatives to ragnarok
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Claude Code read/write access to an Obsidian vault, including creating, editing, searching, and browsing notes.8MIT
- AlicenseNot gradedqualityBmaintenanceLets Claude Code and Claude Desktop retrieve and explore an Obsidian vault through tools for semantic search, reading notes, following graph neighbors, and listing topics.MIT
- AlicenseNot gradedqualityAmaintenanceConnects Claude Desktop and Claude Code to an Obsidian vault by exposing notes as tools, enabling folder listing, note reading, text and semantic search, tag and link queries, and optional note creation, editing, and management, all locally without installing Node.js or editing JSON.MIT
- AlicenseNot gradedqualityCmaintenanceConnects Claude to a local Obsidian vault, enabling listing, reading, searching, and optionally editing notes via natural language, with all operations running locally.3,805 npmMIT
- AlicenseNot gradedqualityBmaintenanceGives Claude Code read-only semantic search over an Obsidian vault by reading the embedding files the Smart Connections plugin already produces, so no API key or network is needed at query time and it works across the WSL/Windows boundary. Exposes tools for meaning-based note and block search with folder scoping, related-note discovery, note reading, and index health checks.37 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides local hybrid search over an Obsidian vault via the Model Context Protocol. It enables Claude Code to retrieve relevant notes with citations, using on-device embeddings and BM25 rank fusion.11 npmMIT
TDQS
Scored across 5 tools
Each tool has a fairly clear niche: search is general hybrid retrieval, find_projects is prompt-driven project matching, list_project enumerates one project's notes, open_note reads full content, and find_by_jira is a keyed lookup. The only real friction is between search and find_by_jira (both retrieve notes) and between find_projects and list_project, though the descriptions make the intent distinguishable.
Four of five tools follow a clean verb_noun snake_case pattern (find_projects, list_project, open_note, find_by_jira). The bare verb 'search' is a minor but reasonable deviation as the primary entry point.
Five tools is well within a healthy range and each covers a distinct retrieval need (general search, project discovery, project detail, note reading, Jira lookup). Nothing feels redundant or bolted on.
For a read-only vault retrieval server, the surface covers the main workflows: find notes, drill into projects, open content, and resolve Jira keys. Minor gaps exist around enumerating projects/vaults/areas without a prompt (all project discovery routes through find_projects), which agents would have to work around via search.