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_emailsA | Search the local mail index with a Returns one line per message: Query syntax (quote phrases with double quotes; no shell is involved):
Examples:
Args: query: the mu query. max_results: cap on returned messages; raise it or narrow the query if the result is cut off. sort: field to sort by. newest_first: reverse sort order (newest/Z first). include_thread: also return other messages from matching threads. |
| view_emailsA | Read emails (headers + body as text) given paths from search_emails. HTML-only emails are converted to plain text. Args: paths: message file paths. max_chars: per-message cap on returned text. |
| list_attachmentsC | List the MIME parts (attachments, inline images, bodies) of one email. |
| open_attachmentA | Save attachments of an email to a temp dir, optionally opening them. Returns the saved file paths, so their contents can be read afterwards. Args:
path: message file path.
pattern: case-sensitive PCRE matched against attachment file names,
e.g. |
| mu_helpA | Full mu reference, for when the short guide in search_emails isn't enough. Topics: query (complete query language), fields (live list of fields and flags), find (search options), extract (attachment handling). |
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 5 tools
Each tool targets a distinct action: search metadata, view message bodies, list MIME parts, save/open attachments, and read help. Boundaries are clear; no two tools overlap in purpose.
Four tools follow a consistent verb_noun snake_case pattern (search_emails, view_emails, list_attachments, open_attachment), but mu_help deviates and list_attachments/open_attachment mix plural/singular. Minor deviations only.
Five tools are well-scoped for a local email search/read server. Each tool earns its place; no bloat or missing essential primitive.
Search and view cover the core read path, but open_attachment saves files without any tool to read their contents afterward, creating a dead end for attachment processing. No update/tag operations either, though those may be outside the read-only scope.