Skip to main content

What It Is

An MCP server for BRIK64 exposes documentation, command contracts, PCD authoring rules and evidence-oriented workflows through the Model Context Protocol tool surface.

What It Is For

  • Let agents discover the current CLI contract and authoring rules without inventing unsupported syntax.
  • Prefer monomer selection, .brik traceability and scoped evidence language.
  • Keep local CLI behavior as the default path for private, offline-first work.

Status

Beta / host-dependent. The public docs define the behavior expected from an MCP integration. Hosted MCP behavior depends on the workspace where it is enabled.

Expected Agent Behavior

  • Read project context before generating PCD.
  • Prefer monomer selection over ad hoc code generation.
  • Preserve .brik traceability.
  • Preview managed agent instructions from the documented skill path or host agent environment before any AGENTS.md write.
  • Treat CLI evidence as operational evidence for the inspected scope. It does not prove that the code is correct.
An MCP server for BRIK64 should expose:
  • current CLI command contract;
  • PCD authoring rules;
  • monomer vocabulary guidance;
  • EVA composition rules;
  • managed-section marker contract;
  • update policy;
  • evidence status vocabulary.

Agent Handoff

Local CLI behavior remains the default path for private, offline-first work.