Click on "Install 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., "@Tencent Mail Agent MCP Server list yesterday's emails"
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.
這是一個基於 Model Context Protocol (MCP) 的伺服器，提供從 騰訊企業郵 (Tencent Exmail) 或任何支援 IMAP 協定的郵件服務中獲取並分析郵件的工具。此伺服器旨在與 Claude Desktop 等 MCP 客戶端配合使用。
list_yesterday_emails: 獲取昨天的郵件。
自動依據日期範圍過濾（SINCE 昨天, BEFORE 今天）。
回傳的 metadata 包含：UID、寄件者 (From)、主旨 (Subject)、日期 (Date) 以及內文片段 (snippet，前 500 個字元)。
效能優化：預設限制獲取最新的 100 封郵件（可設定）。
Related MCP server: IMAP/SMTP Email MCP Server
複製專案庫：
git clone <repository-url>
cd mail-agent-mcp安裝依賴套件：
npm install編譯專案：
npm run build將 .env.example 複製並重新命名為 .env：
cp .env.example .env編輯 .env 並提供您的郵件登入資訊：
EMAIL_USER=your-email@example.com
EMAIL_PASSWORD=your-app-password
EMAIL_HOST=imap.exmail.qq.com
EMAIL_PORT=993對於騰訊企業郵，如果您啟用了兩階段驗證 (2FA)，則需要使用應用專用密碼 (App Password)。
npm run devnpm start若要將此伺服器加入 Claude Desktop，請在您的 claude_desktop_config.json 中新增以下設定：
{
"mcpServers": {
"mail-agent": {
"command": "node",
"args": ["/絕對路徑/至/mail-agent-mcp/dist/index.js"],
"env": {
"EMAIL_USER": "your-email@example.com",
"EMAIL_PASSWORD": "your-app-password",
"EMAIL_HOST": "imap.exmail.qq.com",
"EMAIL_PORT": "993"
}
}
}
}ISC
Fetch emails received yesterday. Limited to the latest 100 emails to ensure performance.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of emails to fetch (default: 100) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses a limit of 100 emails and mentions performance as a rationale, which is useful. However, it does not state whether the operation is read-only, how results are ordered, or what fields are returned, leaving notable behavioral aspects undisclosed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two concise sentences, front-loaded with the core purpose and a brief performance rationale. No wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with one optional parameter and no siblings, but the description omits important context such as timezone handling for 'yesterday', result ordering, and what email data is included. It is adequate but leaves several gaps that could affect correct usage.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already documents the limit parameter. The description adds 'Limited to the latest 100 emails' but this conflicts with the schema's configurable limit parameter, potentially misleading the agent into thinking the limit is fixed at 100. This adds negative value rather than clarifying parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool fetches emails received yesterday, with a specific verb ('Fetch') and resource ('emails received yesterday'). It is unambiguous and distinguishes this tool from potential siblings by specifying the time scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for retrieving yesterday's emails but does not explicitly state when to use it versus alternatives, nor any exclusions. With no sibling tools provided, the lack of explicit guidance is less critical, but still a gap.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.0list_yesterday_emailsScored across 1 tool
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is singular and clear.
The single tool name 'list_yesterday_emails' follows a clear verb_noun pattern and is descriptive. Consistency is trivially maintained.
One tool feels thin for a mail server, but it is not entirely trivial—it does one specific task. The count is borderline and could be part of a larger intended set.
The server appears to be for email management, yet it only lists yesterday's emails. Missing send, read, search, and other lifecycle operations represent severe gaps for the domain.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Connect any mailbox to Claude, ChatGPT & AI: read, send, reply, schedule & search emails.
Task-scoped email inboxes for AI agents: read mail, extract verification codes, and reply.
Email inboxes for AI agents: send, receive, reply, search, and manage threaded email over MCP.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wuenhouse/mail-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
