I Connected Claude to My Titan (GoDaddy) Inbox with an Open-Source MCP Server

#ai #opensource #mcp #typescript

If your business email is on Titan, Claude can't reach it the way it reaches Gmail or Outlook. If you bought your domain and mailbox from GoDaddy, you're very likely on Titan too.

The reason is simple: Titan has no public REST API.

So I built titan-email-mcp, an open-source Model Context Protocol server. It connects Claude (Desktop, Code, Cursor, or any MCP client) to a Titan mailbox using the protocols Titan does support: IMAP and SMTP.

What it lets you do

Once it's connected, you can ask Claude things like:

"Summarize my unread mail from today."
"Find that invoice from last March."
"Draft a reply confirming Thursday. Don't send it."
"Move all newsletters in my inbox to Archive."

The 10 tools

Tool	Purpose
`test_connection`	Verify IMAP + SMTP login without touching mail
`list_folders`	Folders with message/unread counts
`list_emails`	Latest emails in a folder
`search_emails`	Filter by from, to, subject, text, dates, unread
`read_email`	Full message: headers, body, attachment list
`send_email`	Send new mail (copy saved to Sent)
`reply_email`	Threaded reply / reply-all, or save as draft
`save_draft`	Save to Drafts (always available)
`move_email`	Move to Archive, Trash, etc.
`set_flags`	Read/unread, flag/unflag

Setup in 2 minutes

1. Enable IMAP/SMTP in Titan webmail under Settings → Enable Titan on other apps. Without this, logins are rejected even with the right password.

2. Add it to Claude Desktop in claude_desktop_config.json:

{
  "mcpServers": {
    "titan-email": {
      "command": "npx",
      "args": ["-y", "titan-email-mcp"],
      "env": {
        "TITAN_EMAIL": "you@yourdomain.com",
        "TITAN_PASSWORD": "your-password",
        "TITAN_PROVIDER": "titan",
        "TITAN_FROM_NAME": "Your Name",
        "TITAN_ALLOW_SEND": "false"
      }
    }
  }
}

Or add it with Claude Code:

claude mcp add titan-email --scope user \
  -e TITAN_EMAIL=you@yourdomain.com \
  -e TITAN_PASSWORD=your-password \
  -e TITAN_PROVIDER=titan \
  -e TITAN_ALLOW_SEND=false \
  -- npx -y titan-email-mcp

3. Verify by asking Claude to run test_connection. You should see "status": "ok" for both IMAP and SMTP.

GoDaddy users

GoDaddy resells Titan under its own hostnames. Set TITAN_PROVIDER=godaddy and you don't need to look them up. This preset is tested against a live GoDaddy-hosted mailbox. For other resellers, override TITAN_IMAP_HOST / TITAN_SMTP_HOST directly.

Design decisions

Giving an AI agent access to your inbox should make you a little nervous. These choices are deliberate:

Read-only with one flag. TITAN_ALLOW_SEND=false disables sending. Drafts still work, so the agent drafts and you hit send.
No middleman. Credentials go from your local config straight to Titan over TLS. There's no proxy and no telemetry.
Nothing persisted. Each call opens a short-lived IMAP session and closes it. Nothing is cached or logged to disk.
Small surface. Ten tools, not fifty, so there are fewer ways for an agent to surprise you.

Stack

It's written in TypeScript on Node.js and speaks MCP over stdio. It's published on npm and listed on the official MCP Registry and on Smithery. MIT licensed.

Try it

If you're on another Titan reseller, PRs adding its hostnames are welcome. A ⭐ helps others find the project.

What should an email agent do next: triage rules, attachment handling, scheduled digests? Tell me in the comments.

DEV Community