Br8n MCP server

Read from the package source without running it. The installed server may list more.

• br8n_activity

  Query your cross-repo ACTIVITY graph — what you've been working on.

• br8n_build_graph

  Build/refresh the KB's knowledge graph from its findings. An LLM extracts entities + relationships, which are deduped and written to kg_nodes/kg_edges. ``rebuild=True`` (default) clears the existing graph first (clean rebuild). ``use_schema=True`` steers extraction with the KB's approved intent schema if one was set via ``br8n_set_kg_schema``; with none set it builds free-form. Returns ``{findings

• br8n_capture

  Persist a workspace snapshot as a Finding. Creates the project/KB on demand.

• br8n_distill

  (Re)build the curated .br8n/docs/ tree from the KB's session notes. `force=True` distills now and returns {distilled, doc_count, folders}; otherwise it just nudges the debounced background distiller. Used by /br8n:docs --rebuild.

• br8n_explorewrite action

  Run the gap-fill explore pipeline (plan→search→crawl→extract→merge).

• br8n_get_kg_schema

  Both ontologies for the KB: ``intent`` (the user-approved target schema set via ``br8n_set_kg_schema``, or null) and ``emergent`` (the node/relation types actually present in the built graph, with totals). Compare to see drift.

• br8n_graph

  Read the KB's knowledge graph: the full graph (capped) or a depth-bounded subgraph around nodes whose label matches ``focus``. Returns nodes/edges + counts. Empty until ``br8n_build_graph`` has run.

• br8n_journalwrite action

  Write a personal JOURNAL entry — cross-project, searchable any time.

• br8n_journal_recent

  List your most recent journal entries, newest first (no query).

• br8n_journal_search

  Search your journal (and optionally your project notes) by meaning.

• br8n_kb_exists

  Cheap first-run guard: does a br8n KB exist for this project/kb?

• br8n_kg_stats

  KG metrics: node/edge totals plus counts by node type and by relation.

• br8n_mark_drift_offered

  Stamp that a schema-drift offer was surfaced for the KB, at ``residual`` count.

• br8n_mark_init_offered

  Stamp the KB with the time the KG schema wizard was offered.

• br8n_note

  Persist a session note: a `note` Finding (searchable, feeds resume) AND a markdown file under .br8n/notes/<kb>/. Then schedules a debounced re-distill of the curated doc tree. Called by the Stop hook at session end. `content` should be rendered per the KB's note policy (br8n_notes_policy_get). next_action: the single ~two-minute step future-you should do first (one line). Returns {finding_id, note

• br8n_notes_policy_get

  Read the per-KB note-taking policy (section template + free-text steer) from .br8n/notes-policy.json. Returns {policy: {sections, steer}, project, kb}. Returns the default policy if none is set yet.

• br8n_notes_policy_set

  Persist the per-KB note-taking policy. `policy` = {sections: [{name, enabled}], steer: str}. Validates before writing; on a bad shape returns {ok: False, errors}. On success returns {ok: True, policy, project, kb}. Used by /br8n:notes.

• br8n_projects

  List every repo+branch you've captured to, most-recent first.

• br8n_propose_kg_schema

  STEP 1 of KG-intent co-design. Mine the KB's findings and propose a draft target ontology: ``node_types``, ``relation_types``, ``relation_validity``, and ``competency_questions``. Persists nothing — review with the user, then approve with ``br8n_set_kg_schema``. If the KB has no findings the draft is a generic default plus a ``note``.

• br8n_resume

  Tap the session KB and return the 30-second resume card.

• br8n_schema_drift

  Should br8n offer to (re)design this KB's KG schema right now?

• br8n_set_kg_schema

  STEP 2 of KG-intent co-design. Validate and persist the user-approved KG schema dict (as returned by ``br8n_propose_kg_schema``, edited as the user wishes) as a new version. Returns ``{ok: true, schema}`` on success, or ``{ok: false, errors}`` if the schema is malformed (nothing is saved). The next ``br8n_build_graph(use_schema=True)`` builds against it.

• br8n_timeline

  (Re)build the append-only activity timeline at .br8n/timeline/ from this repo+branch's notes + captures + journal. `force=True` runs a pass now and returns {forced, appended, recent_days, week_days, *_path}; otherwise it nudges the debounced background rollup. Used by /br8n:timeline --rebuild.

• Code scan76 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 59 days ago12/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Safety score

88/100

higher than 75% of 1,119 Developer tools servers

Tools

23

the typical Developer tools server has 7

Tools that change things

9%

typical: 5%. Fewer write tools means less an agent can break

GitHub stars

1

more than 50% of 855 Developer tools servers

Br8n: common questions

Is Br8n MCP server safe?

Yes, by our scan: it is graded A (88/100). Read the Br8n safety report

How do I install Br8n?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Br8n need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Br8n maintained?

The last commit was 99 days ago (2026-07-28). The latest release is v1.1.2.

What can I use instead of Br8n?

Servers from other publishers that do the same job: Repowise MCP server, Git MCP server and Gitwand MCP server.

How does Br8n compare with other Developer tools MCP servers?

safety score 88/100 (higher than 75% of 1,119 Developer tools servers); tools 23 (the typical Developer tools server has 7); tools that change things 9% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.