> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brik64.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> BRIK64 Model Context Protocol server for agent tooling.

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

## Recommended MCP Resources

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

```text theme={null}
MCP resource used:
BRIK64 command selected:
PCD files changed:
AGENTS.md managed section changed:
Evidence status:
Remaining assumptions:
```

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


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.