hive
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vault_listB | List vault projects, or files within a project. When called without arguments, lists all available projects. When called with a project, lists files in that project directory. |
| vault_queryB | Read content from a vault project — use instead of direct filesystem access. |
| vault_searchB | Search the vault: full-text, ranked, or recent changes. Default mode: flat full-text search across all vault files. Ranked mode (ranked=True): results scored by relevance. Recent mode (since_days>0): files changed in the last N days. rank_by mode (rank_by != 'bm25'): lessons-only, ranked by usage. |
| session_briefingA | Call at the start of every new session to load project context. Without a project, returns the available project list with a usage hint — discoverability parity with vault_health() and worker_status(). With a project, assembles active tasks, recent lessons, git activity, and project health into a single response (replaces 3-4 manual calls). |
| vault_writeA | Write to the vault: append, replace a section, or create a new file. Modes:
|
| vault_patchA | Surgical find-and-replace in a vault file with auto git commit. Supports single or multi-replacement. For a single replacement, provide
Each Uses 3-pass cascading match: exact → body-only → whitespace-normalized. |
| vault_commitA | Stage everything in the vault and create one commit. Companion to Returns the new commit SHA on success, a clean-tree notice when there is nothing to commit, or a human-readable error. |
| vault_deleteA | Delete a single file from the vault (destructive; recoverable via git). Removes one file and, by default, commits the deletion so it stays
recoverable from git history ( |
| vault_healthA | Return vault health metrics, validation, and optional usage analytics. Always emits the Without parameters, returns a health summary for all projects. When checks are specified, runs drift detection (frontmatter, stale, links). When include_usage is True, appends tool usage analytics. When include_runtime is True, appends runtime metadata (uptime, tools, budget). |
| capture_lessonA | Capture lessons: inline / batch write, or lookup by keyword. Inline mode (default): provide title, context, problem, solution.
Batch mode: provide text to extract lessons automatically via worker.
Lookup mode: provide |
| delegate_taskA | Offload work to a cheaper model or summarize vault files. When project is provided, reads a vault file. Small files (≤50 lines) are returned directly. Large files are auto-delegated to a worker for summarization — falls back to raw content if workers are unavailable. |
| worker_statusA | Show worker health: configuration, reachability, model, and usage. HIVE-384 reshaped this tool, and the reshape is the point rather than a side effect. The old output led with a dollar budget and reported two providers by configuration: it said "Ollama: offline / OpenRouter: no API key" for an unknown length of time while every caller treated the worker as a working capability. A status surface that cannot distinguish "configured" from "answers" is how a dead backend stays invisible. So reachability is probed, not inferred, and reported separately from configuration. The dollar figures are gone: on a flat subscription they would read zero forever, and a gauge that always says the same thing looks like a working gauge. |
| vault_askA | Ask a natural-language question; get a source-cited synthesized answer (semantic retrieval / RAG) or relevant vault sections when no synthesis model is configured. OPTIONAL — disabled by default. Requires the |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| retrospective | Quick end-of-session review that extracts lessons and appends them to the vault. |
| delegate | Structured protocol for delegating tasks to cheaper models via hive-worker. |
| vault_sync | Post-sprint vault synchronization — reconcile docs with shipped code. |
| benchmark | Estimate token savings from hive MCP tools in the current session. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| projects_resource | List all vault projects with file counts and available shortcuts. |
| health_resource | Vault health metrics for all projects. |
TDQS
Scored across 13 tools
Most vault_* tools have clearly distinct purposes, but vault_query, vault_search, and vault_ask are all read-oriented and could occasionally be confused by an agent. The descriptions do enough to separate exact-content reads from full-text search and RAG, so this is only a minor concern.
The dominant vault_* verb pattern is consistent and readable, covering commit, list, query, search, write, patch, delete, health, and ask. The auxiliary tools (session_briefing, worker_status, capture_lesson, delegate_task) break the prefix pattern, though they are still reasonably named and not chaotic.
Thirteen tools is well within the ideal 3–15 range and each tool maps to a meaningful capability: vault lifecycle, health, search, lessons, session context, worker status, and delegation. Nothing feels redundant enough to cut, and the scope justifies the count.
The vault domain is well covered: list, read, write, patch, search, delete, commit, health, and ask provide a strong lifecycle. Minor gaps exist—no explicit project creation, lesson-specific update/delete, or git history surface—but most can be worked around via existing tools.