Vulcanus
Related Servers
Alternatives to Vulcanus
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceLocal, searchable project memory for AI coding agents. Markdown source of truth, MCP interface, safe structured updates311Apache 2.0
- AlicenseNot gradedqualityBmaintenanceExposes a living systems memory vault to autonomous agents, letting them search notes with BM25 ranking, read sections within token budgets, extract API/port/schema contracts, compute dependency blast radius, and run machine-verifiable invariant assertions before mutating code. It also supports surgical frontmatter edits, schema linting, wikilink integrity checks, and worklog recording, over stdio MCP.MIT
- AlicenseNot gradedqualityCmaintenanceProvides long-lived, cross-project technical memory for AI agents via markdown cards stored in git and indexed by SQLite, enabling search, retrieval, and human-reviewed knowledge management.ISC
- AlicenseNot gradedqualityBmaintenanceProvides structured, addressable access to a local markdown vault with heading-anchored fragments, BM25 search, and stable IDs for verifiable retrieval.14 npm2MIT
- AlicenseAqualityAmaintenanceVault-native, accountable memory for Claude Code and MCP clients. Markdown is the source of truth, no LLM on the Stop path.61 npm2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceA local-first CLI and MCP server that helps you build and search a personal knowledge vault from Markdown notes, with semantic search and AI-powered features like stale note detection and session memory harvesting. It’s provider-agnostic, requires no GPU in its default mode, and exposes your vault as long-term memory to any MCP-compatible AI tool like Claude Code.47Apache 2.0
TDQS
Scored across 8 tools
Each tool has a clear, distinct purpose: recall for capsule retrieval, search for text search, list_projects for project routing, append_decision/update_capsule/append_rule for distinct write operations, and vault_status/doctor for health checks at different granularities. Descriptions explicitly cross-reference when to use which tool, eliminating ambiguity.
Most tools follow a verb_noun pattern (list_projects, append_decision, update_capsule, append_rule), but recall, search, and doctor are single verbs, and vault_status is a noun compound. The minor inconsistency is easy to read and does not hinder understanding.
With 8 tools, the set is well-scoped for a project memory and vault management server. Each tool earns its place, covering reading, searching, updating, and validating without bloat or redundancy.
The core workflows—accessing capsules, searching, updating summaries, appending decisions/rules, and checking health—are covered. Slight gaps exist: no direct tool to read decisions or rules (though search can find them) and no explicit project creation, but these may be out of scope for the vault's purpose.