官方说明7 个来源MCP 服务8 天前
agentmail-to/agentmail-mcp
📇 ☁️ - Email for AI agents: create inboxes on the fly to send, receive and act on email
在 GitHub 查看 ↗直链 · 无中转页
官方说明AgentMail MCP AgentMail has one MCP tool implementation, hosted at: Use that Streamable HTTP endpoint directly when your client supports remote MCP.
配置模板（请按你的客户端调整）
claude mcp add agentmail-mcp -- npx -y agentmail-mcp
这是根据仓库名生成的可粘贴骨架，命令行参数与包名请以该项目 README 为准。
- ★ 数取值
- 68 ★ · agentmail-to/agentmail-mcp · 取自 GitHub 搜索 API · （2026-10-16 20:00:20 核对）
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单（我们从中收集的条目之一） · 条目类型：MCP 服务
- 收录与活跃
- 收录于 2026-10-09 · 最近见到 2026-10-16 · 共见到 32 次 · 被 7 个来源列出
- 评分构成
- 综合分 703 · 68 ★ · 7 个来源 · mcp
常见问题（答案都来自我们的记录）
怎么安装？
我们【没有】从该仓库取到安装命令（我们的 install 覆盖率只有约 4%）。请看它的 README 或 releases 页。
它适合谁 / 用来做什么？
我们把它归在这些标签下: MCP 服务。标签来自条目自身，不是我们强加的分类。
谁维护它、还在更新吗？
仓库
agentmail-to/agentmail-mcp；我们收录于 2026-10-09；最近见到 2026-10-16。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。第三方质量标记
AgentMail MCP
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
AgentMail has one MCP tool implementation, hosted at:
Use that Streamable HTTP endpoint directly when your client supports remote MCP. It provides the current runtime tool catalog and supports the hosted server's existing OAuth and per-request API-key paths. See the AgentMail MCP documentation.
stdio compatibility
Existing Node configurations continue to work through the npm bridge:
Python users can run the equivalent native bridge:
Both bridges discover tools and schemas from the hosted server. They do not contain AgentMail SDK, toolkit, REST API, or tool-definition logic. --tools name1,name2 remains available for stdio clients that need a filtered catalog.
Repository
- packages/server: the hosted MCP server and only AgentMail tool implementation
- packages/npm-stdio-bridge: npm agentmail-mcp
- python/stdio-bridge: PyPI agentmail-mcp
- mcp-manifest.json: generated runtime contract
- tests: contract and transport checks
- docs: architecture, compatibility, migration, release, and operations
The old local npm implementation is preserved at legacy-local-v0.2.2. Authentication hardening is a separate project; this consolidation preserves the hosted server's existing behavior.
Use that Streamable HTTP endpoint directly when your client supports remote MCP. It provides the current runtime tool catalog and supports the hosted server's existing OAuth and per-request API-key paths. See the AgentMail MCP documentation.
stdio compatibility
Existing Node configurations continue to work through the npm bridge:
Python users can run the equivalent native bridge:
Both bridges discover tools and schemas from the hosted server. They do not contain AgentMail SDK, toolkit, REST API, or tool-definition logic. --tools name1,name2 remains available for stdio clients that need a filtered catalog.
Repository
- packages/server: the hosted MCP server and only AgentMail tool implementation
- packages/npm-stdio-bridge: npm agentmail-mcp
- python/stdio-bridge: PyPI agentmail-mcp
- mcp-manifest.json: generated runtime contract
- tests: contract and transport checks
- docs: architecture, compatibility, migration, release, and operations
The old local npm implementation is preserved at legacy-local-v0.2.2. Authentication hardening is a separate project; this consolidation preserves the hosted server's existing behavior.
- 来源
- awesome · https://github.com/agentmail-to/agentmail-mcp
- 按领域浏览
- MCP 服务
- Traction
- 68 ★
- 收录于
- 昨天
更多MCP 服务
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。