day3

Official server for the day3 email platform: read account context, draft, edit, preview and test-send newsletter campaigns, and enroll contacts in automations; sending to an audience needs an extra API key scope. Bearer API key. Endpoint: https://go.day3.app/api/mcp · Docs

Needs auth Reachable, and asks for an OAuth sign-in before it will talk. Tools were not inspected.

Category: Marketing, content & social
Transport: http
Source: https://github.com/Mopra/day3.app
Endpoint: https://go.day3.app/api/mcp
MCP Registry: io.github.Mopra/day3
Handshake time: 861 ms
Repository: 1 stars · last push 2026-10-12
Last checked: 2026-10-13 15:08:53 UTC
Listed since: 2026-10-13

Health and compatibility

Endpoint reachable	Verified	Responded in 861 ms
MCP handshake (initialize)	Untested	The server asks for an OAuth sign-in first
Tool discovery (tools/list)	Untested	Not attempted
Authentication	Verified	Requires an OAuth sign-in
Protocol version	Untested	Only known after a completed handshake
Transport	Untested	Listed as http

Last checked 2026-10-13 15:08:53 UTC. Verified means the check saw it happen; it says nothing about whether the server is safe.

Recent history

1 daily check so far. Green answered, violet asked for auth, red did not answer.

Set up in your client

Claude Code

Run this in a terminal:

claude mcp add --transport http day3 https://go.day3.app/api/mcp

Then run /mcp inside Claude Code to sign in.

Claude Desktop

Open Settings → Connectors → Add custom connector and paste this URL:

https://go.day3.app/api/mcp

Or bridge it through mcp-remote in claude_desktop_config.json (needs Node.js):

{
  "mcpServers": {
    "day3": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://go.day3.app/api/mcp"
      ]
    }
  }
}

Cursor

Add to Cursor

Or add it to ~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{
  "mcpServers": {
    "day3": {
      "url": "https://go.day3.app/api/mcp"
    }
  }
}

VS Code

Add to VS Code

Or add it to .vscode/mcp.json:

{
  "servers": {
    "day3": {
      "type": "http",
      "url": "https://go.day3.app/api/mcp"
    }
  }
}

Or from a terminal:

code --add-mcp '{"name": "day3", "type": "http", "url": "https://go.day3.app/api/mcp"}'

Windsurf

Add it to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "day3": {
      "serverUrl": "https://go.day3.app/api/mcp"
    }
  }
}

Other clients

Most clients accept this shape. The endpoint is:

https://go.day3.app/api/mcp

{
  "mcpServers": {
    "day3": {
      "type": "http",
      "url": "https://go.day3.app/api/mcp"
    }
  }
}

If it does not connect

This server uses OAuth. Your client opens a browser window to sign in the first time it connects.
Restart the client after editing a config file, and keep keys out of files you commit.
If the tools do not appear, open the client's MCP log: a 401 means the credentials were not accepted, and a timeout means the server did not answer.

Badge

Maintain this server? Put its live status in your README:

[![MCP status](https://mcp.aianytime.net/badge/day3.svg)](https://mcp.aianytime.net/s/day3/)

Edit this entry · Report a problem

More in Marketing, content & social

Checks record what a server answered, not whether it is safe. A listing is not a security audit; read a server's source and permissions before you connect it. Add a server · JSON · llms.txt · llms-full.txt

Browse: Agents, IDEs & developer tools · Search & discovery · Knowledge, memory & context · Media & generation · Security · Finance & markets · Marketing, content & social · Cloud, ops & data · Commerce, travel & logistics · Work & productivity · No account needed · Local servers