Let an AI assistant drive your client
eMule Qt speaks the Model Context Protocol (MCP), the open standard AI assistants use to work with other programs. Switch it on and an assistant such as Claude can look at your client and act on it: “what is still downloading?”, “search Kad for this and queue the result with the most sources”, “pause everything in the Video category”.
What an assistant can do
The daemon offers 51 tools, chosen for what an assistant actually needs:
- Status — connection, Kademlia, firewall and port state, statistics and the log.
- Search — start a search, read the results and download straight from them. Results carry the fake-file verdict, so the assistant is told which ones to doubt and why.
- Downloads — list, add, pause, resume, stop and cancel, see a download’s sources, clear completed.
- Servers and Kad — list, add, remove and connect to servers, start and stop Kad, import nodes.
- Sharing — shared files and directories, uploads and the upload queue.
- Usenet — the Usenet queue, adding an NZB by URL and acting on a release.
- Categories and preferences — read them, and change them where the schema says they are writable.
The same code as the REST API
MCP is not a second implementation. Every tool is an entry of the same operation table that produces the REST API, so a tool call is validated and carried out exactly like the matching HTTP request: an unknown field or a value out of range is refused, not ignored. Destructive calls — cancelling a download, removing a release — must say "confirm": true. Shutting the daemon down is not a tool at all.
Yours to open, and closed until you do
- Off by default — nothing listens for an assistant until you enable it.
- API key on every call — the same key as the REST API, and the server can run over HTTPS.
- Read-only mode — one switch, and the assistant is offered only the tools that change nothing. It can look at everything and touch none of it.
- No drive-by web pages — a request from a browser origin you have not allowed is refused.
- No secrets — credentials, API keys and anything that names a program or certificate cannot be read or set through the preferences tools.
Connecting an assistant
The endpoint is /mcp on the web server’s port (default 4711), over streamable HTTP. A client that speaks HTTP connects directly — Claude Code, for example:
claude mcp add --transport http emuleqt http://localhost:4711/mcp --header "Authorization: Bearer <api key>"
A client that can only start a local program uses the small bridge emuleqt-mcp, which ships next to the daemon in every download. It reads the port and the key from your local configuration, so there is nothing to type:
{ "mcpServers": { "emuleqt": { "command": "/path/to/emuleqt-mcp" } } }
The bridge also reaches a daemon on another machine:
emuleqt-mcp --url https://nas.example:4711/mcp --api-key <key>
eMule Qt implements MCP revision 2026-07-28. A client that only knows an older revision is told so in plain words instead of failing silently.