day3
Draft email campaigns in day3 from Claude Code, Cursor or VS Code as editable composer blocks.
Connector by Mopra · GitHub account verified by the MCP Registry
Install
Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install connector/mopra-day3
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Remote endpoint
https://go.day3.app/api/mcpRemote (HTTP)
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list, install config and code. Checked Oct 26, 2026.
- Tools
- 7 read · 8 write · 3 delete
- Secrets
- 1 (API keys, tokens or passwords)
- Install scripts
- Nothing to install (hosted)
- Runs as
- Hosted (remote endpoint)
Tools by what they do 18
Read from the source code; the running server may list different tools.
Read 7 · Look things up without changing anything.
day3_check_domainday3_contextday3_get_campaignday3_list_automationsday3_list_campaignsday3_preview_campaignday3_setup_status
Write 8 · Create, change, send or run things.
day3_add_contactsday3_add_domainday3_create_audienceday3_create_campaignday3_create_formday3_send_testday3_set_mailing_addressday3_update_campaign
Delete 3 · Delete, drop, revoke or wipe things.
day3_enroll_in_automationday3_schedule_campaignday3_send_campaign
Secrets and settings it asks for
Secrets: values you paste in that let it act as you.
Authorization
Network hosts it talks to 34
acme.com· found in codeadmin.mailchimp.com· found in codeapi.beehiiv.com· found in codeapi.cloudflare.com· found in codeapi.kit.com· found in codeapp.beehiiv.com· found in codeapp.kit.com· found in codecloudflare-dns.com· found in codeconnect.mailerlite.com· found in codedash.cloudflare.com· found in codedashboard.mailerlite.com· found in codeday3.app· found in codedevelopers.cloudflare.com· found in codedocs.aws.amazon.com· found in codedocs.day3.app· found in codedocs.digitalocean.com· found in codedocs.netlify.com· found in codego.day3.app· found in remote endpoint, install command, codegodaddy.com· found in codegoogle-analytics.com· found in codehelp.one.com· found in codehelp.shopify.com· found in codeionos.com· found in codenamecheap.com· found in codeopenapi.vercel.sh· found in codesimply.com· found in codesupport.google.com· found in codesupport.hostinger.com· found in codesupport.squarespace.com· found in codesupport.wix.com· found in code
Show 4 more hosts
ui.shadcn.com· found in codevercel.com· found in codeyourapp.com· found in codeyoursite.com· found in code
Files it touches
/opt/day3
Tools (18)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
day3_add_contactsAdd contacts to an audienceAdd or update up to 500 contacts in an audience. Only add people who agreed to hear from this sender: mailing a bought or scraped list gets the workspace paused. Status may be subscribed (default) or unsubscribed, to carry over opt-outs from a previous tool.
day3_add_domainAdd a sending domainAdd the domain this workspace sends from (a subdomain like mail.example.com is best) and create its first sender. Returns the DNS records the human must add at their DNS host. Then call day3_check_domain to see when they resolve.
day3_check_domainCheck a sending domainread-onlyRe-check whether a domain's DNS records are live and the domain is verified. DNS can take minutes to hours; Day3 also keeps checking on its own, so there is no need to poll quickly.
day3_contextGet Day3 workspace contextread-onlyEverything needed before writing an email: the workspace's audiences, senders, verified sending domains, plan and sending status, and what this connection is allowed to do. Call this first — the ids it returns are the ones the other tools take.
day3_create_audienceCreate an audienceCreate a list of contacts that campaigns are sent to.
day3_create_campaignCreate a campaign draftCreate a draft campaign in Day3 from Day3 Markdown. Returns the campaign's id and a URL where a human can open it in the composer. Creating a draft never sends anything.
day3_create_formCreate a signup formCreate a hosted signup form that adds people to an audience, and return its public URL to share or link from a website. Double opt-in is on by default: new signups confirm by email first.
day3_enroll_in_automationEnroll a contact in an automationcan change or delete dataEnroll one email address in an active automation, so they receive every email in the flow on its schedule. Pass `attributes` to create the contact in the automation's audience if they are not in it yet (otherwise a missing contact is reported as `not_subscribed` and nothing is sent). Requires the `automations:enroll` scope. Confirm with the user before calling this.
day3_get_campaignGet a campaignread-onlyRead a campaign including its body as Day3 Markdown. Use this before editing, so changes made in the Day3 composer since you last wrote are picked up rather than overwritten.
day3_list_automationsList automationsread-onlyList the workspace's automations (welcome series, onboarding flows) newest first, with their status and trigger. `trigger` is `audience_join` when the flow also fires on its own as people join the audience, or `api` when only enrolling starts it. Only `active` automations can be enrolled into.
day3_list_campaignsList campaignsread-onlyList campaigns newest first, optionally filtered by status.
day3_preview_campaignPreview a campaignread-onlyRender the campaign exactly as it will arrive — theme, merge tags and compliance footer included. Returns the plain-text rendering plus a URL that opens the HTML in a browser. Set include_html to also get the raw HTML document (large).
day3_schedule_campaignSchedule a campaigncan change or delete dataSchedule the campaign to send to its whole audience at a future time. Same consequences as sending, just later. Requires the `campaigns:send` scope.
day3_send_campaignSend a campaign to its audiencecan change or delete dataSend the campaign to its whole audience, now. This is irreversible: it starts the automated risk review and, if that passes, delivery begins immediately — there is no further confirmation step. Requires the `campaigns:send` scope. Confirm with the user before calling this.
day3_send_testSend a test emailDescription is built at runtime.
Show 3 more tools
day3_set_mailing_addressSet the business mailing addressSet the physical mailing address printed in every email footer. Anti-spam law requires it, so Day3 will not send without one. Use the real business address the human gives you; never invent one.
day3_setup_statusGet workspace setup statusread-onlyWhat this workspace still needs before it can email real subscribers, in order, with the tool that does each step. Call it after connecting to a new workspace, and again after each step.
day3_update_campaignUpdate a campaign draftUpdate fields on a draft or scheduled campaign. Only the fields you pass are changed. Passing `markdown` replaces the whole body.
Signals
- Stars
- 1
- Forks
- 0
- Open issues
- 0
- Last commit
- Oct 19, 2026 (9 days ago)
- Last release
- Oct 11, 2026 (17 days ago)
From GitHub (fetched Oct 24, 2026).
Details
- Registry name
io.github.Mopra/day3- Version
- 1.0.0
- Auth
- Bearer token
- License
- License unknown
- Repository
- github.com/Mopra/day3.app
- Website
- docs.day3.app/mcp
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
Cite this page
day3 MCP server. Agent Mart. https://agentmart.dev/connectors/mopra-day3 (last updated 2026-10-24)