Delivrie

io.github.codeddesignerPublished by GitHub account codeddesignerv1.1.0Updated Nov 14, 2026

Send email, run broadcasts and automations, and answer your inbox from any AI agent.

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Delivrie's remote MCP server lets an AI agent send email, run broadcasts and automations, and answer an inbox.

What you can do
  • Send transactional and marketing email through the Delivrie platform
  • Run broadcasts and automations, and manage audiences
  • Read and answer inbox messages from the agent
  • Work with the same email service that offers a REST API, signed webhooks and metrics
When to use it
Useful when you want an assistant to draft and send email, trigger marketing broadcasts or automations, or triage and reply to incoming mail without leaving the chat.
Requirements
A remote MCP endpoint at delivrie.io reached over streamable HTTP, with OAuth sign-in required. No local package, environment variables or headers are declared; a Delivrie account is implied by the OAuth flow.
Before you install
The server can send email and run broadcasts and automations, so messages may reach real recipients and consume plan limits. OAuth grants access to your Delivrie account; review the scopes before connecting. The README also mentions billing through Paystack, so paid plans may apply.

Installation

In SourceWeft

  1. Open Delivrie in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.codeddesigner%2Fdelivrie/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "delivrie": {
      "type": "http",
      "url": "https://delivrie.io/api/mcp"
    }
  }
}

README

Delivrie

Email for developers: transactional and marketing email with a REST API, signed webhooks, a visual broadcast editor, audiences, metrics, and an MCP server for AI agents. Sending runs on Amazon SES.

Live at https://delivrie.io

Structure

PathWhat it is
index.html, styles.css, script.jsMarketing landing page
app.html, app/Dashboard SPA (vanilla JS ES modules, no build step)
assets/Logos, favicon and icons (from the Figma brand page)
supabase/functions/delivrie/Edge function: REST API, SES/SNS integration, webhooks, cron, MCP server
supabase/functions/billing/Edge function: Paystack subscriptions (USD and NGN), served at /api/billing/*
supabase/migrations/Database schema: tables, row-level security, RPCs, cron job, storage bucket
vercel.jsonRewrites /api/* to the edge function and app routes to app.html

Deploy

  • Frontend: static files on Vercel. No build command; output directory is the repo root.
  • Backend functions: pushed changes under supabase/functions/ deploy automatically through .github/workflows/deploy-functions.yml (needs the SUPABASE_ACCESS_TOKEN repository secret).
  • Backend: Supabase (Postgres + Auth + Storage) with the delivrie edge function. To recreate the database on a new project, run the files in supabase/migrations/ in order (or supabase db push). The cron migration contains the project's function URL; change it if you deploy to a different project.

Configuration (Supabase edge function secrets)

SecretRequiredPurpose
AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEYYesIAM user with ses:* and SNS access to delivrie-events topics
APP_URLYesPublic URL, e.g. https://delivrie.io
SYSTEM_FROMOptionalSender for invites/system mail, e.g. Delivrie <[email protected]>
SYSTEM_REGIONOptionalDefault SES region (default eu-west-1)
ANTHROPIC_API_KEYOptionalEnables AI answers in Help → Ask Delivrie
ENFORCE_LIMITSOptionaltrue to enforce plan limits
PAYSTACK_SECRET_KEYFor billingPaystack secret key (sk_test_… while testing, sk_live_… in production)

The Supabase anon key in app/js/lib/sb.js is public by design; data access is protected by row-level security.

Source: README.md at commit c4c41d5

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestNov 14, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.