server-noonien
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOONIEN_GC | No | Delete tombstones without a daemon: only where this node is the directory's only writer — a promise nothing in the directory can prove. Where a daemon owns the directory (it announces itself with its knowledge file from startup) it has no effect: the daemon collects. Default is off. | off |
| NOONIEN_DIR | No | Directory holding this machine's shards: the file backend's store and the daemon's replica store. A leading ~ is expanded. Default is ~/.noonien. | |
| NOONIEN_BACKEND | No | file, memory or s3. Default is file. | file |
| NOONIEN_NODE_ID | No | This node's shard name — the identity the MCP server writes under and the daemon replicates. Must be unique per machine and written by a single server at a time. Default is the hostname. | |
| NOONIEN_S3_BUCKET | No | Bucket (required for the s3 backend). | |
| NOONIEN_S3_PREFIX | No | Key prefix all shard objects live under. Default is empty string. | |
| NOONIEN_S3_REGION | No | Region passed to the S3 client. Default is us-east-1. | us-east-1 |
| NOONIEN_S3_ENDPOINT | No | Custom endpoint for MinIO / R2 / Contabo and similar. | |
| NOONIEN_COMPACT_AFTER | No | Compact the local shard online after this many appended operations (0 disables). Default is 1000. | 1000 |
| NOONIEN_S3_FORCE_PATH_STYLE | No | Path-style requests. Default is on when an endpoint is set. |
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
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_entitiesC | Create multiple new entities in the knowledge graph |
| create_relationsB | Create multiple new relations between entities in the knowledge graph. Relations should be in active voice |
| add_observationsB | Add new observations to existing entities in the knowledge graph |
| update_entitiesA | Prefer this to deleting an entity and re-creating it under another name: rename existing entities and/or change their entity type, keeping their observations and relations |
| update_observationsA | Prefer this to delete_observations followed by add_observations: replace observation contents on existing entities in place |
| update_relationsA | Prefer this to deleting a relation and creating another: change the type of existing relations and/or repoint their endpoints |
| merge_entitiesA | Prefer this to deleting one entity and re-adding its observations and relations to another: merge an entity into another, unioning their observations and repointing its relations |
| delete_entitiesA | Delete multiple entities and their associated relations from the knowledge graph |
| delete_observationsC | Delete specific observations from entities in the knowledge graph |
| delete_relationsC | Delete multiple relations from the knowledge graph |
| read_graphA | Read the knowledge graph, or a page of it: the optional limit and offset take a slice of the entities in name order |
| search_nodesB | Search for nodes in the knowledge graph based on a query |
| open_nodesB | Open specific nodes in the knowledge graph by their names |
| read_conflictsA | Call this when a write may have been superseded by another machine, or before trusting an edit: it lists the elements more than one node has written, with their authors, so a last-writer-wins resolution is visible instead of silent |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| knowledge-graph | The full knowledge graph with all entities and relations |
TDQS
Scored across 14 tools
Each tool pairs a distinct resource (entity, observation, relation) with an action, and the update/merge tools clearly differentiate in-place edits from merges. The main soft spot is the read trio (read_graph, open_nodes, search_nodes), which are all retrieval operations and could occasionally be confused, though descriptions distinguish whole-graph paging, exact-name lookup, and query search.
Every tool follows a clean verb_noun pattern (create_entities, delete_observations, update_relations, merge_entities, read_graph, search_nodes). Conventions are uniform across all 14 tools with no mixing of styles.
14 tools is well within the sweet spot and each earns its place by covering a distinct resource-action pair across entities, observations, and relations plus graph-level reads. Nothing feels redundant or padded.
Full lifecycle coverage exists for all three resource types (create, update, delete on entities/observations/relations), supplemented by merge, rename-via-update, search, paged read, and conflict inspection. No obvious dead ends for a knowledge-graph workflow.