Skip to main content
Glama
deceptikon

Vault MCP Server

by deceptikon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
VAULT_PATHNoPath to the UniHub Vault directory. If not set, the server checks default locations: ./.unihub-vault/UniHubVault and ~/Q/massage.kg/.unihub-vault/UniHubVault.

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_issueA

Create a new issue in the 10_Inbox directory.

Args:
    name: Short descriptive name for the issue.
    body: Detailed description of the issue.
    tags: Optional list of tags for categorization.

Returns:
    8-character unique issue ID.
read_issueA

Read an issue's content by its unique ID.

Args:
    iss_uniq_id: 8-character unique issue ID.

Returns:
    Full content of the issue file.
update_issueA

Update an issue's content by its unique ID.

Args:
    iss_uniq_id: 8-character unique issue ID.
    content: New content to write or append.
    append: If True, appends to end of file; otherwise replaces entirely.

Returns:
    Confirmation message.
move_issueA

Move an issue to a different stage.

Args:
    iss_uniq_id: 8-character unique issue ID.
    stage: Target stage folder name. One of:
           - "10_Inbox" or "inbox"
           - "20_Processing" or "processing"
           - "30_ToReview" or "review"
           - "999_Finished" or "finished"

Returns:
    Confirmation message with new location.
list_issuesA

List all issues in a specific stage.

Args:
    stage: Stage folder name. One of:
           - "10_Inbox" or "inbox" (default)
           - "20_Processing" or "processing"
           - "30_ToReview" or "review"
           - "999_Finished" or "finished"

Returns:
    Newline-separated list of issue filenames.
read_noteA

Read any note from the vault.

Args:
    path: Path relative to vault root (e.g., "50_Protocols/Auth.md").

Returns:
    Full content of the note.
list_notesA

List all markdown files in a directory.

Args:
    directory: Directory path relative to vault root.
               If None, lists root directory.

Returns:
    Newline-separated list of filenames.
search_vaultA

Search through all .md files in the vault.

Auto-detects search type:
- If query contains regex metacharacters (.*+?^${}()|[]\), uses regex search.
- Otherwise, uses case-insensitive keyword search.

Args:
    query: Search term or regex pattern.

Returns:
    Matching lines in format: filepath:linenum: content
get_statusA

Get an overview of vault status: issues by stage and recent notes.

Provides a quick dashboard showing:
- Issue count per stage with recent items
- Recently modified notes across the vault

Returns:
    Formatted status summary.
set_telegram_webhookB

Set the Telegram bot webhook URL.

check_telegram_webhookA

Check Telegram bot webhook status.

poll_telegram_updatesB

Poll Telegram for updates and forward them to local webhook.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 12 tools

Disambiguation5/5

Every tool has a clearly distinct purpose: issue CRUD and staging, note reading and listing, vault search, status overview, and three separate Telegram webhook operations (check, set, poll). No two tools overlap in function or could be confused for each other.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (create_issue, read_note, list_issues, set_telegram_webhook, etc.). The verb consistently leads, making the action obvious and the object clear, with no mixed conventions or ambiguous abbreviations.

Tool Count5/5

With 12 tools, the set is well-scoped for a vault management server. Each tool addresses a specific need in issue tracking, note access, search, and Telegram integration; none are redundant or excessive for the intended functionality.

Completeness4/5

The core issue lifecycle (create, read, update, move between stages, list) is complete, and note reading/searching is well covered. Minor gaps include the lack of an explicit delete operation for issues and no create/update/delete for notes, but these are likely intentional design choices for a vault-based workflow.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources