mu-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MUHOME | No | Passed to mu as `--muhome`; otherwise mu's normal configuration and `MUHOME` environment behavior apply. Optional. | |
| MU_BIN | No | Path to the mu executable. Optional; if omitted, mu is resolved normally. | |
| MU_MCP_TIMEOUT | No | Sets the per-command timeout in seconds. Optional; default is 30. | 30 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_mailA | Search the local mu-indexed mailbox using mu query syntax. Examples: "from:alice@example.com subject:invoice", "after:2025-01-01 before:2025-02-01", or "flag:unread". Returns at most 100 metadata records; local filesystem paths are excluded. |
| read_mailA | Read the first message matching a mu query; message output is truncated. Use a specific query such as "message-id:abc@example.com" or combine sender, subject, and date terms to identify the intended email. Returns headers and plain-text content. This tool does not modify the mailbox. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
search_mail returns metadata records while read_mail returns message content, so their core actions are distinct. However, both accept mu queries and an agent might initially attempt to use search_mail for reading, though descriptions clarify the limitations.
Both tool names follow the same snake_case verb_noun pattern: search_mail and read_mail. The convention is clear and consistently applied.
Two tools is quite thin for a mailbox server; while the read-only scope justifies minimalism, common operations like listing folders or fetching full messages are absent. The count feels borderline rather than well-scoped.
The surface covers basic search and read, but read_mail truncates output and there is no way to retrieve full messages or attachments. These are notable gaps for a mail retrieval tool, though read-only limits some expected operations.