Skip to main content
Glama

Server Details

Shared product-knowledge graph for AI agent fleets — vault tools + agent self-signup over MCP.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
Brainz

TDQS

A4.1/5.0

Scored across 18 tools

Disambiguation4/5

Most tools target a clearly distinct resource+action (get_concept vs get_related vs get_context vs search_concepts vs list_concepts are separated by id/query/graph-walk/metadata), and the task lifecycle (create/take/complete/list_tasks) is clean. A couple of pairs blur slightly — onboard vs sync are both multi-action 'start/status/complete' playbook workflows, and get_concept's neighbor list overlaps with get_related — but descriptions disambiguate them well.

Naming Consistency4/5

The dominant pattern is consistent verb_noun (create_task, get_concept, list_tasks, search_concepts, upsert_concept, link_concepts, delete_concept). A handful of single-word tools (burndown, dream, onboard, sync) and vault_stats break the pattern, but everything remains readable and predictable.

Tool Count4/5

18 tools is on the heavy side of the 3-15 ideal band, but each covers a genuinely distinct capability across a rich domain (concepts, graph, tasks, search, context, onboarding, sync, dream, metrics, vaults). No obvious filler tools; the count tracks the multi-feature scope reasonably.

Completeness4/5

Concept CRUD is well covered (upsert/get/list/search/delete) plus linking and graph traversal, and the task lifecycle (create/take/list/complete) is present. Minor gaps: no task update/delete, no explicit unlink_concepts (only delete removes outgoing edges), and no vault rename/delete — but agents can work around these via upsert/delete.

Available Tools

18 tools
burndownTask burndownA
Read-only
Inspect

Burndown and flow metrics for the vault's tasks, computed from their recorded history. scope is a concept id (an iteration, milestone, feature, domain or any concept tasks are part_of / realize, including nested containers) or tag:<tag>; omit it for every task. Returns, for the window: open vs done over time with an ideal line when the scope has start/end dates, scope changes, velocity per iteration or week, a projected completion date with an optimistic/pessimistic range, lead and cycle time per agent label, and claims held longer than staleAfterHours. metrics limits the sections returned. Read-only.

Inputs: to, from, unit, scope, +3 more.

complete_taskComplete a taskAInspect

Mark a task done. Sets taskStatus=done + doneAt and appends outcome to the task body as an Outcome section. The result carries a one-line reminder that the rest of the graph is not updated automatically.

Inputs: id (required), outcome (required).

create_taskCreate a taskAInspect

Turn a finding into first-class work: creates a task-type concept with taskStatus=open and the given relations — part_of a domain and/or an epic, realizes stories/features, governed_by specs — plus codeAreas pointing at where the work lands. Use when you discover work that isn't reflected in the codebase yet (a gap, a needed fix, a follow-up). The task then shows up in list_tasks / take_task and on the Kanban board.

Inputs: body (required), title (required), epic, tags, +4 more.

create_vaultCreate a vaultAInspect

Create a new, empty vault owned by you and add it to this connection. Returns the new vault and the vaults this connection can now use. Once a connection covers more than one vault, every vault tool takes a vault argument (a slug or id) and list_vaults lists the vaults. Each account has a vault limit and an hourly creation limit.

Inputs: name (required), slug.

delete_conceptDelete conceptA
Destructive
Inspect

Remove a concept from the vault and all of its outgoing edges. Use to clear a note that is wrong, obsolete, or junk (e.g. a probe or test node that shouldn't be in the graph). Idempotent: deleting an id that doesn't exist is a no-op success (deleted:false), not an error. Deletion is permanent — prefer upsert_concept to correct a note you want to keep. Returns { deleted, id }.

Inputs: id (required).

dreamDream (nightly consolidation)A
Destructive
Inspect

Dreaming: a scheduled consolidation sweep over this vault. Light stages what changed since the last dream (near-duplicate concepts, finished task outcomes, hygiene counts); REM asks an LLM for proposals; deep applies the ones that pass threshold gates: merges duplicates (edges redirected, the other tombstoned), promotes outcome knowledge into concepts, adds missing links, and files a task for each contradiction. A sweep that would touch too much of the vault is rejected; every applied dream keeps preimages and can be reverted. {action: "status"} shows schedule + last dream; {action: "run"} dreams now; {action: "diary"} reads the Dream Diary; {action: "revert", id} undoes one dream; {action: "configure", ...} sets the schedule, mode (apply, propose, light-only), phases, thresholds, caps, a stricter loss rail and the LLM choice; {action: "apply", id, proposals?} decides a proposed dream. Without an LLM only light runs.

Inputs: action (required), id, llm, caps, +9 more.

get_conceptGet conceptA
Read-only
Inspect

Fetch one concept by exact id: full markdown body, metadata, and its direct graph neighbors (each with the relation that connects it). Use after search_concepts or when another note wiki-links an id you need in full. The neighbors list tells you what to fetch next. If you don't know the id, use search_concepts instead.

Inputs: id (required).

get_contextAssemble context bundleA
Read-only
Inspect

Assemble a markdown briefing of the concepts most relevant to a query and/or explicit ids, expanded through the graph and trimmed to a token budget. The briefing is self-contained, so it can be handed to another agent or pasted into a prompt as-is. The final JSON line reports which concept ids were included, whether the bundle was truncated, and its approximate token count. Provide at least one of query or ids.

Inputs: ids, depth, query, product, +1 more.

list_conceptsList conceptsA
Read-only
Inspect

Enumerate concept metadata (no bodies), optionally filtered by product, type, or a single tag. Use to get the lay of the land in an unfamiliar vault, to audit what exists (e.g. all decisions for a product), or when search vocabulary isn't matching. For content, follow up with get_concept or get_context.

Inputs: tag, type, product.

list_tasksList tasksA
Read-only
Inspect

List the vault's work pile: task-type concepts with their lifecycle (open/taken/done), oldest first, including who has taken each one (takenBy). Filter by taskStatus or by the domain the tasks are part_of. Read-only; take_task is what claims a task.

Inputs: domain, taskStatus.

onboardOnboard this vaultAInspect

Index an existing product's codebase into this vault. {action: "start"} returns the onboarding playbook: a method for surveying the codebase and recording its product knowledge (domains, features, stories, specs, workflows, decisions, constraints) as concepts via upsert_concept, each anchored to the code with codeAreas. {action: "status", areaList} reports onboarded state, concept counts and, given your repo's source areas (Brainz can't read the repo), which areas are covered or uncovered. {action: "complete", summary, areaList} marks the vault onboarded and stores the summary; it is rejected while too many areas are uncovered. Until onboarding completes, search_concepts and get_context results include a one-line note saying so.

Inputs: action (required), summary, areaList, repoHint, +1 more.

search_conceptsSearch conceptsA
Read-only
Inspect

Search the product knowledge vault by free-text query. Useful when you need product knowledge but don't yet know which concept ids exist. Returns ranked hits (id, title, type, score, snippet) only; get_concept returns one full note and get_context an assembled briefing. An empty hit list means nothing matched.

Inputs: query (required), mode, tags, type, +2 more.

syncSync this vault to the current codeAInspect

Re-index an onboarded vault after the code changes (drift). {action: "start"} returns the sync playbook: the vault's last_synced_at, a coverage map over the concepts' code_areas, and a method for re-indexing only what changed (you run git — Brainz can't read the repo — and pass back changedPaths + areaList): update stale concepts in place, add concepts or tasks for new work, and report coverage gaps. {action: "status", areaList} reports onboarded state, last sync time, staleness, concept counts and coverage. {action: "complete", summary, areaList} stamps last_synced_at and appends the summary to the product-onboarding-summary concept (a running sync log). After ~14 days without a sync, get_context and search results include a one-line note saying so.

Inputs: action (required), summary, areaList, productName, +1 more.

take_taskTake a task off the pileAInspect

Claim a task and get its briefing in one call. Pass an id to claim a specific task, or omit it to claim the next open task (oldest open by createdAt then id). Atomically flips the task to "taken" and records takenBy/takenAt; errors if it's already taken or done. Returns the task and a get_context-style briefing for its part_of domain plus the concepts it realizes / is governed_by (with code_areas). complete_task marks it done.

Inputs: id, takenBy.

upsert_conceptCreate or update conceptA
Destructive
Inspect

Write a concept note into the vault (creates or overwrites the markdown file, then reindexes it). Use to capture new product knowledge discovered during a task — a decision made, a constraint hit, a pattern adopted — so future agents can find it. Omit id to derive a slug from the title; pass an existing id to update that note. Body is markdown; [[wiki-links]] to other concept ids create graph edges. Returns the saved concept's metadata.

Inputs: body (required), title (required), id, tags, +12 more.

vault_statsVault statsA
Read-only
Inspect

Summarize the vault: counts of concepts and edges, the products and tags in use, a breakdown by concept type, and whether semantic search is available. Useful for gauging how much knowledge is here and which product/tag filters exist.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to persistently store, recall, and share scoped knowledge through a self-hosted MCP server that combines a knowledge graph, vector storage, and graph RAG.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables teams of AI coding agents (Claude Code, Cursor, Codex) to share persistent, time-aware graph memory and coordinate their work via MCP, so agents recall verified fixes at the moment of failure, learn procedures automatically, avoid file conflicts, claim tasks race-free, and hand off facts and decisions between sessions.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory graph, knowledge marketplace, and MCP tool gateway for autonomous AI agents. Agents store experiences, trade knowledge via micropayments, and discover capabilities across the Hive network.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources