Agent-readable builder base for Canton Network applications. Doc-first. Not runnable. Use to generate apps.
canton-mcp is a builder base: structured knowledge, generation recipes, maps, and templates that guide creation of Canton-based applications. It does not ship a runnable app. It provides the patterns and steps to generate one.
Primary consumers: Coding agents (Cursor, Claude Code, Copilot) and developers using AI-assisted workflows.
Disclaimer: canton-mcp is a builder base, not a runnable application. It provides guidance, recipes, and templates. No MCP server, generation scripts, or validation runners are implemented. Coding agents must follow recipes manually. Generated apps use mocks (MockWalletAdapter, InMemoryPartyIdentityStore) unless you apply additional recipes (replace-mocks, sql-persistence, real-ledger). Full recipe execution assumes access to canton-mvp as source.
| Aspect | canton-mvp | canton-mcp |
|---|---|---|
| Role | Builder foundation (runnable starter kit) | Builder base (agent-readable generation layer) |
| Structure | Code-first monorepo | Doc-first: maps, recipes, templates |
| Consumption | Clone → run → extend | Clone → read → generate |
| Output | Working app you fork | Generated app in target directory |
| Primary consumer | Human developers | Coding agents + developers |
canton-mcp uses canton-mvp as source. It reads, references, and selectively copies per docs/source-strategy.md. It does not replace or modify canton-mvp.
See docs/repository-positioning.md.
- Coding agents generating Canton apps from natural language requests
- Developers using AI tools to scaffold wallet, token, or swap applications
- Teams adopting Canton who need structured guidance and copy rules
- Contributors extending the generation recipes or maps
Not for: Running an app directly. Use canton-mvp for that.
- Read AGENTS.md — navigation, rules, core truth
- Scan llms.txt — dense quickstart
- For app generation: APP_GENERATION_GUIDE.md → decision tree → recipe(s)
- Before editing: SAFE_EDIT_BOUNDARIES.md
Entry points:
| Need | File |
|---|---|
| Generate app | APP_GENERATION_GUIDE.md |
| Recipe index | TASK_RECIPES.md |
| File lookup | MODULE_INDEX.md |
| Edit rules | SAFE_EDIT_BOUNDARIES.md |
| Add content | EXTENSION_POINTS.md |
| Area | Status |
|---|---|
| Maps | canton-components, canton-builder-paths, wallet-token-swap-paths, digital-asset-stack, concept-map, ecosystem-gap-fill-index |
| Generation recipes | generate-minimal-api, wallet-app, token-app, swap-app, onboarding-admin-app, internal-prototype, replace-mocks, sql-persistence, real-ledger, ecosystem-orientation |
| Templates | app-shell, api-module, wallet-module, token-module, swap-module, onboarding-module, admin-module, persistence-adapter, auth-adapter, docs-pack, repo-pack |
| Extracted patterns | package-map, flow-map, docs-map, examples-map (adapted from canton-mvp with provenance) |
| Agent tasking | task-types, agent-workflows, change-strategy, validation-strategy, task-execution-plans |
| Schemas | task-schema, module-schema, recipe-schema |
| Ecosystem supplements | wallet, ledger, Daml, validator/scan, token, onboarding (gap-fill docs) |
| Future MCP tools | Design only: docs/future-mcp-tools.md, maps/mcp-tool-map.md, tools/future-tool-catalog.md |
Not implemented: MCP server, runtime tools, live ledger/wallet integration. canton-mcp is read-only guidance.
| Item | Status |
|---|---|
| MCP server | Design in docs/future-mcp-tools.md; no implementation |
| Tool schemas (JSON) | schemas/ reserved; no runtime |
| Generation scripts | tools/ has tasking docs; no automation yet |
| Validation scripts | Strategy documented; no runner |
See ROADMAP.md and docs/future-mcp-phase.md.
Readiness assessment: AgentBuilderReadinessReport.md
canton-mcp/
├── docs/ # Plans, strategies, ecosystem, terminology
├── maps/ # Component maps, builder paths, tool map
├── recipes/ # Generation recipes (step-by-step)
├── templates/ # Code scaffolds (.skel, skeletons)
├── extracted/ # Adapted patterns from canton-mvp (provenance required)
├── tools/ # Tasking system, future tool catalog
├── schemas/ # Task, module, recipe schemas
├── reports/ # Audits, gap-fill
└── examples/ # Reference structures
| Doc | Purpose |
|---|---|
| docs/terminology.md | Consistent terms |
| docs/source-strategy.md | Copy vs reference vs reimplement |
| docs/repository-positioning.md | canton-mvp vs canton-mcp |
| docs/canton-ecosystem-map.md | Canton ecosystem |
| docs/future-mcp-phase.md | Planned MCP phases |
| docs/future-mcp-tools.md | Future MCP tool design |
| ROADMAP.md | Planned work |
| CONTRIBUTING.md | How to contribute |
| RELEASE_NOTES_DRAFT.md | Draft release scope |
- Use canton-mcp as reference when building with AI.
- Follow generation recipes to produce new apps.
- Copy or adapt from canton-mvp per docs/source-strategy.md.
- Extend recipes via EXTENSION_POINTS.md.
See CONTRIBUTING.md.
Apache-2.0