AI Agent Hub
Back to plugins
🧰

dsh-qqmail

Web Tools Updated 2026.09.16

Run the following command in DeepSeek Harness:

dsh plugin install zhengjy01/dsh-qqmail

Paste the following prompt into your AI chat to install this plugin:

Install the QQ Mail agent-tool plugin in DeepSeek Harness by running dsh plugin install zhengjy01/dsh-qqmail, with the full source available at https://github.com/zhengjy01/dsh-qqmail

About this plugin

dsh-qqmail gives a DeepSeek Harness agent direct hands on a mailbox: list, search, read, send, reply, flag, move, and delete email over plain IMAP/SMTP, removing the need for a human to relay messages. Authentication uses a 16-character provider authorization code rather than OAuth, so there is no application registration, no 2FA redirect, and no browser round trip. The code is written to a local file with 0600 permissions and never appears in tool results, the settings panel, or logs.

The plugin registers in read-only mode by default — write tools such as send, delete, and move are absent from the tool registry entirely, not merely refused at call time. Deletion moves mail to the Trash folder unless permanent: true is passed explicitly. Chinese keyword searches are handled by scanning a recent window of roughly 400 messages locally, sidestepping the silent zero-match that server-side IMAP SEARCH would return when no charset negotiation is honoured.

Beyond the primary agent-tool entry point, the same core is exposed as a CLI (with --json for structured output) and as an MCP stdio server, so agents that cannot host a DSH plugin can consume the identical tool schemas. It is aimed at developers building email automation on DeepSeek Harness and at teams that need a single, reusable mailbox backend for multiple agents.

Use Cases

  • Automatically read, search, and reply to work email via agent
  • Batch-organize inbox, download attachments, and archive messages
  • Multiple agents share one mailbox backend over MCP

Best For

  • Developers building email automation on DeepSeek Harness
  • Teams that need a unified mailbox backend for LLM agents
  • Users of other agent frameworks consuming tools via MCP