Memory
Operator discovery (2026-10-08): Activepieces MCP server — model architects flows, fetches emails, builds input forms, chat-with-agent-behind-tools; deterministic workflows + preconfigured pieces that Claude/ChatGPT use well. Operator plans self-hosting. DECISION SHAPE (operator's, recorded as direction): do NOT expose Activepieces raw — build own wrapper layer of SELECTED tools combined with own tools. Connections: Activepieces-complementary (not Flow-replacing) already decided in workspace-decisions; this makes Activepieces the conductor surface behind the wrapper. Open design points noted (not ruled): piece curation criteria, credential scoping per piece/account/purpose, compose-time vs run-time approval, wrapper as the single MCP surface unifying Activepieces pieces + own verdict tools (+ Flow boards?).
Tags: activepieces, mcp, wrapper, orchestration, project:redaction-kernel, kind:episodic, status:canonical — Source: mcp — 2026-10-08 13:49:34 UTC