118 MCP Tools, 4 Safety Levels: Building a Server-Enforced Form Ops Layer
When people hear that a product works from Claude, ChatGPT, Cursor, and other AI clients, the default assumption is: "So you added chat to your dashboard." That is not the architecture. FORMLOVA is...

Source: DEV Community
When people hear that a product works from Claude, ChatGPT, Cursor, and other AI clients, the default assumption is: "So you added chat to your dashboard." That is not the architecture. FORMLOVA is a chat-first form service where MCP is the primary operational interface -- 118 tools across 24 categories, covering everything from form creation to response analytics to email campaigns. The dashboard exists for dense visual inspection. Chat leads for intent-to-action sequences. The interesting engineering problem is not "how do you expose tools over MCP." It is: how do you make conversation safe enough to carry real operations -- publishing live forms, sending bulk emails, deleting data -- when the LLM between you and the server will routinely ignore your instructions? The Problem With Prompts: LLMs Skip Steps Here is something I learned building this system: LLMs ignore or skip prompt instructions. You can write "ALWAYS confirm before sending email" in your system prompt. Models will ski