Titan Email MCP
Connect Claude — Desktop, Code, Cursor, or any client — directly to a mailbox, so it can read, search, triage, and send mail on your behalf.
Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
npx -y [email protected]Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
TITAN_EMAIL=<value> TITAN_PASSWORD=<secret> TITAN_PROVIDER=<value> TITAN_FROM_NAME=<value> TITAN_ALLOW_SEND=<value> TITAN_SENT_FOLDER=<value> TITAN_DRAFTS_FOLDER=<value> claude mcp add io.github.qmmughal-titan-email-mcp -- npx -y titan-email-mcp@1.0.5รันในเทอร์มินัล
{ "mcpServers": { "io.github.qmmughal-titan-email-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "TITAN_EMAIL": "<value>", "TITAN_PASSWORD": "<secret>", "TITAN_PROVIDER": "<value>", "TITAN_FROM_NAME": "<value>", "TITAN_ALLOW_SEND": "<value>", "TITAN_SENT_FOLDER": "<value>", "TITAN_DRAFTS_FOLDER": "<value>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดPackage: npmjs.com/package/titan-email-mcp · Source: github.com/qmmughal/titan-email-mcp · Listed on the official MCP Registry as io.github.qmmughal/titan-email-mcp, and on Smithery
Titan Email (the mailbox product bundled with many domain registrars, including GoDaddy) has no public REST API. This server bridges that gap by talking to Titan's standard IMAP and SMTP endpoints instead, so your AI assistant gets real mailbox access without any vendor integration work.
Contents: Why use this · Supported providers · Tools · Quick start · GoDaddy users — ready-to-paste config · Configuration · Security notes · Troubleshooting · Development · Contributing · License
TITAN_PROVIDER setting handles the different server hostnames — see Supported providers.TITAN_ALLOW_SEND (default on, but trivially switched off) so you can run Claude in read-only / draft-only mode until you trust it.npx titan-email-mcp — no cloning or building required for everyday use.Titan Email is used directly (imap.titan.email / smtp.titan.email) and resold under other brands with different hostnames. Set TITAN_PROVIDER to pick the right defaults — no need to remember hostnames:
godaddy has been tested against a live GoDaddy-hosted Titan mailbox and confirmed working.
If your reseller uses yet another hostname, leave TITAN_PROVIDER unset and override TITAN_IMAP_HOST / TITAN_IMAP_PORT / TITAN_SMTP_HOST / TITAN_SMTP_PORT directly — check your provider's welcome email or webmail settings page for the exact values. Explicit host/port variables always win over the preset.
1. Enable IMAP/SMTP access — in Titan webmail (or your reseller's equivalent, e.g. GoDaddy's Email & Office settings): Settings → Enable Titan on other apps. This is required; without it, logins from this server will be rejected even with the correct password.
2. Get the server — either works, pick one:
npx titan-email-mcp directly; npm fetches it on first use and caches it. This is the path used in the config examples below.git clone https://github.com/qmmughal/titan-email-mcp.git
cd titan-email-mcp/titan-mcp
npm install
npm run build
This produces dist/index.js — point your client's args at its absolute path instead of using npx.3. Register it with your MCP client — pick your client below, plug in your credentials, then restart the client.
4. Verify. In a new conversation, ask Claude to run test_connection. You should get back "status": "ok" for both imap and smtp. If not, see Troubleshooting.
Edit your claude_desktop_config.json (config file location):
{
"mcpServers": {
"titan-email": {
"command": "npx",
"args": ["-y", "titan-email-mcp"],
"env": {
"TITAN_EMAIL": "[email protected]",
"TITAN_PASSWORD": "your-password",
"TITAN_PROVIDER": "titan",
"TITAN_FROM_NAME": "Your Name",
"TITAN_ALLOW_SEND": "false"
}
}
}
}
Built from source instead? Swap "command": "npx", "args": ["-y", "titan-email-mcp"] for "command": "node", "args": ["/absolute/path/to/titan-email-mcp/titan-mcp/dist/index.js"].
claude mcp add titan-email --scope user \
-e [email protected] \
-e TITAN_PASSWORD=your-password \
-e TITAN_PROVIDER=titan \
-e TITAN_FROM_NAME="Your Name" \
-e TITAN_ALLOW_SEND=false \
-- npx -y titan-email-mcp
Use --scope project instead of --scope user to make it available only inside one repo (written to .mcp.json, safe to share with a team since it carries no secrets by itself — just don't commit real credentials into it).
If your domain and mailbox were purchased through GoDaddy, your email almost certainly runs on Titan's infrastructure under GoDaddy's own hostnames, not Titan's. This has been tested end-to-end against a live GoDaddy-hosted Titan mailbox — you don't need to look those hostnames up yourself; just use TITAN_PROVIDER=godaddy and everything else works exactly the same as above:
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"titan-email": {
"command": "npx",
"args": ["-y", "titan-email-mcp"],
"env": {
"TITAN_EMAIL": "[email protected]",
"TITAN_PASSWORD": "your-godaddy-mailbox-password",
"TITAN_PROVIDER": "godaddy",
"TITAN_FROM_NAME": "Your Name",
"TITAN_ALLOW_SEND": "false"
}
}
}
}
Claude Code:
claude mcp add titan-email --scope user \
-e [email protected] \
-e TITAN_PASSWORD=your-godaddy-mailbox-password \
-e TITAN_PROVIDER=godaddy \
-e TITAN_FROM_NAME="Your Name" \
-e TITAN_ALLOW_SEND=false \
-- npx -y titan-email-mcp
Before either one works, enable IMAP/SMTP access in GoDaddy's Email & Office settings (same "allow other apps" toggle mentioned in step 1 above — GoDaddy's webmail may label it slightly differently than Titan's own). Then run test_connection to confirm. If godaddy doesn't work for your specific plan, your mailbox may be on a different GoDaddy backend — check Email & Office → Settings → Email Setup in your GoDaddy dashboard for the exact IMAP/SMTP hostnames and override TITAN_IMAP_HOST/TITAN_SMTP_HOST directly (see Configuration).
Any client that supports the standard mcpServers JSON shape (command / args / env) works the same way — use the Claude Desktop block above as a template and drop it into that client's MCP config file.
All configuration is environment variables passed through your MCP client's server config — never command-line flags or files on disk.
Run list_folders once after setup to confirm the exact Sent/Drafts folder names your mailbox uses — some providers localize or rename them.
TITAN_ALLOW_SEND=false until you've watched Claude use the mailbox and trust the behavior. You can flip it on later with no code changes.npm install
npm run build # tsc -> dist/
npm start # run the built server directly (reads env vars from your shell)
The server speaks MCP over stdio (StdioServerTransport) — it's not an HTTP service, so running it directly just blocks waiting for a client on stdin.
Releasing a new version (maintainers): bump version in package.json (and the matching version fields in server.json), run npm run build to confirm it compiles, commit and push, then npm publish from titan-mcp/. The package only ships dist/, README.md, and LICENSE (see files in package.json) — source TypeScript stays GitHub-only. After the npm publish lands, update the MCP Registry listing with mcp-publisher publish (requires mcp-publisher login github once per session — see the registry quickstart), then tag a GitHub release (gh release create vX.Y.Z) so Smithery's crawler picks up the new version via smithery.yaml.
Issues and PRs welcome at github.com/qmmughal/titan-email-mcp. If you add support for another Titan-based reseller, please add its hostnames to the provider preset table in src/index.ts and this README.
MCP server for Titan Email (IMAP/SMTP), tested and confirmed with GoDaddy mailboxes.
{ "mcpServers": { "io.github.qmmughal-titan-email-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ], "env": { "TITAN_EMAIL": "<value>", "TITAN_PASSWORD": "<secret>", "TITAN_PROVIDER": "<value>", "TITAN_FROM_NAME": "<value>", "TITAN_ALLOW_SEND": "<value>", "TITAN_SENT_FOLDER": "<value>", "TITAN_DRAFTS_FOLDER": "<value>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: TITAN_EMAIL, TITAN_PASSWORD, TITAN_PROVIDER, TITAN_FROM_NAME, TITAN_ALLOW_SEND, TITAN_SENT_FOLDER, TITAN_DRAFTS_FOLDER
Titan Email ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-10 MCP server for Titan Email (IMAP/SMTP), tested and confirmed with GoDaddy mailboxes.