BREP_mcp_core 0.3.0

The BREP MCP server core: the Model Context Protocol surface generated from the CAD app's own registries, its sessions, script runner and transports (stdio and streamable HTTP). Embedded in the app behind `brep-app --mcp`; hosted headlessly by BREP_mcp.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

# BREP_mcp_core — shared automation server

Host-independent MCP server library (`brep_mcp_core`, manifest version 0.3.0).
It depends on `BREP_render`, and has no dependency on `BREP_app`. Hosts implement
the protocol in `src/host.rs`: the native app window and the `BREP_mcp` headless
harness use the same tool, session and transport implementation.

The core provides registry-derived tools and schemas, stdio and streamable HTTP,
feature validation, script execution, screenshot processing, and generated docs.
Assembly, PMI, wire-harness and metadata operations are exposed through the app's
command registry. The remote browser host remains planned.

From the repository root:

```sh
python3 BREP-dev-data/testing/run.py -- cargo test --manifest-path BREP_mcp_core/Cargo.toml --locked --release
./build.sh test-mcp
```

The second command also tests the app host and generated registry documents.
This library is publishable; the recorded 2026-09-07 family release predates it.
See the publishing guide (`BREP-dev-data/reference/PUBLISHING.md`) and the
automation build plan (`BREP-dev-data/reference/docs/developer/mcp-automation-build-spec.md`),
both in the private development submodule.