QwikVault MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_LOG_LEVEL | No | Log verbosity: debug | info | warn | error | info |
| MCP_WIKI_ROOT | No | Absolute path to the directory containing .brain_wiki/ | process.cwd() |
| MCP_TOKEN_BUDGET | No | Max token budget for Directory-tree.md read operations | 100000 |
| MCP_WIKI_LANGUAGE | No | Enforce wiki write language: auto | vi | en | auto |
| MCP_ENABLE_EMBEDDING | No | (v2) Enable optional vector layer for wikis >1,000 articles | false |
| MCP_ENFORCE_WIKI_FIRST | No | Enforce /wiki read-map before other wiki commands in each server process | false |
| MCP_DISABLE_INSTANCE_LOCK | No | Allow concurrent instances for multi-agent swarm configurations | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cmdA | Execute QwikVault MCP commands using slash syntax. All features are available through this single entry point. Commands: /wiki (write|read|smart-read|analyze|read-map|search|suggest|list|emit|sync|status|report|delete), /health, /help. Type /help to see full command reference. |
| rawA | Legacy tool passthrough. Use cmd() with slash commands instead. raw({ tool: "view_file", args: { path: "..." } }) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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'.