never4ga-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NEVER4GA_VAULT | Yes | Path to your Markdown vault (e.g. ~/notes). Point it at a new vault or an existing folder of notes. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| never4ga_workspace_resolveB | Which Never4gA workspace a directory belongs to, and why. Mechanical: it refuses to guess rather than picking one. |
| never4ga_context_startupB | The smallest useful context for starting a session in a workspace: what it is, what binds it, what the last session did. Opens a session and returns its id. |
| never4ga_context_focusA | More context about particular terms, at a stated depth. Use when the startup pack was not enough or work moved to an unfamiliar area. |
| never4ga_searchB | Search the vault. Lexical always, and semantic as well when an embedder is configured; the lanes are fused by rank. Returns ranked results with the reason each was retrieved, and says when the index is stale. |
| never4ga_get_conceptB | One concept by its Never4gA id: its frontmatter, its body, and the relations the projection knows about. |
| never4ga_doctorA | Check vault health. Reports findings with repair hints and never repairs anything itself. |
| never4ga_work_searchC | Ask the workspace's tracker what is open. The tracker stays the system of record; this reads it rather than mirroring it. |
| never4ga_work_getB | Read one work item from the workspace's tracker. |
| never4ga_captureA | Put a thought, link or fragment in the Inbox without deciding where it belongs. Use when something is worth keeping and classifying it now would interrupt the work. |
| never4ga_checkpointA | Record what this session has done so far. Runtime state only: it never touches the vault, so an interruption cannot leave half a log behind. |
| never4ga_wrapA | Close a session: write the one activity log it leaves behind, and report what was declared along the way -- decisions, things worth remembering, work items that may need an update, and the context documents the session was given, with the question whether it changed anything they assert. It writes nothing but the log. Idempotent: wrapping twice updates one document rather than writing two, and a title given the second time replaces the first and renames the file. |
| never4ga_decideA | Draft a decision record. It is written as PROPOSED and is not in effect: an agent never authors an accepted decision, and only the maintainer moves one to accepted. |
| never4ga_work_createB | Create a work item on the workspace's tracker. Describes the change and sends nothing unless |
| never4ga_work_updateA | Change fields on a work item. Describes the change and sends nothing unless |
| never4ga_work_commentA | Comment on a work item, or replace a comment already made. Describes the change and sends nothing unless |
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 15 tools
Each tool has a clearly distinct purpose: session lifecycle (startup, checkpoint, wrap), vault retrieval (search, get_concept, context_focus), and work tracker operations (search, get, create, update, comment) are separated by domain prefixes and descriptions. Overlap is minimal, and the descriptions clarify boundaries.
All tools share the never4ga_ prefix and snake_case, which makes them groupable, but the action ordering varies: some use noun_verb (work_get, workspace_resolve), others verb_noun (get_concept), and several are bare verbs/nouns (wrap, decide, search). This is mostly consistent with minor deviations.
15 tools is at the upper end of the ideal range, but each tool maps to a distinct operation in session management, vault access, and work tracking. The set is well-scoped with no obvious redundancy.
Core lifecycle and retrieval workflows are covered, including session start/checkpoint/wrap, vault search and concept retrieval, and work item create/read/update/comment. Minor gaps exist (e.g., no work item delete or direct concept update/delete), but these may be intentional or manageable via other tools.