Provides calendar event extraction and event creation support; on non-Mac systems, generates an .ics file and a Google Calendar link to add events.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@webmail-mcp summarize the latest emails in my IIT Delhi inbox"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Your IIT Delhi mailbox, in the AI assistant you already use.
Connect once. ChatGPT, Claude, Gemini, Cursor, or any other MCP client can read your institute mail and send from it. The mail password stays on the machine that runs this server. The assistant only gets a token.
The hosted site is webmail-mcp.ariesiitd.com. This repository is the same program, for people who want to run it themselves.
MIT licensed.
You need Python 3.11 or newer.
git clone https://github.com/rizzhubsane/webmail-mcp
cd webmail-mcp
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
webmail-mcp init
webmail-mcp connector iitd --username YOUR_KERBEROS_ID
webmail-mcp enable-send
webmail-mcp token create --name mine --scope read --scope draft --scope sendconnector iitd asks for the webmail password in the terminal. It checks the password with IIT Delhi mail, then stores it encrypted under ~/.assistant-bridge. That directory is mode 0700. master.key is mode 0600. The token is printed once. The disk keeps a hash of it.
Do not type the mail password into a chat. Do not commit master.key, vault.json, accounts.json, oidc.json, or a token.
Point the assistant at the local process. An example is in config/mcp.example.json.
webmail-mcp mcpwebmail-mcp serve listens on 127.0.0.1 only. Binding 0.0.0.0 is refused unless the process is running as an Azure web app.
A demo inbox needs no mail password:
webmail-mcp init
webmail-mcp connector mock
webmail-mcp token create --name demo --scope read --scope draftRelated MCP server: simple-email-mcp
The assistant calls these tools. You talk normally.
You ask | Tool |
What came in? |
|
Find the mail I sent |
|
Draft a reply |
|
Send it |
|
Mail this professor |
|
Show the thread |
|
Put it on my calendar |
|
When you say send, it sends. A leftover [placeholder] still blocks the send. Adding an event to the Mac Calendar app works on a Mac. Everywhere else you get an .ics file and a Google Calendar link.
read can look at mail. draft can write a draft. send can transmit it. Create the token with only the scopes you want.
pytestThe tests do not contact IIT Delhi mail servers.
On the hosted site, the mail password is stored encrypted for your Kerberos id. DevClub sign-in confirms who you are. It does not hand over the mail password. The assistant never receives the password.
If you self-host, that password stays on your computer.
Details for the hosted site are at webmail-mcp.ariesiitd.com/privacy.
This server cannot be deployed
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Email inboxes for AI agents: send, receive, reply, search, and manage threaded email over MCP.
Hosted email MCP for your own Gmail, Outlook.com, Microsoft 365, iCloud or IMAP inbox: read, search, draft, reply in thread, forward and file mail. It moves or flags up to 500 messages in one call, and a send leaves exactly one copy in Sent. A calendar is a separate connection, and connecting one adds diary and scheduling tools.
Your agent needs a mailbox of its own — to receive, thread, draft and send, with attachments, without borrowing your personal inbox or your company's SMTP. **What you can ask for** • "Create an inbox for this agent and tell me its address." • "Read the new messages in this thread and draft a reply." • "Send this message with the attachment and wait for the response." • "Search this inbox for everything from that domain." • "Show delivery metrics and the events on this inbox." **How to use it** Point any MCP client at https://mcp.aisa.one/mail/mcp and sign in with OAuth — there is no key to create or paste. 49 tools: create and delete inboxes, list and read messages, raw message bodies, attachments, threads, drafts and draft attachments, send and reply, message search, inbox events, metrics, and list entries — reads and writes. **Why this rather than the source** A real inbox an agent owns, rather than an SMTP credential it borrows from a human. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the contact elsewhere in the catalogue, then write to them from here — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/sales/mcp finds the person to write to.
