---
summary: "Initial scaffold from @cyanheads/mcp-ts-core with complete MCP surface design — 19 tools and 6 resources for BrAPI v2.1 find/get, pedigree traversal, writes, filter discovery, and dataset lifecycle."
breaking: false
---

# 0.1.0 — 2026-04-23

Initial scaffold and design for a TypeScript MCP server exposing BrAPI v2.1 to LLMs as a goal-oriented plant-breeding workbench. Implementation lands in subsequent releases.

## Added

- Project scaffold from `@cyanheads/mcp-ts-core` — skills, TypeScript config, Biome, Vitest, devcheck, Dockerfile, agent protocol files, changelog structure.
- Design doc at [`docs/design.md`](docs/design.md) covering:
  - 19-tool MCP surface organized by axis — orient (`connect`, `server_info`, `describe_filters`), retrieve (`find_*`/`get_*`, `walk_pedigree`), orchestrate (`submit_observations`, `manage_dataset`), and escape hatches (`raw_get`, `raw_search`).
  - 6 resources (server info, study, germplasm, dataset, calls, filters) — tool-only clients lose nothing (primary entities have paired `get_*` tools; reference data via `find_*`; niche lookups via `raw_get`).
  - 2 prompt templates — EDA framework for a single study, meta-analysis across germplasm + trait.
  - Service layer: `BrapiClient`, `CapabilityRegistry`, `ReferenceDataCache`, `DatasetStore`, `OntologyResolver`, `ServerRegistry`.
  - Workflow analysis (server_info, find_studies, walk_pedigree, submit_observations), response companions (orient-combine, filter distributions, traversal stats, post-action state), design decisions, known limitations, and a compatibility matrix adapted from [Plant-Phenomics-Lab/Breedbase-Client](https://github.com/Plant-Phenomics-Lab/Breedbase-Client).
- Echo tool/resource/prompt starter definitions from the framework (placeholder — replaced during implementation).
