Dreamlit

ai.dreamlit由 dreamlit.ai 發布官方發布者v0.1.0更新於 Oct 24, 2026

Create, test, publish, and manage Dreamlit notification workflows from AI clients.

已驗證Streamable HTTP可網頁執行效率與工作流溝通與協作資料與分析

概覽

AI 產生的概覽

讓助理為 Supabase 和 Postgres 應用程式建立、檢查、測試、發布、取消發布並分析 Dreamlit 通知工作流程。

可以做什麼
Dreamlit 提供產品層級工具,可依成果導向的提示建立通知工作流程,而不必直接編輯流程圖。唯讀工具涵蓋工作區脈絡、專案、工作流程、品牌樣式、附預覽網址的工作流程結構,以及分頁的分析資料。寫入工具可建立或更新草稿、重新命名和移動工作流程,並傳送單封測試郵件或 Slack 訊息。發布是獨立步驟:先驗證並回傳確認欄位,確認發布後安裝觸發器或安排廣播,取消發布則停用它們。
適用情境
當你希望 AI 用戶端草擬資料庫觸發通知或排程摘要等工作流程、透過 Dreamlit 檢視並發布,或回答關於通知互動與執行資料的有限問題時使用。
執行需求
透過支援遠端伺服器的 MCP 用戶端存取的遠端 Streamable HTTP 端點。驗證採用 OAuth,不支援 OAuth 的用戶端可改用個人存取權杖;存取範圍限於授權時選擇的工作區,權杖以專案為範圍。權限範圍為 workflows:read、workflows:write、workflows:publish 和 analytics:read。
安裝前請注意
發布與取消發布會改變線上行為:confirm_publish 會安裝觸發器、安排或傳送廣播,取消發布會停止新的執行,但進行中的執行可能繼續傳送。當 confirmSend 為 true 時傳送測試訊息會產生副作用。只授予所需權限,因為寫入與發布權限可讓助理變更實際工作流程。不要在提示中放入密鑰或原始憑證。分析資料僅支援分頁,不提供大量匯出。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Dreamlit,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/ai.dreamlit%2Fmcp/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。

{
  "mcpServers": {
    "dreamlit": {
      "type": "http",
      "url": "https://mcp.dreamlit.ai/mcp"
    }
  }
}

README

Dreamlit MCP

Dreamlit MCP lets AI clients create, inspect, test, publish, unpublish, analyze, and style Dreamlit notification workflows.

Dreamlit is a database-driven notification workflow platform for Supabase and Postgres apps. Use this MCP server when you want an AI client to help build notification workflows from outcome-oriented prompts, review and publish them through Dreamlit, or answer bounded analytics questions about notification performance.

Server

  • Production MCP URL: https://mcp.dreamlit.ai/mcp
  • Transport: Streamable HTTP
  • Authentication: OAuth, with personal access token fallback for clients that do not support OAuth

This repository contains public setup docs and MCP registry metadata for Dreamlit's hosted remote MCP server. The production backend implementation is not open source.

Quick Start

Use your MCP client's remote server flow and enter:

text
https://mcp.dreamlit.ai/mcp

The client should open a Dreamlit authorization page. Choose the workspace you want the AI client to access and approve the requested scopes.

Codex CLI

sh
codex mcp add dreamlit --url https://mcp.dreamlit.ai/mcpcodex mcp login dreamlit

To request every supported v1 scope explicitly:

sh
codex mcp login dreamlit --scopes workflows:read,workflows:write,workflows:publish,analytics:read

MCP Inspector

sh
npx @modelcontextprotocol/inspector

Then choose Streamable HTTP and use:

text
https://mcp.dreamlit.ai/mcp

Tools

Dreamlit exposes product-level workflow and analytics tools, not low-level graph editing or database APIs.

ToolScopePurpose
get_statusworkflows:readGet Dreamlit guidance, workspace context, project setup, schema hints, workflow state, and app URLs.
list_projectsworkflows:readFind accessible Dreamlit projects in the approved workspace.
list_workflowsworkflows:readFind workflows in a project by name, description, trigger type, and pagination.
list_brand_kitsworkflows:readFind saved brand kit ids and style summaries with pagination before applying one to generated email drafts.
get_workflow_and_preview_urlworkflows:readInspect a workflow draft and get the Dreamlit preview or builder URL before editing or publishing.
get_analyticsanalytics:readQuery bounded notification analytics, recipient engagement, and workflow run data with filters and cursor pagination.
create_or_update_workflowworkflows:writeCreate a new workflow draft or update an existing draft from a natural-language prompt.
send_workflow_testworkflows:writeConfirm and send a draft email or Slack test without publishing the workflow.
prepare_publishworkflows:publishValidate a workflow before publishing and return confirmation fields.
confirm_publishworkflows:publishPublish or schedule a workflow after explicit user confirmation.
unpublish_workflowworkflows:publishDisable live triggers or schedules for a workflow.

Recommended Flow

  1. Call get_status first to understand the workspace, project setup, and prompting guidance.
  2. Use list_projects and list_workflows if the user names a project or workflow without IDs.
  3. Use list_brand_kits when the user wants a specific saved brand kit applied to generated email drafts.
  4. Use get_workflow_and_preview_url before editing an existing workflow.
  5. Use get_analytics for bounded analytics questions, filtering first and paginating with returned cursors for larger result sets.
  6. Use create_or_update_workflow to create or update a draft.
  7. Open the returned preview or builder URL and send workflow tests for important email or Slack messages.
  8. Publish only after explicit user confirmation, using prepare_publish followed by confirm_publish.

Drafts are not live after authoring. Publishing is always a separate explicit step.

Prompting Tips

Ask for the outcome, not a workflow graph. Good prompts include:

  • The event or schedule that should start the workflow.
  • The audience or recipient.
  • The message goal and tone.
  • The data needed for personalization.
  • Timing, timezone, and business rules.
  • Whether recipients should be able to unsubscribe.

Examples:

text
When a new organization row is inserted, send an internal Slack alert with the organization name, owner email, and plan.
text
Every Monday at 9 AM America/New_York, send admins a weekly usage digest summarizing active users, failed payments, and new signups.
text
Tomorrow at 10 AM, announce the launch to active users who opted into product updates. Include unsubscribe.

Access Model

OAuth access is scoped to the workspace selected during authorization. Personal access tokens are project scoped and can be created from Dreamlit project settings.

Available scopes:

  • workflows:read
  • workflows:write
  • workflows:publish
  • analytics:read

Use the least privilege that fits the client. Read-only workflow and brand-kit clients should request only workflows:read; analytics clients should request analytics:read.

Data Handling

Dreamlit MCP can access workflow metadata, saved brand kit summaries, connected project context, and bounded analytics results needed to perform the requested actions. It does not require clients to send database credentials through MCP.

Analytics access is structured and paginated. Use filters and cursors for larger result sets; CSV exports and bulk dumps are not exposed through MCP.

Do not paste secrets, raw credentials, or private tokens into prompts. Use Dreamlit's app settings for integrations and credentials.

Support

For support, contact [email protected].

來源:README.md,提交 829d855

工具

13

get_status

Get status

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.

輸入參數projectIdworkflowId

create_or_update_workflow

Create or update workflow

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.

輸入參數nameprompt必填projectIdworkflowIdstartNewChatuserCurrentTimeIsouserCurrentTimeZoneIduserEmailStepComments

rename_workflow

Rename workflow

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.

輸入參數name必填workflowId必填

move_workflow_to_folder

Move workflow to folder

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.

輸入參數folder必填workflowId必填

list_projects

List projects

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.

輸入參數limitsearch

list_workflows

List workflows

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.

輸入參數limitoffsetsearchprojectIdtriggerFilters

list_brand_styles

List brand styles

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.

輸入參數limitoffsetprojectId

get_workflow_and_preview_url

Get workflow and preview URL

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. Step ids are for reading only; when asking create_or_update_workflow for changes, describe steps by what they do. Do not use to create, update, publish, or unpublish workflows.

輸入參數workflowId必填

get_analytics

Get analytics

Read-only. Use to query Dreamlit analytics for overview metrics, notification rows, recipient engagement, or 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. Do not use for CSV exports, bulk dumps, workflow edits, publishing, or low-level database access.

輸入參數sortview必填limitrangecursorwindowchannelfiltersincludetimeZoneprojectId

send_workflow_test

Send workflow test

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.

輸入參數rowDataworkflowId必填confirmSendmessageTypetestTargetIdtestRecipientEmail

prepare_publish

Prepare publish

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.

輸入參數workflowId必填

confirm_publish

Confirm publish

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.

輸入參數workflowId必填isSandboxedexpectedUpdatedAtIsoexpectedEditableVersionIdexpectedPublishedVersionId

unpublish_workflow

Unpublish workflow

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.

輸入參數workflowId必填inProgressRuns

版本歷史

1
  1. v0.1.0最新Sep 16, 2026

評分

已滿足適用檢查項的 90%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。