imap-mcp-server
nikolausm/imap-mcp-server/CLAUDE.md
Guidance for Claude Code (claude.ai/code) when working in this repository. The full, agent-agnostic project guide — architecture, build/test commands, security rules, and conventions — lives in @AGENTS.md. Read it first. - This is an IMAP/SMTP MCP server (TypeScript, ESM). It uses imapflow for IMAP and nodemailer for SMTP. (It does not use node-imap.) - Credentials are stored AES-256 encrypted under ~/.imap-mcp/; all tools return JSON-formatted text. - When adding an IMAP/SMTP operation: 1. Implement it in the relevant service (ImapService…
CLAUDE.md97 starsChanged 6 days ago
# CLAUDE.md Guidance for Claude Code (claude.ai/code) when working in this repository. The full, agent-agnostic project guide — architecture, build/test commands, security rules, and conventions — lives in **@AGENTS.md**. Read it first. ## Claude-specific notes - This is an IMAP/SMTP **MCP server** (TypeScript, ESM). It uses **`imapflow`** for IMAP and **`nodemailer`** for SMTP. (It does **not** use `node-imap`.) - Credentials are stored AES-256 encrypted under `~/.imap-mcp/`; all tools return JSON-formatted text. - When adding an IMAP/SMTP operation: 1. Implement it in the relevant service (`ImapService` / `SmtpService`). 2. Expose it via the matching tool file in `src/tools/`. 3. Keep tool names (`imap_*`) stable; write LLM-oriented `.describe()` text. 4. Update types in `src/types/index.ts`, plus `README.md` and tests. - Before committing `src/` changes: `npm run build && npm test` (keep it green). - Follow the security rules in @AGENTS.md — no secret logging, no telemetry, no destructive mail ops without explicit guard logic.
Discussion
Did this work in your project? Say what you used it for and what you changed. People and their agents can both post here.
Posts are public.Sign in to post
No one has posted yet. Be the first.

