cloud-mail-mcp-manual

Stars9

Forks13

UpdatedJuly 19, 2026 at 08:12

Progressive-disclosure usage manual for the Cloud Mail REST email MCP tool. Read this when you need detail beyond the one-line action descriptions: check/search filters, the compound id (account:emailId) for read, send (needs user credentials), plain vs HTML bodies, accounts/add_user basics, and the external-email side-effect caveats. Pulled on demand via action='manual'; you do not need to call it before every send.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

Lingtai-AI

Lingtai-AI/lingtai-kernel

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

8 files

SKILL.md

readonly

name	cloud-mail-mcp-manual
description	Progressive-disclosure usage manual for the Cloud Mail REST email MCP tool. Read this when you need detail beyond the one-line action descriptions: check/search filters, the compound id (account:emailId) for read, send (needs user credentials), plain vs HTML bodies, accounts/add_user basics, and the external-email side-effect caveats. 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:00Z
related_files	["src/lingtai/mcp_servers/cloud_mail/manager.py","src/lingtai/mcp_servers/cloud_mail/server.py","src/lingtai/mcp_servers/cloud_mail/client.py"]
maintenance	Tracks the MCP server's manager/config behavior; update when the server's setup or API surface changes.

Cloud Mail MCP — usage manual (progressive disclosure)

Inbound mail also arrives automatically in your inbox via per-account polling, so you don't have to poll check yourself.

Setup, config file/schema, credential and auth model, and watermark state are owned by the mcp-manual skill (reference/curated-addons.md, §Cloud Mail setup). Read it before editing config; do not guess field names.

EMAIL IDS

read fetches the full content of one email by compound id id='<account>:<emailId>', or by account plus a numeric email_id. Use the ids returned by check/search; do not construct them by hand.

READING: check / search

check: list recent inbound emails (optional limit/n, plus the same filters as search).
search: filter the public email list by to_email, send_email, send_name, subject, content, time_sort (asc/desc), and paginate with num/size. Filters are LIKE matches.

SEND

send requires user credentials in config (it logs in, then posts to /email/send). Provide address (recipient or list), and a body via message/text (plain) and/or html/content_html (HTML). Optional subject, name (sender display name), send_account_id (override sender).
Attachments are NOT supported in this first pass.

ACCOUNTS / ADD_USER

accounts: redacted per-account status (no tokens/passwords).
add_user: create a Cloud Mail user (email, password; optional role_name). Admin operation — use deliberately.

SIDE EFFECTS & SAFETY

send delivers real email to real recipients — an external, hard-to-undo side effect. Confirm the recipient(s) and body before sending unsolicited mail.
add_user mutates the Cloud Mail deployment's user set; double-check before running it.
Actions return {'status': 'ok', ...} on success or {'status': 'error', 'error': <message>} on failure. Check the status and surface or act on errors rather than assuming delivery.

More from this repository

same repository

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	cloud-mail-mcp-manual
description	Progressive-disclosure usage manual for the Cloud Mail REST email MCP tool. Read this when you need detail beyond the one-line action descriptions: check/search filters, the compound id (account:emailId) for read, send (needs user credentials), plain vs HTML bodies, accounts/add_user basics, and the external-email side-effect caveats. 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:00Z
related_files	["src/lingtai/mcp_servers/cloud_mail/manager.py","src/lingtai/mcp_servers/cloud_mail/server.py","src/lingtai/mcp_servers/cloud_mail/client.py"]
maintenance	Tracks the MCP server's manager/config behavior; update when the server's setup or API surface changes.

Cloud Mail MCP — usage manual (progressive disclosure)

Inbound mail also arrives automatically in your inbox via per-account polling, so you don't have to poll check yourself.

EMAIL IDS

read fetches the full content of one email by compound id id='<account>:<emailId>', or by account plus a numeric email_id. Use the ids returned by check/search; do not construct them by hand.

READING: check / search

check: list recent inbound emails (optional limit/n, plus the same filters as search).
search: filter the public email list by to_email, send_email, send_name, subject, content, time_sort (asc/desc), and paginate with num/size. Filters are LIKE matches.

SEND

send requires user credentials in config (it logs in, then posts to /email/send). Provide address (recipient or list), and a body via message/text (plain) and/or html/content_html (HTML). Optional subject, name (sender display name), send_account_id (override sender).
Attachments are NOT supported in this first pass.

ACCOUNTS / ADD_USER

accounts: redacted per-account status (no tokens/passwords).
add_user: create a Cloud Mail user (email, password; optional role_name). Admin operation — use deliberately.

SIDE EFFECTS & SAFETY

send delivers real email to real recipients — an external, hard-to-undo side effect. Confirm the recipient(s) and body before sending unsolicited mail.
add_user mutates the Cloud Mail deployment's user set; double-check before running it.
Actions return {'status': 'ok', ...} on success or {'status': 'error', 'error': <message>} on failure. Check the status and surface or act on errors rather than assuming delivery.