titan-email-mcp 1.0.0 → 1.0.2

package/README.md

@@ -1,16 +1,26 @@
 # Titan Email MCP
 
+[![npm version](https://img.shields.io/npm/v/titan-email-mcp.svg)](https://www.npmjs.com/package/titan-email-mcp)
+[![npm downloads](https://img.shields.io/npm/dm/titan-email-mcp.svg)](https://www.npmjs.com/package/titan-email-mcp)
+[![CI](https://github.com/qmmughal/titan-email-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/qmmughal/titan-email-mcp/actions/workflows/ci.yml)
+[![license](https://img.shields.io/npm/l/titan-email-mcp.svg)](LICENSE)
+
 Connect Claude — Desktop, Code, Cursor, or any [MCP](https://modelcontextprotocol.io) client — directly to a **Titan Email** mailbox, so it can read, search, triage, and send mail on your behalf.
 
+Package: [npmjs.com/package/titan-email-mcp](https://www.npmjs.com/package/titan-email-mcp) · Source: [github.com/qmmughal/titan-email-mcp](https://github.com/qmmughal/titan-email-mcp)
+
 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](#why-use-this) · [Supported providers](#supported-providers) · [Tools](#tools) · [Quick start](#quick-start) · [Configuration](#configuration) · [Security notes](#security-notes) · [Troubleshooting](#troubleshooting) · [Development](#development) · [Contributing](#contributing) · [License](#license)
+
 ## Why use this
 
 - **Your inbox becomes an agent tool.** Ask Claude to summarize unread mail, draft replies in your voice, triage by sender, or find "that invoice from last March" — in plain English, in the same conversation you're already having.
 - **Works with GoDaddy-hosted Titan mailboxes.** If you bought your domain and mailbox through GoDaddy, your email is very likely running on Titan's infrastructure under the hood. One `TITAN_PROVIDER` setting handles the different server hostnames — see [Supported providers](#supported-providers).
 - **Safe by default.** Sending is gated behind `TITAN_ALLOW_SEND` (default **on**, but trivially switched **off**) so you can run Claude in read-only / draft-only mode until you trust it.
 - **No middleman service.** Credentials go straight from your MCP client's local config to Titan's own IMAP/SMTP servers over TLS. Nothing is proxied through a third party, cached, or logged to disk.
-- **One process, nine focused tools.** No bloated API surface — just the operations you actually do in a mailbox (see [Tools](#tools) below).
+- **One process, ten focused tools.** No bloated API surface — just the operations you actually do in a mailbox (see [Tools](#tools) below).
+- **Published on npm.** Run it with `npx titan-email-mcp` — no cloning or building required for everyday use.
 
 ## Supported providers
 
@@ -42,16 +52,17 @@ If your reseller uses yet another hostname, leave `TITAN_PROVIDER` unset and ove
 
 **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. Clone and build:**
+**2. Get the server** — either works, pick one:
 
-```bash
-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`, which your MCP client launches as a subprocess. Note the **absolute path** to it — you'll need it below.
+- **npx (no install step)** — your MCP client runs `npx titan-email-mcp` directly; npm fetches it on first use and caches it. This is the path used in the config examples below.
+- **Clone and build**, if you want to read/modify the source first:
+  ```bash
+  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.
 
@@ -65,8 +76,8 @@ Edit your `claude_desktop_config.json` ([config file location](https://modelcont
 {
   "mcpServers": {
     "titan-email": {
-      "command": "node",
-      "args": ["/absolute/path/to/titan-email-mcp/titan-mcp/dist/index.js"],
+      "command": "npx",
+      "args": ["-y", "titan-email-mcp"],
       "env": {
         "TITAN_EMAIL": "you@yourdomain.com",
         "TITAN_PASSWORD": "your-password",
@@ -79,6 +90,8 @@ Edit your `claude_desktop_config.json` ([config file location](https://modelcont
 }
 ```
 
+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 Code
 
 ```bash
@@ -88,7 +101,7 @@ claude mcp add titan-email --scope user \
   -e TITAN_PROVIDER=titan \
   -e TITAN_FROM_NAME="Your Name" \
   -e TITAN_ALLOW_SEND=false \
-  -- node /absolute/path/to/titan-email-mcp/titan-mcp/dist/index.js
+  -- 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).
@@ -143,6 +156,8 @@ 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`, 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.
+
 ## Contributing
 
 Issues and PRs welcome at [github.com/qmmughal/titan-email-mcp](https://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.

package/package.json

@@ -1,7 +1,8 @@
 {
   "name": "titan-email-mcp",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "MCP server that connects Claude (or any MCP client) to a Titan Email mailbox over IMAP/SMTP — including Titan accounts resold through GoDaddy.",
+  "mcpName": "io.github.qmmughal/titan-email-mcp",
   "main": "dist/index.js",
   "type": "module",
   "bin": {