Workspace
This document explains how the repository is organized and how each crate relates to the others.
Repository map
flowchart TD
ROOT[antikythera-mcp-framework]
ROOT --> CORE[antikythera-core]
ROOT --> SDK[antikythera-sdk]
ROOT --> CLI[antikythera-cli]
ROOT --> SESSION[antikythera-session]
ROOT --> LOG[antikythera-log]
ROOT --> TESTS[tests]
ROOT --> SCRIPTS[scripts]
ROOT --> WIT[wit]
ROOT --> DOCS[documentation]
Crate responsibilities
| Path | Role |
|---|---|
antikythera-core/ | Core MCP runtime, agent logic, config loading, providers, and transports |
antikythera-sdk/ | Public API layer for Rust and server-side WASM component bindings, config/session/agent helper modules |
antikythera-cli/ | Native binaries for the current CLI surface |
antikythera-session/ | Session storage, history, and export/import |
antikythera-log/ | Structured logging and subscriptions |
tests/ | Workspace integration tests and scenario coverage |
scripts/ | WIT generation and component build helpers |
wit/ | Generated WIT output |
documentation/ | Focused guides and references |
Workspace dependency shape
flowchart LR
CLI[antikythera-cli] --> CORE[antikythera-core]
CLI --> SDK[antikythera-sdk]
SDK --> CORE
SDK --> SESSION[antikythera-session]
SDK --> LOG[antikythera-log]
CORE --> LOG
TESTS[tests] --> CORE
TESTS --> SDK
TESTS --> SESSION
TESTS --> LOG
SCRIPTS[scripts] --> SDK
SCRIPTS --> WIT[wit output]
Practical reading order
- Start with
antikythera-coreto understand the runtime behavior. - Move to
antikythera-sdkto see the public API and bindings layer. - Check
antikythera-clifor the current command-line surface. - Use
tests/to see how the repository is exercised end-to-end.