email-tool
Email for any AI agent that speaks MCP: Claude Code, Claude Desktop, Cowork, ChatGPT desktop, Codex and others.
Read, search, draft and send mail, with attachments, over IMAP/SMTP.
Works with
Compliance
Build and security
Code quality
Project
email-tool lets an AI assistant read, search, draft and send your email. It runs on your own computer, keeps passwords in your operating system's keyring, and is built for organizations under CMMC Level 2 and NIST SP 800-171: every action is logged, sending can wait for your approval, and CUI-marked mail stays inside the domains you allow.
Documentation: skhan61.github.io/email-tool
Quick start
No terminal, any app: Start here. Install email-tool in your app (Claude Desktop and Cowork: one file to open; ChatGPT desktop and Codex: one installer to open), then ask your assistant to "add my mailbox".
From a terminal:
-
Install uv.
-
Connect your AI app. In Claude Code:
/plugin marketplace add skhan61/email-tool /plugin install email-tool@email-tool
Other apps: Advanced setup.
-
Ask your assistant to "add my mailbox", or from a terminal:
uv tool install git+https://github.com/skhan61/email-tool email-tool-mcp add work --auth microsoft --address you@company.com
Gmail, Google Workspace and other accounts: Mailbox details.
Documentation
| Page | What it covers |
|---|---|
| Start here | Install in any app and add a mailbox, no terminal |
| Everyday use | What to ask, the tools, approving before sending |
| Mailbox details | What each mailbox needs (Gmail App Password, Microsoft, GCC High, Google Workspace, others), and the terminal steps |
| Advanced setup | uv by hand, configuration files, ChatGPT Business, other MCP apps, update or remove |
| Why CMMC | Each protection, with examples |
| CMMC control mapping | NIST SP 800-171 requirements, evidence and your part |
| For administrators | Policy, audit log, FIPS mode, your own Microsoft or Google app |
| Troubleshooting | Every message and its fix |
| Privacy | What email-tool accesses and where it goes |
Contributing and security
See CONTRIBUTING.md. Report vulnerabilities privately as described in SECURITY.md.
License
1 maintainer
Metadata
1 maintainer
Release files for email-tool-mcp 5.4.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| email_tool_mcp-5.4.2.tar.gz | 1.6 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| email_tool_mcp-5.4.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.7 MB
Release files / email_tool_mcp-5.4.2.tar.gz
| Download URL | email_tool_mcp-5.4.2.tar.gz |
|---|---|
| Size | 1.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
15145c5e59ca8b7089fddf3e25c6538a90962d8be91d6b280ea958a01670ed89
|
|
BLAKE2b-256 checksum How to use checksums |
16bf6aecb5dc71c3fde4e64a1e3f36f862138ae1fde6e9665b273c47fc8ba2bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / email_tool_mcp-5.4.2-py3-none-any.whl
| Download URL | email_tool_mcp-5.4.2-py3-none-any.whl |
|---|---|
| Size | 85.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5bd0cc534b78a253129c7eb828f84f952f9b911151b527dd87a800c0a381aaa5
|
|
BLAKE2b-256 checksum How to use checksums |
51b1e2a620d2ec99c631457aa0807e57a42d0f7f5f458848102520e677c622bd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for email-tool-mcp 5.4.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for email_tool_mcp-5.4.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
