okwn/canton-mcp
AI-native Canton builder repository for coding agents, app generation recipes, architecture maps, and future MCP tooling.
Platform-specific configuration:
{
"mcpServers": {
"canton-mcp": {
"command": "npx",
"args": [
"-y",
"canton-mcp"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
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.
---
Loading reviews...