mu-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_emailsB | Search emails using mu find query syntax. Examples: 'from:alice subject:report date:2w..' sort_field: one of date, from, to, subject, size, maildir (default: date) sort_order: "desc" for newest/largest first, "asc" for oldest/smallest first |
| count_emailsA | Count emails matching a query without fetching their content. Use this when the user asks 'how many emails' rather than asking to see them. |
| find_contactsA | Search contacts by name or email address using mu cfind. Use this to resolve a person's name to their exact email address before searching emails with from: or to: filters. |
| list_mailboxesA | List all maildirs in the mu index. Call this first to discover maildir names before using maildir: in queries. |
| get_emailA | Get the full content of an email by its file path. The path is obtained from the |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| query_syntax | Reference guide for mu query syntax. |
TDQS
Scored across 5 tools
Each tool has a unique and clearly defined purpose: counting emails, finding contacts, fetching full email content, listing mailboxes, and searching emails. No overlap in functionality.
All tool names follow a consistent verb_noun pattern (e.g., count_emails, find_contacts, get_email), all in lowercase snake_case. The naming is predictable and clear.
With 5 tools covering core email operations (search, count, retrieve, list mailboxes, find contacts), the number is well-scoped and each tool serves a necessary role.
The set covers the main query and retrieval needs, but lacks operations like deleting or moving emails. For a read-oriented MCP, it's mostly complete; minor gap for listing all contacts without a query.