Servers Playground How we check Add a server Log in

Brainz

Working

ai.brownmatter/brainzv0.1.0 Domain verified

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

AI & Agents

Website Registry entry

Maintain this server? Claim it

Try it

Call this server's tools from your browser. Nothing to install.

https://brainz.brownmatter.ai/mcp

Authorization (optional)

Bearer bz_... vault API key (optional: clients that support MCP OAuth sign in instead). Without it, tools/list works and every tool call answers with an OAuth 401 challenge.

Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.

Tool list from our last check. Connect live to refresh it.

complete_task

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.

idstring, required

Id of the task to mark done.

outcomestring, required

A short account of what was done — appended to the task body as an Outcome section.

This tool isn't marked read-only, so it may change something on the server or in an account you connected.

I understand, run it anyway

Brainz MCP server | mcptry

Tools (16)

complete_task

Argument	Type	Description
id*	string	Id of the task to mark done.
outcome*	string	A short account of what was done — appended to the task body as an Outcome section.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id",
    "outcome"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Id of the task to mark done."
    },
    "outcome": {
      "type": "string",
      "description": "A short account of what was done — appended to the task body as an Outcome section."
    }
  },
  "additionalProperties": false
}

create_task

Turn a finding into first-class work: creates a `task`-type concept with taskStatus=open and the given relations — part_of a domain, `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.

Argument	Type	Description
body*	string	Markdown description of the work. [[wiki-links]] become edges.
tags	array	Tags, e.g. a priority tag like "high" or an area tag.
title*	string	Human-readable task title (required, non-empty).
domain	string	Domain concept id this task is part_of.
realizes	array	Story/feature concept ids this task realizes (creates `realizes` edges).
codeAreas	array	Rough codebase paths/globs where the work lands.
governedBy	array	Spec concept ids that govern this task (creates `governed_by` edges).

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "title",
    "body"
  ],
  "properties": {
    "body": {
      "type": "string",
      "description": "Markdown description of the work. [[wiki-links]] become edges."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags, e.g. a priority tag like \"high\" or an area tag."
    },
    "title": {
      "type": "string",
      "description": "Human-readable task title (required, non-empty)."
    },
    "domain": {
      "type": "string",
      "description": "Domain concept id this task is part_of."
    },
    "realizes": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Story/feature concept ids this task realizes (creates `realizes` edges)."
    },
    "codeAreas": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Rough codebase paths/globs where the work lands."
    },
    "governedBy": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Spec concept ids that govern this task (creates `governed_by` edges)."
    }
  },
  "additionalProperties": false
}

delete_concept

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 }.

destructive

Argument	Type	Description
id*	string	Exact concept id (slug) to delete, e.g. "lead-scoring".

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Exact concept id (slug) to delete, e.g. \"lead-scoring\"."
    }
  },
  "additionalProperties": false
}

dream

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", enabled?, cadenceHours?} sets it up. Without an LLM only light runs.

destructive

Argument	Type	Description
id	string	With "revert": the dream id to undo (from "diary" or "status").
limit	integer	With "diary": how many entries to return (default 10).
action*	string	"status" reports whether dreaming is on, its cadence, the last/next dream and any sweep in flight. "run" starts (or continues) a sweep NOW and advances it as far as one request allows. "diary" returns recent Dream Diary entries (newest first). "revert" undoes one dream via its preimages (requires `id`). "configure" turns dreaming on/off and sets the cadence.
enabled	boolean	With "configure": turn nightly dreaming on or off.
cadenceHours	integer

get_concept

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.

read-only

Argument	Type	Description
id*	string	Exact concept id (slug), e.g. "lead-scoring".

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Exact concept id (slug), e.g. \"lead-scoring\"."
    }
  },
  "additionalProperties": false
}

get_context

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`.

read-only

Argument	Type	Description
ids	array	Explicit seed concept ids (kept first, in order).
depth	integer	Graph hops to expand from the seeds (default 1).
query	string	Search query used to pick seed concepts.
product	string	Restrict expansion to concepts of this product.
tokenBudget	integer	Approximate token cap for the bundle (chars/4, default 4000).

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "ids": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Explicit seed concept ids (kept first, in order)."
    },
    "depth": {
      "type": "integer",
      "default": 1,
      "maximum": 3,
      "minimum": 0,
      "description": "Graph hops to expand from the seeds (default 1)."
    },
    "query": {
      "type": "string",
      "description": "Search query used to pick seed concepts."
    },
    "product": {
      "type": "string",
      "description": "Restrict expansion to concepts of this product."
    },
    "tokenBudget": {
      "type": "integer",
      "default": 4000,
      "minimum": 1,
      "description": "Approximate token cap for the bundle (chars/4, default 4000)."
    }
  },
  "additionalProperties": false
}

get_related

Walk the knowledge graph outward from a concept and return everything within `depth` hops, with distance and the edge path that reached it. Use to map the blast radius before changing a feature (what depends on it, what constrains it, which decisions apply) or to discover structure that keyword search misses. Filter by relation names (e.g. depends_on) to follow only one kind of edge.

read-only

Argument	Type	Description
id*	string	Concept id to start from.
depth	integer	How many hops to traverse (1-3, default 1).
limit	integer	Max related nodes to return.
relations	array	Only follow edges with these relation names, e.g. ["depends_on", "part_of"].

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Concept id to start from."
    },
    "depth": {
      "type": "integer",
      "default": 1,
      "maximum": 3,
      "minimum": 1,
      "description": "How many hops to traverse (1-3, default 1)."
    },
    "limit": {
      "type": "integer",
      "minimum": 1,
      "description": "Max related nodes to return."
    },
    "relations": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Only follow edges with these relation names, e.g. [\"depends_on\", \"part_of\"]."
    }
  },
  "additionalProperties": false
}

link_concepts

Add a typed, directed edge between two existing concepts by editing the `from` note's frontmatter (e.g. lead-scoring depends_on contact-model). Use when you notice a relationship the vault is missing. Both concepts should already exist; use upsert_concept first if not.

Argument	Type	Description
to*	string	Target concept id.
from*	string	Source concept id (its file gains the relation).
relation	string	Edge type, e.g. part_of \| realized_by \| governs \| depends_on \| constrains \| supersedes \| related_to (default). Domain→domain links (related_to / depends_on) are encouraged where two domains share a boundary, so the graph shows how areas overlap.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "from",
    "to"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Target concept id."
    },
    "from": {
      "type": "string",
      "description": "Source concept id (its file gains the relation)."
    },
    "relation": {
      "type": "string",
      "default": "related_to",
      "description": "Edge type, e.g. part_of | realized_by | governs | depends_on | constrains | supersedes | related_to (default). Domain→domain links (related_to / depends_on) are encouraged where two domains share a boundary, so the graph shows how areas overlap."
    }
  },
  "additionalProperties": false
}

list_concepts

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.

read-only

Argument	Type	Description
tag	string	Only concepts carrying this tag.
type	string	Only concepts of this type.
product	string	Only concepts of this product.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "tag": {
      "type": "string",
      "description": "Only concepts carrying this tag."
    },
    "type": {
      "enum": [
        "concept",
        "domain",
        "feature",
        "story",
        "spec",
        "workflow",
        "task",
        "decision",
        "constraint",
        "pattern",
        "glossary"
      ],
      "type": "string",
      "description": "Only concepts of this type."
    },
    "product": {
      "type": "string",
      "description": "Only concepts of this product."
    }
  },
  "additionalProperties": false
}

list_tasks

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.

read-only

Argument	Type	Description
domain	string	Only tasks that are part_of this domain concept id.
taskStatus	string	Only tasks in this lifecycle state ("open" \| "taken" \| "done"). Omit for all.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "domain": {
      "type": "string",
      "description": "Only tasks that are part_of this domain concept id."
    },
    "taskStatus": {
      "enum": [
        "open",
        "taken",
        "done"
      ],
      "type": "string",
      "description": "Only tasks in this lifecycle state (\"open\" | \"taken\" | \"done\"). Omit for all."
    }
  },
  "additionalProperties": false
}

onboard

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.

Argument	Type	Description
action*	string	"start" returns the onboarding playbook, "complete" marks the vault onboarded (requires `summary`), "status" reports onboarded state and concept counts.
summary	string	Required with "complete": 2–5 sentences on what was indexed and any notable gaps — stored as the product-onboarding-summary concept.
areaList	array	With "status" or "complete": the repo's top-level source areas (packages/, apps//src subtrees, major dirs) from your own repo walk — Brainz can't read the repo. "status" diffs concepts' code_areas against this to report covered vs uncovered areas; "complete" is REJECTED if too many areas are still uncovered.
repoHint	string	With "start": where the codebase lives (path or URL), echoed into the playbook.
productName	string	With "start": the product's name, echoed into the playbook heading.

search_concepts

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.

read-only

Argument	Type	Description
mode	string	Search mode. "hybrid" (default) fuses keyword and semantic ranking; semantic silently falls back to keyword if embeddings are unavailable.
tags	array	Only return concepts carrying ALL of these tags.
type	string	Only return concepts of this type.
limit	integer	Max hits to return (default 10).
query*	string	Free-text search query, e.g. "lead scoring" or "session auth".
product	string	Only return concepts belonging to this product.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "mode": {
      "enum": [
        "hybrid",
        "keyword",
        "semantic"
      ],
      "type": "string",
      "default": "hybrid",
      "description": "Search mode. \"hybrid\" (default) fuses keyword and semantic ranking; semantic silently falls back to keyword if embeddings are unavailable."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Only return concepts carrying ALL of these tags."
    },
    "type": {
      "enum": [
        "concept",
        "domain",
        "feature",
        "story",
        "spec",
        "workflow",
        "task",
        "decision",
        "constraint",
        "pattern",
        "glossary"
      ],
      "type": "string",
      "description": "Only return concepts of this type."
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1,
      "description": "Max hits to return (default 10)."
    },
    "query": {
      "type": "string",
      "description": "Free-text search query, e.g. \"lead scoring\" or \"session auth\"."
    },
    "product": {
      "type": "string",
      "description": "Only return concepts belonging to this product."
    }
  },
  "additionalProperties": false
}

sync

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.

Argument	Type	Description
action*	string	"start" returns the sync (re-onboard) playbook — a DRIFT playbook scoped to what changed since the last sync (NOT the full onboarding playbook). "complete" records last_synced_at and appends the summary to the running sync log (requires `summary`). "status" reports onboarded state, last sync time, concept counts, staleness, and (with areaList) coverage.
summary	string	Required with "complete": 2–5 sentences on what changed, what you updated, and what you indexed — APPENDED to the product-onboarding-summary concept as a running sync log (never overwritten).
areaList	array	With "start", "status", or "complete": the repo's top-level source areas from your own repo walk (Brainz can't read the repo). Used to compute the coverage map (covered vs uncovered areas) — "complete" is REJECTED if too many areas are still uncovered.
productName	string	With "start": the product's name, echoed into the playbook heading.

take_task

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.

Argument	Type	Description
id	string	Claim this specific task by id. Omit to claim THE next open task (oldest by createdAt then id).
takenBy	string	Label for who's claiming it (agent/orchestrator name). Defaults to a generic label.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "id": {
      "type": "string",
      "description": "Claim this specific task by id. Omit to claim THE next open task (oldest by createdAt then id)."
    },
    "takenBy": {
      "type": "string",
      "description": "Label for who's claiming it (agent/orchestrator name). Defaults to a generic label."
    }
  },
  "additionalProperties": false
}

upsert_concept

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.

destructive

Argument	Type	Description
id	string	Concept id (slug). Omit to derive from title; pass an existing id to update.
body*	string	Markdown body. [[other-id]] wiki-links become graph edges.
tags	array	Tags for filtering.
type	string	Concept type (default "concept"). The 11 built-in types are concept, domain, feature, story, spec, workflow, task, decision, constraint, pattern, glossary; a vault may also define custom types. An unknown type falls back to "concept".
title*	string	Human-readable title (required, non-empty).
doneAt	string	For tasks: ISO timestamp when completed.
status	string	Lifecycle status (default "active").

vault_stats

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.

read-only

No arguments.

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

Input schema (JSON)

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "title",
    "body"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Concept id (slug). Omit to derive from title; pass an existing id to update."
    },
    "body": {
      "type": "string",
      "description": "Markdown body. [[other-id]] wiki-links become graph edges."
    },
    "tags": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Tags for filtering."
    },
    "type": {
      "type": "string",
      "description": "Concept type (default \"concept\"). The 11 built-in types are concept, domain, feature, story, spec, workflow, task, decision, constraint, pattern, glossary; a vault may also define custom types. An unknown type falls back to \"concept\"."
    },
    "title": {
      "type": "string",
      "description": "Human-readable title (required, non-empty)."
    },
    "doneAt": {
      "type": "string",
      "description": "For tasks: ISO timestamp when completed."
    },
    "status": {
      "enum": [
        "active",
        "draft",
        "deprecated"
      ],
      "type": "string",
      "description": "Lifecycle status (default \"active\")."
    },
    "product": {
      "type": "string",
      "description": "Product grouping key."
    },
    "takenAt": {
      "type": "string",
      "description": "For tasks: ISO timestamp when claimed."
    },
    "takenBy": {
      "type": "string",
      "description": "For tasks: label of the agent/orchestrator that claimed it."
    },
    "codeAreas": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Rough codebase paths/globs where this knowledge lives, e.g. [\"packages/core/src/vault.ts\", \"apps/web/src/routes/**\"] — lets agents briefed by get_context know where to apply it."
    },
    "relations": {
      "type": "object",
      "description": "Typed edges, e.g. {\"depends_on\": [\"auth-system\"]}. Conventions: part_of (feature/story/task → domain), realized_by (story → features), realizes (task → stories/features), governs (spec → what it constrains), governed_by (task → specs), depends_on, constrains, supersedes, related_to. For domain concepts, prefer linking to OTHER domains (related_to / depends_on) wherever they share a boundary or hand off responsibility — connected domains reveal how the product's areas overlap instead of floating as isolated islands.",
      "additionalProperties": {
        "type": "array",
        "items": {
          "type": "string"
        }
      }
    },
    "taskStatus": {
      "enum": [
        "open",
        "taken",
        "done"
      ],
      "type": "string",
      "description": "For type=\"task\" concepts: lifecycle \"open\" | \"taken\" | \"done\" (default \"open\"). Prefer the task tools (create_task / take_task / complete_task) over setting this directly."
    }
  },
  "additionalProperties": false
}