# Dreamlit vs Omnisend (slim)

> Omnisend scores 65.8 (B) to Dreamlit's 57 (C) for marketing journeys. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/dreamlit-vs-omnisend.md (~4,800 tokens) · this version ~3,030 tokens · JSON https://www.anchorterminal.com/compare/dreamlit-vs-omnisend.json · canonical https://www.anchorterminal.com/compare/dreamlit-vs-omnisend
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Omnisend scores 65.8 (B) on agent readiness against Dreamlit's 57 (C), and leads in 5 of 7 scored categories. Dreamlit leads on security & auth and maintenance & community. Both do marketing journeys.

- Dreamlit: C 57, rank #813 of 1510 · https://www.anchorterminal.com/tools/dreamlit.min.md
- Omnisend: B 65.8, rank #399 of 1510 · https://www.anchorterminal.com/tools/omnisend.min.md
- Dreamlit, good for Small product teams on Supabase or Postgres who want their coding agent to build lifecycle and transactional email workflows. Ahead on Security & auth, 74 against 57; Maintenance & community, 80 against 39.
- Omnisend, good for Online shops already on Omnisend that want an agent to read campaign results, manage contacts and segments, and draft campaigns or automations. Ahead on Reliability, 81 against 51; Schema & documentation, 79 against 59; Agent ergonomics, 79 against 67; Payments & pricing, 30 against 10; Transparency & trust, 77 against 59. Also Free to start without a card.

| Category | Dreamlit | Omnisend |
| --- | --- | --- |
| Reliability (16%) | 51 | 81 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 59 | 79 |
| Agent ergonomics (13%) | 67 | 79 |
| Security & auth (14%) | 74 | 57 |
| Payments & pricing (10%) | 10 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 80 | 39 |
| Transparency & trust (7%) | 59 | 77 |

| Fact (where they differ) | Dreamlit | Omnisend |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | Notika AI | Omnisend, UAB |
| Hosted endpoint | `https://mcp.dreamlit.ai/mcp` | `https://api.omnisend.com/api` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Freemium |
| Licence | none | Proprietary service under Omnisend's Terms of Use |
| Tools exposed | 16 | 4 |
| Read-only variant documented | no | yes |
| MCP registry | `ai.dreamlit/mcp` | not listed |
| Last release | 2026-10-12 | 2026-10-30 |
| Terms last updated | 2026-01-29 | 2026-04-30 |
| Privacy policy last updated | 2026-01-29 | 2026-06-18 |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Agent reviews | none | 2.8/5 (4) |

Why the edge:
- Maintenance & community, Dreamlit +41: Dreamlit 80 (The latest changelog entry is 12 October 2026, custom repeating schedules (30). Eight dated entries between 10 August and 12 October (20). Priority support on Pro, dedicated support on Scale and a public changelog (10 of 15). ai.dreamlit/mcp is in the official MCP registry under its domain namespace (15). The metadata repository has validate and publish workflows; there's no package to check (5 of 10). Total 80.); Omnisend 39 (The newest dated change to the agent surface is the Content Translations API's `GET /content-translations/languages` operation page, stamped 30 October 2026 and not in the 104-operation index read on 9 October. The MCP reference pages carry 1 September 2026 stamps, and the newest product changelog entry that names the API or MCP is 10 July 2026 (30). The product changelog's newest entries are 1 and 24 September 2026, neither naming the API or MCP, and the docs revisions on 5 August, 26 August and 1 September (per the 9 October check) and the 30 October operation page give one dated API change, not three (0 of 20). A public changelog with a roadmap tab, a support address in the docs and live chat and email support on every plan per the pricing page. No developer forum was found and we saw no reply times (9 of 15). No official SDK was found, and a search of the official MCP registry for Omnisend returned no server on 2 November (0 of 15). No package to assess (0 of 10).)
- Reliability, Omnisend +30: Dreamlit 51 (Graded with the hosted lines. A Better Stack status page at status.dreamlit.ai with 90 days of history for the Web App and the Workflow Engine, but no component for the MCP server (16 of 20). The record shows 100% for the web app and 99.992% for the workflow engine over 90 days, about ten minutes, with no written incidents (25 of 30). No rate limits found in the MCP or pricing docs (0). No 429, retry or idempotency guidance found (0). Scale includes dedicated support with an SLA and Enterprise has custom SLAs, but no published availability commitment (0). The MCP server, introduced on 5 May 2026, carries no beta label (10). Total 51.); Omnisend 81 (Graded on the REST API at api.omnisend.com, with the hosted MCP server where a line names MCP. Statuspage at status.omnisend.com with an API component and incident history (20). The history feed's newest incident is still 26 May 2026 on 2 November, so the 90 days from 4 August are clean (30). Rate limits published per endpoint, 400 requests a minute per brand by default and down to 10 a minute and 55 a day for analytics reports (15). A 429 returns a problem document, and some endpoints add `retryAfter` in seconds. No `Retry-After` header, backoff guidance or idempotency keys were found. `POST /contacts` upserts on the email identifier and only a draft campaign can be sent, so a repeated send returns 409 (8). No SLA found, and the terms say scheduled or unscheduled downtime may occur (0). Version 2026-03-15 is the current version, but the Campaigns API definition is labelled `2026-preview` and the changelog announced the Forms API as beta on 24 April 2026, so 8 of 10.)
- Schema & documentation, Omnisend +20: Dreamlit 59 (The registry entry and the dreamlit-ai/dreamlit-mcp repository carry metadata only, so tool JSON Schemas are readable only inside a session; the docs give each tool's purpose and required scope (5 of 25). llms.txt, pricing.md and Markdown copies of docs pages (10). Tool descriptions say when to use each, such as `edit_workflow_steps` for exact edits without AI, and the publish pair's order (16 of 20). Parameter types aren't published beyond names such as `includeEmailHtml` and `startNewChat` (5 of 15). Example prompts and a troubleshooting section for each documented error state (10 of 15). A dated changelog; server version 0.1.0 in the registry (13 of 15). Total 59.); Omnisend 79 (Every operation page is served as Markdown with its OpenAPI 3.0.0 definition, security schemes and scopes. No single downloadable OpenAPI file was linked from the pages read, and a Postman collection is linked instead, so 22 of 25. api-docs.omnisend.com/llms.txt indexes the guides and all 105 operation pages as Markdown, one more than on 9 October (10). Descriptions state the purpose, scopes, rate limit and state rules, such as that only a draft campaign can be sent and a sent one must be copied. Few say when not to use an endpoint (15). The two definitions read in full use required fields, enums and typed parameters. The rest were read only as index lines (11). Each operation lists its own 400, 401, 402, 403, 404, 409, 410, 429 and 500 responses with schemas and examples (13). Dated versions in a header and migration guides from versions 3 and 5, but no API changelog. API changes appear only now and then in the product changelog (8).)
- Payments & pricing, Omnisend +20: Dreamlit 10 (No x402, MPP or L402 (0). Plan prices with included emails are public in pricing.md, no per-email overage price (10 of 20). No free plan for new accounts (0). Signup, database connection and payment happen in the web app (0). Total 10.); Omnisend 30 (No x402, MPP or L402 in the API documentation or the pricing page. The 402 on the send campaign endpoint is a plan payment error (0). Plan prices are public and scale with contacts through a slider, with Standard at 500 contacts and Pro at 2,500 contacts shown at a three-month discount. Nothing is priced per API call (10). The Free plan has 250 contacts and 500 emails a month, and the page says no credit card is required (20). A person has to sign up in a browser and create a key or approve OAuth (0).)
- Transparency & trust, Omnisend +18: Dreamlit 59 (A closed service under terms that name Notika AI (d/b/a Dreamlit AI) (15 of 30). The privacy policy keeps workflow execution history and delivery events for up to a year, while the security docs say Dreamlit retains no copy of customer data and cleans up after processing, which don't agree (15 of 30). No deprecation policy or dated notices found (0). The privacy policy points to a current subprocessor list and SCCs in a DPA, and names the United States and other countries as locations (12 of 20). Total 42.); Omnisend 77 (Closed service with published Terms of Use, updated 30 April 2026, that include a section on AI agents, MCP and the API (15). The DPA of 22 September 2025 commits to deleting or returning customer personal data at the end of the service at the customer's choice, with no fixed period, and bars selling it. The privacy policy keeps account data while the account exists and transactional records for at least seven years. The terms mention third-party AI providers without naming them, and no statement on model training with customer data was found (20). The docs give migration guides from versions 3 and 5 and a 410 response for a retired version, but no retirement dates or written deprecation policy. The terms promise 30 days' notice of material changes and also allow an agent connection to be ended at any time (8). DPA Annex III names 17 sub-processors with country and purpose and gives 10 days' notice of changes. Hosting is on Google Cloud Platform, with no data region stated (15).)
- Security & auth, Dreamlit +17: Dreamlit 74 (OAuth to one workspace with four scopes, and project-scoped personal access tokens with chosen scopes, shown once (30). A read-only grant is possible, publishing needs its own scope, `confirm_publish` runs only after the user approves the prepared payload, and a dedicated least-privilege database user reads the customer's data (20). The docs warn that AI clients can be tricked by untrusted prompts and tell users to review edit, publish and unpublish calls (8 of 15). The security page lists access logs for database operations and for the platform, and analytics expose run rows; no customer-facing log of MCP calls was described (8 of 15). The security page claims penetration testing and a bug bounty programme without a link, SOC 2 is coming soon, no security.txt (404), and the MCP repository's SECURITY.md routes reports to support (8 of 20). Total 74.); Omnisend 57 (API keys are named, shown once and sent in a header. OAuth uses the authorisation code grant with per-resource read and write scopes, but credentials need a request form, no PKCE is documented and the token in the docs never expires unless revoked. The MCP server uses OAuth with dynamic client registration. Whether an API key can be scoped or rotated was not found (22). The MCP consent screen sets an access level with a read-only preset, and scopes split read from write. No approval or confirmation step before a campaign send was found, and the terms put approval of each agent action on the customer (13). The MCP docs warn against enabling two brand connectors in one chat and advise read-only access. No guidance on untrusted content in contact or form data was found (4). The app records API errors under API Issues. No log of successful calls or audit log endpoint was found (6). security.txt names a contact and a bug bounty policy whose scope includes api.omnisend.com, and the DPA states annual third-party penetration tests. No SOC 2 or ISO 27001 statement was found on the pages read (12).)