Dreamlit MCP server
ai.dreamlit/mcpdreamlit.aistreamable-httpv0.1.0Scanned
Create, test, publish, and manage Dreamlit notification workflows from AI clients.
16 tools: 2 can delete or cancel things, 2 do something that can't be undone, 6 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 3
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 2 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Dreamlit MCP server can do
The Dreamlit MCP server is published by dreamlit.ai, a domain the MCP Registry verified. It has 16 tools. It can delete or cancel things (2 tools: confirm_publish and unpublish_workflow), do things that cannot be undone, such as sending, paying or publishing (send_workflow_test and prepare_publish) and create or change data (6 tools: create_or_update_workflow, edit_workflow_steps, rename_workflow, move_workflow_to_folder and 2 more). 6 tools only read.
2 tools bring in text other people can write (create_or_update_workflow and get_workflow_and_preview_url); 3 tools can send data out of your system (send_workflow_test, prepare_publish and confirm_publish).
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 0.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
16 tools
Deletes or cancels 2Claude Code: deny
confirm_publishUse only after explicit user confirmation and a prior prepare_publish result to publish or schedule a Dreamlit workflow.Can send data outNo findings
Why it is in this group
- The name "confirm_publish" says "publish": a word for a change that another call does not undo.
- The server marks it destructive (destructiveHint: true).
What it can reach
- outboundThe name "confirm_publish" says "publish": it sends or publishes something to other people.
Description, as the server wrote it Use only after explicit user confirmation and a prior prepare_publish result to publish or schedule a Dreamlit workflow. Side effect: installs live database/repeating/auth triggers, schedules or sends broadcasts, and may enable notification delivery; sandbox mode can hold notifications for inspection. Returns the published workflow status and app URLs. Do not call speculatively or without carrying forward the prepare_publish safety fields.
Annotations the server declares
- title: Confirm publish
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
unpublish_workflowUse after explicit user intent to unpublish a Dreamlit workflow.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Use after explicit user intent to unpublish a Dreamlit workflow. Side effect: disables live triggers or schedules so no new runs start. Runs already in progress keep sending unless inProgressRuns is "stop". If the workflow has in-progress runs and inProgressRuns is omitted, returns clarification_required with the count and changes nothing: ask the user whether to stop those runs or let them finish, then call again with their choice. Returns updated workflow status, stopped run counts (allRunsStopped, remainingRunCount), and app URLs. If some runs could not be stopped, ask the user, then call again with inProgressRuns "stop": on an already-unpublished workflow it only stops the runs still in progress. Do not use for deleting drafts, canceling one broadcast run, or editing workflow content.
Annotations the server declares
- title: Unpublish workflow
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Can't be undone 2Claude Code: ask
prepare_publishRead-only validation step before publishing.Can send data out1 finding
Why it is in this group
- The name "prepare_publish" says "publish": a word for a change that another call does not undo.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe name "prepare_publish" says "publish": it sends or publishes something to other people.
Findings
- Warn
The server marks "prepare_publish" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "prepare_publish" says "publish": a word for a change that another call does not undo.
Description, as the server wrote it Read-only validation step before publishing. Use after the user asks to publish and after inspecting the workflow if needed. Returns validation status, publish mode, preview URL, and a confirmation payload with version/timestamp safety checks for confirm_publish. Does not publish or schedule anything by itself.
Annotations the server declares
- title: Prepare publish
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
send_workflow_testSide effect when confirmSend is true: sends one current draft email or Slack message for review, but does not publish, schedule, or edit the workflow.Can send data outNo findings
Why it is in this group
- The name "send_workflow_test" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "send_workflow_test" says "send": it sends or publishes something to other people.
Description, as the server wrote it Side effect when confirmSend is true: sends one current draft email or Slack message for review, but does not publish, schedule, or edit the workflow. Use after authoring or inspection when the user wants to verify an important message before publishing. Returns sent-test details, app URLs, a confirmation request, or a clarification request with user-facing message choices. If the test has no data because row level security hides a source table's rows from Dreamlit, returns error code table_rows_hidden_by_rls with unreadableTables[].fixSql to run, or ask the user to run, in the Supabase SQL editor. Do not expose test target ids as copy; ask users to choose by message label and confirm before sending.
Annotations the server declares
- title: Send workflow test
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 6Claude Code: ask
create_or_update_workflowCreates a new Dreamlit workflow draft or updates an existing draft from an outcome-oriented natural-language prompt.Reads text others writeNo findings
Why it is in this group
- The name "create_or_update_workflow" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Creates a new Dreamlit workflow draft or updates an existing draft from an outcome-oriented natural-language prompt. Use after get_status; use get_workflow_and_preview_url first when editing an existing workflow, then describe the steps to change by what they do, not by step id. Each call continues the workflow's current chat; pass startNewChat to start fresh. Broadcasts that are scheduled, sent, or cancelled can't be edited; duplicate them in the Dreamlit web app instead. Existing Supabase Auth workflows can be edited except for the immutable trigger step; creating Supabase Auth workflows must happen through Supabase Auth email setup in the Dreamlit web app. Side effect: may create or modify a draft, but does not publish or install live triggers. Returns the workflow/draft result, action-required or handoff details when more input is needed, and relevant app URLs. Do not use for publishing, direct database changes, or low-level graph edits.
Annotations the server declares
- title: Create or update workflow
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
edit_workflow_stepsApplies up to 5 exact edits to existing steps in a workflow draft, instantly and without AI: email subject, preview text, HTML, sender, reply-to, and recipient; Slack message; quer…No findings
Why it is in this group
- The name "edit_workflow_steps" says "edit": a word for a change.
Description, as the server wrote it Applies up to 5 exact edits to existing steps in a workflow draft, instantly and without AI: email subject, preview text, HTML, sender, reply-to, and recipient; Slack message; query SQL; wait rule; and step description. Use when you know the exact new value; call get_workflow_and_preview_url first for step ids and current values, with includeEmailHtml to edit HTML. Edits are checked against the draft as it will be once they are all saved: templates and waits may only use fields their step gets, and query edits are rejected if later steps still use fields the new query no longer returns. Each edit applies on its own, except that a SQL edit and the edits below it apply together or not at all. The edits show in the workflow's Dreamlit chat. Side effect: changes the draft only; does not publish. Returns each edit's status with an error code and message for failed edits, and app URLs. Do not use to add, remove, or move steps, edit triggers, or make changes that need writing or judgment; use create_or_update_workflow for those.
Annotations the server declares
- title: Edit workflow steps
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
get_lifecycle_reportSide effect: creates a preparation request when no report is ready or refresh is true and the latest report became ready more than 24 hours ago; repeat calls reuse an open request.1 finding
Why it is in this group
- The name "get_lifecycle_report" says "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "get_lifecycle_report" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_lifecycle_report" says "get": a word for reading.
Description, as the server wrote it Side effect: creates a preparation request when no report is ready or refresh is true and the latest report became ready more than 24 hours ago; repeat calls reuse an open request. Pass refresh: true only when the user asks for a new report; when checking on a pending report, call without refresh. Use for Dreamlit's prepared lifecycle analysis: key metrics worth tracking, the signup-to-paid funnel and where users drop off, deliverability health, and which stages (welcome, onboarding, engagement, retention, winback) have no emails yet. Available on Pro and Scale plans only. Reports are prepared by Dreamlit's agents and reviewed by our team. Returns a ready report or a processing state while Dreamlit prepares it; check back later. The requester is also emailed when ready. Does not return raw notification analytics; use get_analytics for that.
Annotations the server declares
- title: Get lifecycle report
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
get_recommendationsSide effect: creates a preparation request when no report is ready or refresh is true and the latest report became ready more than 24 hours ago; repeat calls reuse an open request.1 finding
Why it is in this group
- The name "get_recommendations" says "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "get_recommendations" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_recommendations" says "get": a word for reading.
Description, as the server wrote it Side effect: creates a preparation request when no report is ready or refresh is true and the latest report became ready more than 24 hours ago; repeat calls reuse an open request. Pass refresh: true only when the user asks for a new report; when checking on a pending report, call without refresh. Use for Dreamlit's prioritized recommendations on which emails or workflows to add and what to fix or change in existing ones. Available on Pro and Scale plans only. Reports are prepared by Dreamlit's agents and reviewed by our team. Returns a ready report or a processing state while Dreamlit prepares it; check back later. The requester is also emailed when ready. Does not return raw notification analytics; use get_analytics for that.
Annotations the server declares
- title: Get recommendations
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
move_workflow_to_folderUse when the user asks to put a workflow or broadcast in a folder, move it to another folder, or take it out of a folder.No findings
Why it is in this group
- The name "move_workflow_to_folder" says "move": a word for a change.
Description, as the server wrote it Use when the user asks to put a workflow or broadcast in a folder, move it to another folder, or take it out of a folder. Folders are per list: the Published and Drafts lists on the Workflows page and the Sent and Drafts lists on the Broadcasts page each have their own folders, and this moves the workflow within the list it shows in now. Folders are flat; a "/" is just part of the name. A draft's folder does not carry over when it is published. Side effect: may create the folder; never deletes folders and does not change the draft, published version, or live triggers. Returns the folder, the list, and app URLs. Do not use to rename or delete folders.
Annotations the server declares
- title: Move workflow to folder
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
rename_workflowUse when the user asks to rename an existing Dreamlit workflow.No findings
Why it is in this group
- The name "rename_workflow" says "rename": a word for a change.
Description, as the server wrote it Use when the user asks to rename an existing Dreamlit workflow. Side effect: changes only the workflow name; the draft, published version, and live triggers are unchanged. Returns the updated name and app URLs. Do not use to edit workflow content or to name a new workflow; pass name to create_or_update_workflow instead.
Annotations the server declares
- title: Rename workflow
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 6Show 6 read-only tools
get_analyticsRead-only.No findings
Why it is in this group
- The name "get_analytics" says "get": a word for reading.
Description, as the server wrote it Read-only. Use get_analytics to query raw notification analytics: email and Slack sends and deliveries, email opens, clicks and bounces, overview metrics, per-recipient rows and workflow run rows, with filters, sorting, and cursor pagination. Returns bounded structured analytics data, effective query metadata, pagination details when rows are included, and relevant app URLs. Use get_lifecycle_report or get_recommendations for Dreamlit's prepared analysis. Does not provide Dreamlit's lifecycle judgments or prioritized recommendations. Do not use for CSV exports, bulk dumps, workflow edits, publishing, or low-level database access.
Annotations the server declares
- title: Get analytics
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_statusRead-only.No findings
Why it is in this group
- The name "get_status" says "get": a word for reading.
Description, as the server wrote it Read-only. Use first when the agent needs Dreamlit product guidance, prompting guidance, approved workspace context, project setup, schema hints, workflow state, or relevant app URLs. Returns a compact context pack with concepts, recommended tool flow, actor/workspace/project data, optional authoring context, optional workflow context, and appUrls. Workflow summaries include liveStatus, and broadcasts include an authoritative broadcast.state. Database tables that Dreamlit can see but not read rows from (row level security with no policy for Dreamlit) carry a warning and fixSql; run fixSql, or ask the user to run it, in the Supabase SQL editor. If Dreamlit couldn't read a connection's tables, that connection has tablesError instead of an empty list meaning no tables. Do not use this to create, update, publish, or unpublish workflows.
Annotations the server declares
- title: Get status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_workflow_and_preview_urlRead-only.Reads text others writeNo findings
Why it is in this group
- The name "get_workflow_and_preview_url" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_workflow_and_preview_url" says "get" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Read-only. Use before editing, verifying, or preparing publish for an existing workflow. Returns normalized draft and published workflow structure, liveStatus, the Dreamlit preview/builder URL, and status URLs. Broadcasts also include a broadcast object with state (draft, scheduled, sending, sent, cancelled, or failed), the run's scheduledFor, and cancelledAt or completedAt; this, not published or the trigger's sendAt, says whether the broadcast will send. Email HTML bodies are left out unless includeEmailHtml is true. Pass step ids only to edit_workflow_steps; when asking create_or_update_workflow for changes, describe steps by what they do. Do not use to create, update, publish, or unpublish workflows.
Annotations the server declares
- title: Get workflow and preview URL
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_brand_stylesRead-only.No findings
Why it is in this group
- The name "list_brand_styles" says "list": a word for reading.
Description, as the server wrote it Read-only. Use when the user wants to inspect saved project brand styles for generated email drafts. Returns paginated project brand style summaries, ids, default status, style metadata, and app URLs. Do not use to create, update, delete, or expose raw style provenance.
Annotations the server declares
- title: List brand styles
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_projectsRead-only.No findings
Why it is in this group
- The name "list_projects" says "list": a word for reading.
Description, as the server wrote it Read-only. Use when the target project is unknown or the user names a project instead of providing an id. Returns accessible Dreamlit projects in the approved workspace with project and workflow-list URLs. Do not use to inspect workflow structure or author changes.
Annotations the server declares
- title: List projects
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_workflowsRead-only.No findings
Why it is in this group
- The name "list_workflows" says "list": a word for reading.
Description, as the server wrote it Read-only. Use to find workflows in a project by name, description, or trigger type before inspection or editing. Trigger filters include database, auth email, repeating, broadcast, and no-trigger workflows. Returns paginated workflow summaries, published/sandbox state, liveStatus, trigger type, folder (the folder name in the list the workflow shows in, or null), workflow URLs, totalCount, hasMore, and nextOffset. Broadcasts also include a broadcast object with state (draft, scheduled, sending, sent, cancelled, or failed), scheduledFor, and cancelledAt or completedAt; for broadcasts, broadcast.state and liveStatus are authoritative over published, because a cancelled broadcast stays published but will not send. Do not use as the final source of truth before editing; call get_workflow_and_preview_url for full structure.
Annotations the server declares
- title: List workflows
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:25 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 15
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.dreamlit.ai/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://mcp.dreamlit.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 15 tools that change things (3 destructive, 1 irreversible, 11 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.dreamlit.ai/mcp: tools/list returned 24 tools to an anonymous client, including send_workflow_test (destructive), confirm_publish (destructive), unpublish_workflow (destructive), prepare_publish (irreversible), check_compatibility (write) and 10 more
Posture changes
- Nov 13, 2026
- Tools that change things, listed without credentials: 10 to 15
- Nov 6, 2026
- Tools that change things, listed without credentials: 8 to 10
- Oct 29, 2026
- Tools that change things, listed without credentials: 7 to 8
Findings
Matches of fixed checks, with the text they matched.
The server marks "get_lifecycle_report" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_lifecycle_report" says "get": a word for reading.
The server marks "get_recommendations" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_recommendations" says "get": a word for reading.
- Warnprepare_publish
The server marks "prepare_publish" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "prepare_publish" says "publish": a word for a change that another call does not undo.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 10 -> 15.View diff
- Tools that change things, listed without credentials: 10 to 15
Tools2 added, 1 changed.+2 added~1 changedView diff
- Added:get_lifecycle_reportChanges things
- Added:get_recommendationsChanges things
- Changed:get_analyticsOnly readsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 8 -> 10.View diff
- Tools that change things, listed without credentials: 8 to 10
PostureRemote posture changed. Tools that change things, listed without credentials: 7 -> 8.View diff
- Tools that change things, listed without credentials: 7 to 8
Tools1 added, 6 changed.+1 added~6 changedView diff
- Added:edit_workflow_stepsChanges things
- Changed:create_or_update_workflowChanges thingsdescription
- Changed:get_statusOnly readsdescription
- Changed:get_workflow_and_preview_urlOnly readsdescriptioninputSchema
- Changed:list_workflowsOnly readsdescription
- Changed:send_workflow_testCan't be undonedescription
- Changed:unpublish_workflowDeletes or cancelsdescriptioninputSchema
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http dreamlit https://mcp.dreamlit.ai/mcpclaude mcp add --transport http dreamlit https://mcp.dreamlit.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__dreamlit__get_status",
"mcp__dreamlit__list_projects",
"mcp__dreamlit__list_workflows",
"mcp__dreamlit__list_brand_styles",
"mcp__dreamlit__get_workflow_and_preview_url",
"mcp__dreamlit__get_analytics"
],
"ask": [
"mcp__dreamlit__create_or_update_workflow",
"mcp__dreamlit__edit_workflow_steps",
"mcp__dreamlit__rename_workflow",
"mcp__dreamlit__move_workflow_to_folder",
"mcp__dreamlit__get_lifecycle_report",
"mcp__dreamlit__get_recommendations",
"mcp__dreamlit__send_workflow_test",
"mcp__dreamlit__prepare_publish"
],
"deny": [
"mcp__dreamlit__confirm_publish",
"mcp__dreamlit__unpublish_workflow"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dreamlit. Review it before you use it.
Capability tags behind 5 rules
- mcp__dreamlit__create_or_update_workflow untrusted-input
- mcp__dreamlit__get_workflow_and_preview_url untrusted-input
- mcp__dreamlit__send_workflow_test outbound
- mcp__dreamlit__prepare_publish outbound
- mcp__dreamlit__confirm_publish outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.dreamlit/mcp/verify?hash=7b193250a4c9fed1df39f484ec81f9a27bc7a71f1a6a6afa640f274663534511" | jq -e '.changed == false'Pinned hash 7b193250a4c9, from Nov 10, 2026, 02:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.dreamlit/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.dreamlit/mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:41 UTC.
Dreamlit MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Dreamlit MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 10 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Dreamlit MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: confirm_publish and unpublish_workflow.
Can the Dreamlit MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: send_workflow_test and prepare_publish.
What tools does the Dreamlit MCP server have?
- 16 tools: 2 destructive, 2 irreversible, 6 write, 6 read. confirm_publish, unpublish_workflow, send_workflow_test, prepare_publish, create_or_update_workflow, edit_workflow_steps, rename_workflow, move_workflow_to_folder and 8 more.
Does the Dreamlit MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Dreamlit MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_workflow_test, prepare_publish and confirm_publish.
Has the Dreamlit MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.