QwikVault MCP
Related Servers
Alternatives to QwikVault MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceEnables AI clients to incrementally build and maintain a git-backed personal wiki, providing long-term memory by compiling and cross-referencing knowledge across sessions.2MIT
- AlicenseNot gradedqualityCmaintenanceHosted shared knowledge base for AI agents. Store, search, and retrieve structured knowledge using semantic search. Agents contribute to a growing collective intelligence that compounds over time. No install — just a URL.1MIT
- FlicenseNot gradedqualityNot gradedmaintenanceProvides AI agents with a learning-based knowledge management system that stores, retrieves, and automatically relates knowledge using embeddings, with Git-based version control and Obsidian compatibility.-
- AlicenseNot gradedqualityBmaintenanceGives AI assistants persistent, queryable project memory for decisions, patterns, and rules, reducing the need to re-explain context in every prompt.11Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with queryable, version-controlled project rules and coding standards. Enables validation, rule-based guidance, and task summaries to keep AI work aligned with your project's conventions without repeating context.2MIT
- FlicenseAqualityNot gradedmaintenanceExposes an internal engineering knowledge base to AI assistants, allowing users to search and retrieve standards, runbooks, and architecture decisions. It supports RAG-enhanced search, document scraping, and specialized prompts for incident investigation and code reviews.5-
TDQS
Scored across 2 tools
The two tools overlap significantly: 'cmd' is the recommended interface for all operations, while 'raw' is a legacy passthrough that duplicates functionality. An agent may be confused about which tool to use, especially since both accept different argument formats.
Tool names are short and inconsistent: 'cmd' and 'raw' do not follow a predictable pattern like verb_noun. There is no clear naming convention across the set.
With only 2 tools for a server that features many wiki commands, health checks, and help, the number is very low. While all functionality is bundled into 'cmd', this creates a monolithic interface rather than a well-scoped tool set.
The 'cmd' tool appears to cover all intended operations (read, write, search, etc.), so the core surface is complete. However, the presence of a deprecated 'raw' tool indicates an incomplete transition, and there is no clear tool for help or health—these are subcommands of 'cmd'.