Skip to main content
MCP integration lets agents discover BRIK64 documentation, command contracts, PCD authoring rules and evidence-oriented workflows through a structured tool surface. The public docs define the behavior expected from an MCP integration.

​
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 public skills repository or host agent environment before any AGENTS.md write.
  • Treat CLI evidence as operational evidence for the inspected scope.
An MCP server for BRIK64 should expose:
  • current CLI command contract;
  • PCD authoring rules;
  • monomer catalog;
  • EVA composition rules;
  • managed-section marker contract;
  • update policy;
  • evidence status vocabulary.

​
Agent Handoff

MCP resource used:
BRIK64 command selected:
PCD files changed:
AGENTS.md managed section changed:
Evidence status:
Remaining assumptions:
Hosted MCP behavior depends on the workspace where it is enabled. Local CLI behavior remains the default path for private, offline-first work.