mindgap
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MINDGAP_DB | No | Override the path to the SQLite database file (default $MINDGAP_HOME/mindgap.db) | |
| MINDGAP_HOME | No | Override the home directory for mindgap data (default ~/.mindgap) |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mindgap_ingestA | Validated batch write (workhorse). Upserts nodes + adds edges in one transaction; rejects the WHOLE payload (no partial commit) if any edge endpoint is neither in the DB nor in the payload. Returns the persisted rows so a caller can't claim a write that didn't land. |
| mindgap_add_nodeC | Single node upsert. Returns the persisted row plus stubs_created and warnings. confidence defaults to 0.7. |
| mindgap_linkA | Add one edge between two EXISTING nodes. Hard-fails (isError) if either endpoint is missing — does not auto-stub. |
| mindgap_unlinkA | Delete edge(s) between src and dst (optionally a specific rel). Returns removed count and any nodes left edgeless. |
| mindgap_get_nodeA | Fetch a node and its neighborhood (depth 1..3, default 1). Missing id returns node:null (clean miss, not an error). |
| mindgap_findB | Search nodes by query/type/tag. Returns results + count (limit 1..200, default 50). |
| mindgap_contextB | Render a markdown digest (matched nodes + neighbor links) for a query, mirroring |
| mindgap_statsB | Graph counts: {nodes, edges, by_type, by_rel}. |
| mindgap_exportA | Write a JSON snapshot of the whole graph. Default path data/snapshots/.json; absolute out path allowed. |
| mindgap_remove_nodeA | Delete a node (cascades its edges). Destructive; for stub cleanup. |
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 10 tools
Each tool has a clear, distinct purpose with no overlap. For example, add_node handles single upsert, ingest handles batch writes, link and unlink are opposites, find and get_node serve different retrieval needs, and context provides a digest rendering.
All tools share the 'mindgap_' prefix and use clear verbs, but some are verb_noun (add_node, get_node, remove_node) while others are single verbs (context, export, find, ingest, link, stats, unlink), representing a minor inconsistency.
With 10 tools, the set is well-scoped for a graph knowledge base server, covering core operations without being overly large or insufficient. Each tool serves a necessary function.
The tools cover CRUD-like operations via upsert, batch ingest, retrieval, search, linking, unlinking, stats, export, and context rendering. Minor gaps include lack of explicit update tool (handled by upsert) and dedicated tag management, but core workflows are well-supported.