MCP is turning no-code builders into the back end for AI assistants
When Claude or ChatGPT can build your portal, the editor matters less — the data model, permissions and automations matter more.
For years, no-code builders competed on how easy their editors were to use: drag-and-drop blocks, nice templates, simple data connectors. In 2026 a new question matters just as much: how easily can an AI assistant use it?
The protocol answering that question is MCP, the Model Context Protocol, an open standard that lets assistants such as Claude and ChatGPT connect to outside tools and data.
What changed this month
In early September, Softr ran an "MCP Launch Week" and shipped three things:
- An MCP server that exposes its databases, apps, custom code blocks, integrations and workflows to AI assistants.
- Vibe coding through MCP: describe a dashboard or calculator in Claude or ChatGPT, and it's built as a live block connected to your data.
- Workflow MCP: build, test and publish automations from a chat.
Around the same time, Microsoft made its prompt-to-app builder generally available in Power Apps. There, the AI lives inside Microsoft's own tool rather than in an outside assistant, but the direction is the same: describe the outcome, let AI do the assembly.
Why MCP matters for no-code
Think of a no-code platform as three layers:
| Layer | What it does | Who operated it before | Who can operate it now |
|---|---|---|---|
| Interface | Pages, forms, portals | Builders in the editor | Builders or AI assistants |
| Data | Tables, records, permissions | Builders and app users | Also AI assistants, with scoped access |
| Automation | Workflows and triggers | Builders | Also AI assistants |
With MCP, every layer can be driven from a conversation. The no-code platform starts to act as the back end for work that begins in an AI chat. It holds the data, enforces the permissions and runs the automations.
What builders should watch
- Permissions come first. Softr splits MCP access into separate levels for apps, databases and workflows. Start with read-only, then grant edit or full access only where you need it.
- Credits and cost. Softr says vibe coding through your own assistant doesn't use Softr AI credits, because the AI work runs in the assistant you already pay for. Expect pricing models across the industry to adjust around this.
- Review before you publish. An assistant can publish an app or change a table in seconds. Keep a staging app or version history so changes can be reviewed.
- Lock-in shifts. If your team builds mostly through chat, the platform's data model and permission system matter more than its editor.
The bigger picture
This connects to the broader shift toward agents doing the work. No-code platforms that expose clean, well-permissioned MCP servers are setting themselves up as the system AI assistants build on and run through. Those that don't may end up as just another editor people forget to open.
Try it yourself: How to connect Claude or ChatGPT to Softr with MCP.
The Appboxs newsroom covers launches, funding, acquisitions, pricing changes and AI across the SaaS and no-code world. Every story links to its primary sources. Have a tip, a correction or a story we should cover? Send it through our contact page.
Related stories
Softr opens its no-code platform to Claude and ChatGPT with an MCP server
Newsroom · 8 Sept 2026 · 2 min readAsana buys no-code agent builder StackAI for $75M
Newsroom · 28 May 2026 · 1 min read