imap-mcp-manual

스타9

포크13

업데이트2026년 7월 19일 08:12

Progressive-disclosure usage manual for the IMAP/SMTP email MCP tool. Read this when you need detail beyond the one-line action descriptions: send vs reply, check/read/search over folders, the compound email_id (account:folder:uid), attachments, move/flag/delete/folders, contacts/accounts basics, and the important external-email side-effect caveats (real outbound mail — confirm before sending). Pulled on demand via action='manual'; you do not need to call it before every send.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

Lingtai-AI

Lingtai-AI/lingtai-kernel

GitHub 저장소 열기 Creator 저장소 보기

다운로드

IMAP/SMTP email MCP — usage manual (progressive disclosure)

Pulled on demand via action='manual'; read it for detail beyond the tool schema's one-line action descriptions.

ACTIONS

Action	Purpose	Arguments
`send`	compose a new email	`address`, `message`; optional `subject`, `cc`, `bcc`, `attachments`
`reply`	reply to an existing email; preserves threading/subject from the original	`email_id`, `message`; optional `cc`, `attachments`
`check`	list recent envelopes from a folder	optional `folder`, `n`
`read`	fetch full email(s)	`email_id`
`search`	server-side IMAP search	`query`; optional `folder`
`folders`	list available IMAP folders	—
`move`	move email(s) to another folder	`email_id`, `folder` (destination)
`flag`	set/clear flags	`email_id`, `flags`
`delete`	delete email(s)	`email_id`
`contacts`	list all contacts	—
`add_contact`	add/update a contact	`address`, `name`; optional `note`
`edit_contact`	update contact fields	`address`; optional `name`, `note`
`remove_contact`	remove a contact	`address`
`accounts`	list configured IMAP accounts and connection status	—

address/cc/bcc accept a single string or a list; email_id takes one id or a list of ids.

IDS, FOLDERS, ACCOUNTS

email_id is a compound key: account:folder:uid (e.g. me@example.com:INBOX:1234). Use the ids returned by check/search; do not construct them by hand.
An empty or whitespace-only folder (check/search) or account (any action) is treated as omitted: folder defaults to INBOX, and account uses the default/sole account rather than failing with Unknown account. Most actions accept an optional account (email address), defaulting to the primary account. move is the exception — its destination folder is required, must be non-empty, and is never defaulted to INBOX.
flags is required for flag and maps flag name to bool, e.g. flags={"seen": true, "flagged": false}; flags={"seen": true} marks read. A missing or empty flags returns an error rather than silently doing nothing.
search queries use a server-side search DSL, e.g. from:addr subject:text unseen since:YYYY-MM-DD; supported fields depend on the IMAP addon, so prefer examples returned by this tool over raw RFC IMAP search syntax.

READING & ATTACHMENTS

You are encouraged to read multiple relevant — or even all unread — emails and think before acting.
attachments is a list of file paths (absolute or relative to the working dir) for send/reply. Attach generated artifacts (charts, reports, CSVs, PDFs) as files rather than pasting a path into the body.

SIDE EFFECTS & SAFETY

send and reply deliver real email to real recipients over SMTP — this is an external, hard-to-undo side effect. Confirm the recipient list (including cc/bcc) and the body before sending unsolicited mail.
When replying to external addresses, follow the caller's standing reply policy. Unknown external senders require explicit guidance, or confirmation that the sender is the same human who contacted you through an internal channel, before sending a real reply.
delete and move change server-side mailbox state; double-check the email_id/folder before running them.
Actions return a result dict on success or one carrying an 'error' key on failure (e.g. unknown account, bad email_id, unreadable attachment). Check for the error and surface or act on it rather than assuming delivery.

이 저장소의 다른 Skills

같은 저장소

lingtai-doctor

Lingtai-AI/lingtai-kernel

Read-only health diagnostics for LingTai agents and bots. Use when an agent appears offline or unreachable, when a machine migration may have left stale MCP/addon command paths, when heartbeat/status/process/notification/log surfaces disagree, or before deciding whether to mail, refresh, CPR, or edit persistent configuration. Includes a bundled doctor.py script for layered local checks without exposing secrets.

2026-07-199

environment-variables

Lingtai-AI/lingtai-kernel

Complete catalogue of environment variables consumed by the LingTai kernel, wrapper, bundled MCPs, adapters, tests, and daemon composition surfaces.

2026-07-199

system-manual

Lingtai-AI/lingtai-kernel

Second-layer router for LingTai's progressive-disclosure operating manuals. Read this when resident substrate/procedures are too compact and you need the right lower reference. Route here for the expanded substrate/runtime model, lifecycle and `system` tool actions, the init.json composition and preset runtime model route, action/procedure discipline and skill routing, tool-result summarization, SQLite/`log.sqlite` trace inspection and trajectory mining, runtime/kernel update checks and nudges, environment variables, goal notifications, molt/memory questions, MCP/addon ownership, collaboration topology, and resident prompt design. The nested catalog below names each reference and its exact trigger.

2026-07-199

lingtai-kernel-dev

Lingtai-AI/lingtai-kernel

Mandatory repository-local development guide for LingTai's Python kernel and runtime. Use this before changing code, architecture documents, tests, packaging, capabilities, adapters, or developer documentation in lingtai-kernel. Routes each task through the exact baseline, the distributed ANATOMY/CONTRACT systems, focused validation, and pull-request safety gates.

2026-07-199

file-manual

Lingtai-AI/lingtai-kernel

Operational guide for LingTai's built-in file tools: read, write, edit, glob, and grep. Use when working with local text files, deciding whether to use file tools versus bash, handling large files, avoiding binary/image misuse, or reading non-UTF-8 text via explicit bash/Python/iconv instead of complicating the core read tool. Covers UTF-8 policy, safe write/edit discipline, search workflows, and examples for GBK/Shift-JIS/Latin-1 conversion.

2026-07-199

lingtai-kernel-anatomy

Lingtai-AI/lingtai-kernel

Router for LingTai's distributed code navigation system. Use this before navigating, creating, or maintaining kernel ANATOMY.md files. The normative anatomy-of-anatomy now lives at the repository-root ANATOMY.md; this skill explains how an agent enters and descends that graph, how it pairs with the distributed CONTRACT.md interface-definition graph, and what to do when code and navigation disagree.

2026-07-199

name	imap-mcp-manual
description	Progressive-disclosure usage manual for the IMAP/SMTP email MCP tool. Read this when you need detail beyond the one-line action descriptions: send vs reply, check/read/search over folders, the compound email_id (account:folder:uid), attachments, move/flag/delete/folders, contacts/accounts basics, and the important external-email side-effect caveats (real outbound mail — confirm before sending). Pulled on demand via action='manual'; you do not need to call it before every send.
version	1.0.0
last_changed_at	"2026-07-19T00:00:00.000Z"
related_files	["src/lingtai/mcp_servers/imap/manager.py","src/lingtai/mcp_servers/imap/server.py","src/lingtai/mcp_servers/imap/service.py"]
maintenance	Tracks the MCP server's manager/config behavior; update when the server's setup or API surface changes.

IMAP/SMTP email MCP — usage manual (progressive disclosure)

Pulled on demand via action='manual'; read it for detail beyond the tool schema's one-line action descriptions.

ACTIONS

Action	Purpose	Arguments
`send`	compose a new email	`address`, `message`; optional `subject`, `cc`, `bcc`, `attachments`
`reply`	reply to an existing email; preserves threading/subject from the original	`email_id`, `message`; optional `cc`, `attachments`
`check`	list recent envelopes from a folder	optional `folder`, `n`
`read`	fetch full email(s)	`email_id`
`search`	server-side IMAP search	`query`; optional `folder`
`folders`	list available IMAP folders	—
`move`	move email(s) to another folder	`email_id`, `folder` (destination)
`flag`	set/clear flags	`email_id`, `flags`
`delete`	delete email(s)	`email_id`
`contacts`	list all contacts	—
`add_contact`	add/update a contact	`address`, `name`; optional `note`
`edit_contact`	update contact fields	`address`; optional `name`, `note`
`remove_contact`	remove a contact	`address`
`accounts`	list configured IMAP accounts and connection status	—

address/cc/bcc accept a single string or a list; email_id takes one id or a list of ids.

IDS, FOLDERS, ACCOUNTS

email_id is a compound key: account:folder:uid (e.g. me@example.com:INBOX:1234). Use the ids returned by check/search; do not construct them by hand.
An empty or whitespace-only folder (check/search) or account (any action) is treated as omitted: folder defaults to INBOX, and account uses the default/sole account rather than failing with Unknown account. Most actions accept an optional account (email address), defaulting to the primary account. move is the exception — its destination folder is required, must be non-empty, and is never defaulted to INBOX.
flags is required for flag and maps flag name to bool, e.g. flags={"seen": true, "flagged": false}; flags={"seen": true} marks read. A missing or empty flags returns an error rather than silently doing nothing.
search queries use a server-side search DSL, e.g. from:addr subject:text unseen since:YYYY-MM-DD; supported fields depend on the IMAP addon, so prefer examples returned by this tool over raw RFC IMAP search syntax.

READING & ATTACHMENTS

You are encouraged to read multiple relevant — or even all unread — emails and think before acting.
attachments is a list of file paths (absolute or relative to the working dir) for send/reply. Attach generated artifacts (charts, reports, CSVs, PDFs) as files rather than pasting a path into the body.

SIDE EFFECTS & SAFETY

send and reply deliver real email to real recipients over SMTP — this is an external, hard-to-undo side effect. Confirm the recipient list (including cc/bcc) and the body before sending unsolicited mail.
When replying to external addresses, follow the caller's standing reply policy. Unknown external senders require explicit guidance, or confirmation that the sender is the same human who contacted you through an internal channel, before sending a real reply.
delete and move change server-side mailbox state; double-check the email_id/folder before running them.
Actions return a result dict on success or one carrying an 'error' key on failure (e.g. unknown account, bad email_id, unreadable attachment). Check for the error and surface or act on it rather than assuming delivery.