Introducing Dreamlit MCP: Build Email Workflows from Claude, Cursor, and Lovable
Your AI agent can now read your data model, draft a Dreamlit email workflow, and hand back a preview URL once it's ready. Here's how the MCP server works.
Andrew Kim
It's time to close the loop. Dreamlit MCP arms your AI agents with end-to-end email workflows: no extra code, no extra infrastructure, all driven from your single source of truth.
Connect Dreamlit MCP to Claude Code, Cursor, Lovable, or any client that speaks Model Context Protocol (MCP), and your agent works directly with the Dreamlit Workflow Agent to build, validate, and preview the workflow.
Last updated: May 5, 2026 Validated against the Dreamlit MCP server reference and the Model Context Protocol specification.
Why we built this
We've been talking about Dreamlit as a database-driven workflow platform for a while. The idea is that your database already knows when to email a user, so you shouldn't have to write API integration code to make it happen. (More on that thinking here.)
Over the last few months, more and more of our users have been building inside AI agents. They're describing what they want in plain English to Claude Code, Cursor, or Lovable, and the agent writes the app. But when it came time to add email, the agent hit a wall. It could read the schema. It could understand the intent. It just had no way to translate that into a real Dreamlit workflow without bouncing the user through a browser.
MCP fixes that. AI agents in Claude Code, Cursor, and Lovable already have everything they need to wire a workflow up: your schema, your app code, your intent expressed in plain English. The thing they were missing was a clean interface into Dreamlit. Now they have one.
What is Dreamlit MCP?
Dreamlit MCP is a remote Model Context Protocol server that connects AI agents in Claude Code, Cursor, Lovable, Bolt, and other compatible clients to the Dreamlit Workflow Agent. Your client agent supplies context from your app code and database schema. The Workflow Agent drafts the email workflow, validates it, and returns a preview URL once it matches your intent.
- Hosted at
https://mcp.dreamlit.ai/mcp. No local install or package to run. - Free to use. MCP tool calls don't add charges to your Dreamlit bill.
- Authorization is scoped to one workspace via OAuth, with workflow and analytics scopes (
workflows:read,workflows:write,workflows:publish,analytics:read). - Works with any client that supports remote MCP over Streamable HTTP.
For background on MCP itself, see the Model Context Protocol documentation.
How does the closed loop work?
Your AI agent already has context from your app, your codebase, and your database schema. Dreamlit MCP exposes the workflow primitives so the agent can iterate on a draft against Dreamlit's validation feedback and only hand you a preview URL once it lines up with your intent.
Most "AI builds your X" tools feel like they're guessing. The agent writes something, you go check, it's wrong, you tell it what's wrong, repeat. Dreamlit MCP closes that loop. The agent can:
- Pull your real table and column names from setup state
- Draft a workflow that matches what you described in plain English
- Inspect it, read Dreamlit's validation feedback, and fix issues itself
- Only return a preview URL once the draft lines up with your intent
You don't bounce between windows trying to translate "users" the table into "users" the email audience. The agent does it. Your database stays the source of truth.
What can you ask your AI agent to do?
Describe the email outcome in plain English and the agent will create or update a Dreamlit workflow draft. Once a draft exists, you can also ask it to send a test email to your own inbox using real data from your database, so you see exactly what your users would receive before publishing.
A few prompts that work today.
Build a trigger-based workflow
Create a workflow for the main project: when a new order row is inserted,
send the customer an order confirmation with the order number, total,
and delivery estimate.
Schedule a recurring digest
Send admins a weekly usage digest every Monday at 9am America/New_York.
Include new signups, active users, and failed payments from the previous week.
Send yourself a test email
Send me a test of the order confirmation workflow with real data.
The agent calls get_status first to find the project, drafts the workflow, and returns a preview URL. You open it in Dreamlit, eyeball it, and either ask for tweaks or move toward publish.
Which AI clients work with Dreamlit MCP?
Dreamlit MCP works with any client that supports remote MCP over Streamable HTTP. Setup guides cover the most common ones:
| Category | Clients |
|---|---|
| Coding agents | Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, OpenClaw, VS Code, Windsurf, Zed |
| App platforms | Lovable, Bolt, Replit, v0 |
Each client has a dedicated quick start in the Dreamlit MCP docs. Pick yours, follow the OAuth flow, and your agent can use the server.
How does authorization work?
OAuth, scoped to one workspace. Your client connects to Dreamlit MCP, Dreamlit opens a browser approval screen, and you grant the scopes the client requests:
| Scope | What it allows |
|---|---|
workflows:read | Inspect setup, list projects, workflows, and brand kits, view drafts and published state |
workflows:write | Create new workflow drafts or edit existing drafts from prompts |
workflows:publish | Validate, publish, schedule broadcasts, or unpublish workflows |
analytics:read | Query notification analytics, recipient engagement, and workflow run data |
Personal access tokens are supported as an alternative and are scoped to a single project. You can revoke either method any time.
Can the agent publish workflows without my approval?
No. Publishing is always a separate confirmation step with a preview link. The agent can prepare a publish payload, but it can't push a workflow live until you explicitly approve. Drafts stay drafts.
This matters because AI clients can be tricked by untrusted prompts. Always review tool calls before approving workflow edits, publishing, or unpublishing.
How do I get started?
Sign up for Dreamlit, connect a database, add the MCP server URL to your AI client, and approve access in your browser. The full sequence:
- Sign up or sign in at dreamlit.ai. The free tier covers 3,000 emails per month.
- Connect a Supabase or Postgres database.
- Add the MCP server URL
https://mcp.dreamlit.ai/mcpto your client. Each setup guide walks through the exact steps for that client. - Approve Dreamlit access in the browser when your client opens the OAuth screen.
- Ask your agent: "Check Dreamlit MCP status and list my projects."
From there you can describe an email outcome in plain English and the agent will build the workflow.
If you run into something weird (an unsupported client, an auth failure, a prompt that confuses the agent), we'd love to hear about it. Drop a note on r/dreamlitai or X.
References
- Dreamlit MCP server reference
- Model Context Protocol overview
- Dreamlit MCP quick start guides by client
Last validated: May 5, 2026
Frequently asked questions
What is Dreamlit MCP?
Dreamlit MCP is a hosted Model Context Protocol server at https://mcp.dreamlit.ai/mcp that lets AI agents in Claude Code, Cursor, Lovable, Bolt, and other compatible clients author Dreamlit email workflows end-to-end. The agent uses context from your app code and database schema to draft workflows, validate them against your project, and return a preview URL once they're ready.
Which AI clients work with Dreamlit MCP?
Setup guides cover Claude Code, Claude Desktop, Codex, Cursor, Gemini CLI, OpenClaw, VS Code, Windsurf, and Zed, plus app platforms like Lovable, Bolt, Replit, and v0. Anything that supports remote MCP over Streamable HTTP should work.
Is Dreamlit MCP free to use?
Yes. Connecting and calling MCP tools doesn't add charges to your Dreamlit bill. The free tier on dreamlit.ai covers 3,000 emails per month, so you can wire up a real workflow end-to-end without a card.
Can the AI agent publish workflows without my approval?
No. Drafts stay drafts until you approve them. Publishing is always a separate confirmation step with a preview link, so the agent can't surprise you with a live workflow.
Do I need to install anything to use Dreamlit MCP?
No. Dreamlit hosts the MCP server. You add the URL https://mcp.dreamlit.ai/mcp to your client, complete OAuth in the browser, and your agent can use Dreamlit's tools.
How does authorization work for Dreamlit MCP?
Dreamlit MCP supports OAuth for clients that handle remote-server authentication. Your client connects, Dreamlit opens a browser approval screen, and you grant access to one workspace with the scopes you choose: workflows:read, workflows:write, workflows:publish, analytics:read. Personal access tokens are also supported and are scoped to a single project.
Can my AI agent send a test email through Dreamlit MCP?
Yes. After your agent creates a workflow draft, you can ask it to send a test email to your own inbox using real data from your database. This lets you preview exactly what your users would receive before publishing the workflow.
About the Author
Co-Founder & CTO
Andrew is CTO and Co-Founder of Dreamlit AI. After building integrations at Netflix and leading engineering at fintech startup Bonside, he's now building the notification platform he wished he'd had all along. Full bio →
Other articles
Thinking in Database-Driven Notifications
What are database-driven notifications and how do they matter?
A New Way to Manage Transactional Emails
Reimagine how you send transactional emails. No more cron jobs, no more webhooks, no more API calls!