docs: mcp is a frontend consuming smith-ui
ab7c0553b54d6f0f5ed621b7cc21c8c067dc95ca
Oliver Jan Krylow <oliver@bugabinga.net> · 2026-09-25 17:09 UTC
unsigned 1 parent
repositories / smith
smith
There are many coding harnesses - but this one is fast
owned by admin
Changed files (1)
TO_DISCUSS.md
ready@@ -18,7 +18,7 @@
- smith-web: SSE skeleton first (std-only possible), websocket when live input and multi-viewer arrive — websocket forces the async runtime decision. Sequence: formalize smith-rpc as first smith-ui consumer, then smith-web.
- Fleet / remote effects: p2p multiplexing of machines, tools, plugin instances across smith peers. Layer: beside the effect layer, not smith-ui. Trust tier for fleet peers is the spec-worthy core. Candidate transport: iroh. Trigger: multi-machine usage hurts.
-- smith-mcp: smith AS MCP server for other harnesses — protocol adapter mode like rpc (inbound serving is host-level networking, not plugin territory). Trigger: external-harness integration wanted.
+- smith-mcp: MCP is a UI for agents and humans; smith-as-MCP-server consumes smith-ui so plugin features translate naturally into MCP (progress notifications, resources, tools). Frontend, not adapter mode. Trigger: external-harness integration wanted.
## Rethinks