techtv-mail

techtv-mail

Enables Claude/Cowork to read and send email through a cPanel-hosted IMAP/SMTP mailbox, providing tools to list folders, search messages, fetch message content, and send email as that mailbox.

Category
Visit Server

README

techtv-mail — a Cowork connector for pete@techtv.live

This is a small MCP server that lets Claude (Cowork) read and send email through your cPanel-hosted pete@techtv.live mailbox — the same way it already works with your Microsoft 365 and Gmail accounts, just built specifically for this mailbox since Anthropic doesn't have a pre-built connector for generic IMAP/cPanel mail.

It exposes four tools to Claude:

  • list_folders — see what mail folders exist
  • search_emails — search a folder by sender, subject, body text, or recency
  • get_email — fetch the full text/html of one message
  • send_email — send mail as pete@techtv.live

1. Deploy it somewhere that's always on

This needs to live on a small server that's reachable over the public internet 24/7 — it can't live on your own computer or in a Claude session, since both go offline. The cheapest, simplest options for something this small:

  • Railway (railway.app) — free/cheap tier, deploys straight from a zip or a GitHub repo, sets PORT for you automatically.
  • Render (render.com) — similar, has a free tier for small services (may sleep when idle on the free tier, which adds a few seconds' delay on the first request after a while).
  • A small VPS you already have, if you'd rather run it yourself.

Whichever you pick, the steps are the same shape:

  1. Upload this folder (or push it to a GitHub repo and connect that repo).
  2. Set it to run npm install then npm start (or node server.js).
  3. Set the environment variables below in that host's dashboard — never put real credentials in the code or commit them to git.
  4. Once deployed, the host gives you a public URL, e.g. https://techtv-mail-production.up.railway.app.

2. Environment variables to set on the host

Variable Value
MAIL_HOST mail.techtv.live
IMAP_PORT 993
SMTP_PORT 465
EMAIL_USER pete@techtv.live
EMAIL_PASS the mailbox's real password
ACCESS_TOKEN a long random string — see below

To generate a good ACCESS_TOKEN, run this on any machine with Node or just use a password generator for something like 40+ random characters:

node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"

This token becomes part of the server's URL and is the only thing standing between the public internet and your mailbox, so treat it exactly like a password — long, random, never shared, never posted anywhere public.

3. Add it to Cowork as a custom connector

Once deployed, in the Claude app:

  1. Go to Customize > Connectors (or click "+" / type "/" in a chat and choose "Manage connectors").

  2. Click + to browse, then Add custom connector.

  3. For the server URL, enter:

    https://<your-host-domain>/mcp/<ACCESS_TOKEN>
    

    (both pieces come from your deployment — the domain your host gave you, and the token you set as an environment variable).

  4. Leave the OAuth Client ID/Secret fields blank — this server doesn't use OAuth, the token in the URL is the access control.

  5. Save/Connect. Claude should now list list_folders, search_emails, get_email, and send_email as available tools whenever this connector is enabled in a chat.

Security notes

  • The mailbox password only ever lives in the host's environment variables — it's never in this code, never typed into a chat with Claude.
  • Anyone who obtains the full connector URL (including the token) could use these tools against the mailbox, so don't paste that URL anywhere public (a shared doc, a public repo, a Slack channel others can see).
  • If you ever suspect the URL has leaked, generate a new ACCESS_TOKEN, update it on the host, and re-enter the new URL in Cowork's connector settings — the old URL stops working immediately.
  • This mailbox's actual password should also just live in your password manager as normal; this server needs it once, at deploy time, as an environment variable.

Local test (optional, before deploying)

You can run it locally first to make sure your real credentials work:

npm install
MAIL_HOST=mail.techtv.live IMAP_PORT=993 SMTP_PORT=465 \
EMAIL_USER=pete@techtv.live EMAIL_PASS='<real password>' \
ACCESS_TOKEN=test123 PORT=3000 node server.js

Then in another terminal:

curl -s -X POST http://localhost:3000/mcp/test123 \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}'

A successful response looks like a result block naming the server — if instead you get an authentication error, double check EMAIL_PASS and that IMAP/SMTP access isn't blocked for this mailbox in cPanel.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured