- List my published workflows in Dreamlit.
- Use what you’ve learned about my brand voice from past workflows, and draft a “your free trial is ending” email that matches.
- Create a recurring email that sends me a weekly usage digest every Monday at 9 AM America/New_York. Include new signups, active users, and failed payments from the previous week.
- Send me a test of the welcome email draft so I can review it in my inbox before publishing.
- Publish the “trial ending” reminder workflow. Check for any warnings or errors before publishing.
Why use Dreamlit MCP with Hermes?
Hermes is a personal agent that builds memory across sessions and learns procedural skills you can reuse. Dreamlit MCP turns those into notification workflows that improve over time, drafted by an agent that already knows how you write.- Memory-aware drafting: Hermes remembers the brand voice, sequence patterns, and tone choices from past workflows you’ve shipped together.
- Reusable skills: the procedure for “draft a transactional email and run a test before publishing” becomes a skill Hermes can repeat without re-explanation.
- Multi-channel access: trigger the same workflow draft from Telegram, Discord, Signal, Email, CLI, or any channel Hermes is connected to.
- Scheduled reviews: ask Hermes to check workflow runs every Monday and summarize anything that needs attention.
Server URL
~/.hermes/config.yaml under mcp_servers.
Quick install
1
Confirm MCP support
MCP support is included when you install Hermes with the standard installer. If your install does not include MCP extras, run:
2
Add Dreamlit to Hermes
Open
~/.hermes/config.yaml and add Dreamlit under mcp_servers:3
Authorize Dreamlit
Start Hermes:On first connect, Hermes should open a browser authorization flow. Sign in to Dreamlit, choose the workspace, and approve access.
4
Reload MCP servers
If Hermes was already running when you edited the config, reload MCP servers:You can also restart Hermes to refresh the active tool list.
5
Start prompting
Ask Hermes:
Using an API key instead of OAuth?
Using an API key instead of OAuth?
Use a Dreamlit personal access token if your Hermes environment cannot complete OAuth or if you want one project-scoped credential.
1
Create a token
Open Dreamlit, go to Project Settings -> Project Details -> MCP Access, then click Create token.
2
Choose scopes
Select the smallest set of permissions Hermes needs.
3
Copy the token now
Dreamlit only shows the token once. Store it securely.
4
Pass the token as a Bearer token
Configure Hermes to send the token in
~/.hermes/config.yaml:Hermes can filter tools per MCP server. If Dreamlit tools do not appear, check that the
dreamlit server is enabled and that your tools policy is not excluding Dreamlit tools.What is MCP?
MCP is an open standard that lets connect to external tools and data sources through one shared protocol. Instead of needing a custom Dreamlit integration, connects to Dreamlit’s MCP server and discovers the tools Dreamlit exposes. For Dreamlit, MCP means can work with notification workflows using product-level actions:- Find the right workspace, project, or workflow
- Understand Dreamlit concepts and project setup state
- Create or update workflow drafts from plain-English prompts
- Return preview links so you can inspect the result in Dreamlit
- Prepare publishing and ask for explicit confirmation before anything goes live
What can Dreamlit MCP do?
Dreamlit MCP is focused on workflow authoring and safe workflow operations. It is not a low-level database API.Prerequisites
Before connecting :- Create a Dreamlit account at app.dreamlit.ai.
- Finish workspace and project setup in Dreamlit.
- Connect a Supabase or Postgres database.
- Configure any channels the workflows will need, such as email domains, Brand Styles, or Slack.
- Confirm supports remote MCP over Streamable HTTP, or can send MCP requests through an HTTP bridge.
Dreamlit MCP works against existing Dreamlit workspaces and projects. If says setup is required, open the Dreamlit link it returns and finish setup in the web app before reconnecting.
How does authorization work?
OAuth is the best option when supports remote server authentication. connects to Dreamlit, Dreamlit opens a browser authorization screen, and you approve access to one Dreamlit workspace.1
Add Dreamlit MCP
Use the server URL:
2
Approve Dreamlit access
should open a Dreamlit authorization page. Sign in, choose the workspace, review the requested scopes, and click Allow access.
3
Check status
Ask :
Check Dreamlit MCP status and list my projects.
Permissions
Dreamlit MCP uses workflow and analytics scopes.
OAuth grants are scoped to a workspace. Personal access tokens are scoped to one project.
Tools
discovers these tools from the server.
Dreamlit also exposes the
dreamlit://mcp/guide resource. If supports MCP resources, it can read the guide for prompting guidance, trigger types, unsubscribe guidance, and the recommended Dreamlit MCP flow.
Recommended workflow
Ask to work in this order:1
Check status
Start with
get_status. This gives Dreamlit concepts, setup state, project context, and links back to relevant Dreamlit pages.2
Find the target
Use
list_projects and list_workflows if the project or workflow is unclear.3
Choose a Brand Style
Use
list_brand_styles when you want a specific saved Brand Style applied.4
Inspect before editing
Use
get_workflow_and_preview_url before changing an existing workflow.5
Create or update the draft
Use
create_or_update_workflow with an outcome-oriented prompt.6
Review in Dreamlit
Open the returned workflow URL to inspect the draft, preview output, and make manual adjustments if needed.
7
Test important messages
For email or Slack messages that need to look right before going live, ask to send a test through
send_workflow_test. Confirm the test before it sends, then review the real message in your inbox or Slack channel.8
Publish deliberately
Use
prepare_publish first. Only call confirm_publish after you explicitly approve the prepared publish request.How do I test a draft email or Slack message before publishing?
Usesend_workflow_test to send the current draft message to yourself (or a chosen recipient) so you can review it in the real channel before going live. Tests don’t publish, schedule, or change the workflow draft.
- Email tests default to the authenticated user’s email address. Pass
testRecipientEmailto send to a different inbox. - Slack tests post to the channel configured for the draft message.
- Dreamlit returns a
confirmation_requiredresponse describing the message and recipient. only sends after callingsend_workflow_testagain withconfirmSend: true. - If a workflow has more than one testable message, Dreamlit returns a
clarification_requiredresponse listing each message by label so you can choose one. - Test sends count toward the same draft rate limit as workflow authoring.
Prompting Dreamlit through MCP
Dreamlit works best when you describe the notification outcome, not the internal workflow graph. Good prompts include:- The event or schedule that should start the workflow
- The audience or recipient
- The message goal
- Data needed for targeting or personalization
- Timing, timezone, and business rules
- Whether unsubscribe should be enabled
- Tone or brand notes when they matter
Safety and control
Dreamlit MCP is designed so can help with workflows without making surprise production changes.- Draft changes stay draft-only until you publish.
- Test sends require explicit confirmation and don’t publish, schedule, or edit the draft.
- Publishing is always a separate confirmation step with a Dreamlit preview link.
- If an action needs setup or manual review, Dreamlit sends you back to the web app.
- Query steps are read-only against your application data.
- Access is limited by the permissions you approve. Personal access tokens are project-scoped and can be revoked anytime.
Troubleshooting
Dreamlit authorization is required
Reconnect the MCP server and complete the browser authorization flow. If you are using a personal access token, confirm the token is still active and that is sending it as anAuthorization: Bearer ... header.
Dreamlit tools do not appear after authorization
Start a new chat or session in . If the tools still do not appear, restart or restart the Dreamlit MCP server entry. can cache the MCP server and tool list for an open session.Additional Dreamlit permission is required
The current OAuth grant or personal access token does not include the required scope. Reconnect with the requested access, or create a token with the missing scope.Dreamlit says to choose a project
Your approved workspace has multiple projects and did not specify one. Ask to calllist_projects, then retry with the right project.
Dreamlit says setup is required
Open the returned Dreamlit setup URL, finish workspace and project setup, then reconnect .A workflow edit returns a browser handoff
Some changes still need the Dreamlit web app. Open the returned URL, review the draft, and continue from there.Publishing fails after a preview
The workflow may have changed since the publish preview. Ask to runprepare_publish again, review the new preview and warnings, then confirm only if it still looks right.
Tools are visible but calls time out
Workflow authoring can take longer than read-only calls because Dreamlit is planning and applying a real workflow draft. Retry once. If it keeps failing, open the returned Dreamlit URL if one is present, or contact support.Testing with MCP Inspector
You can use the MCP Inspector to verify the server connection.1
Start the Inspector
2
Choose Streamable HTTP
Select Streamable HTTP as the transport.
3
Enter the server URL
4
Authenticate
Use OAuth if the Inspector supports it, or add a Bearer header:
5
Confirm the connection
Use List tools and call
get_status to confirm the connection.Next steps
Quickstart
Connect your database and create your first workflow.
Workflow basics
Learn how Dreamlit workflows are structured.
Get support
Reach the team if MCP setup blocks you.
Last validated: 2026-05-07