email-mcp-plus
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_emailsA | Search emails using Microsoft Graph API. Uses KQL $search for text queries (from, subject, body) and $filter for date ranges. Works around the $search/$orderBy incompatibility in @marlinjai/email-mcp. |
| list_foldersA | List all mail folders with IDs and item counts. |
| get_sent_itemsC | Search sent items by subject/date. |
| get_email_bodyA | Get full email body by message ID. |
| list_attachmentsB | List attachments for a message. |
| get_attachmentA | Get attachment content (base64). |
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 6 tools
Tools are mostly distinct, but search_emails and get_sent_items both perform searches with overlapping capabilities (subject/date queries). The descriptions clarify that get_sent_items is specific to the sent folder, but an agent could still confuse which to use. Other tools have clearly separate roles.
Tool names generally follow a verb_noun pattern (search_emails, list_folders, get_email_body, list_attachments, get_attachment). However, get_sent_items is a search operation but uses 'get' instead of 'search', deviating from the pattern established by search_emails. Overall, naming is readable and predictable.
With 6 tools, the server is well-scoped for email search and retrieval. Each tool covers a needed function without unnecessary overlap or bloat, making the count appropriate.
The server covers searching, folder listing, body retrieval, and attachment handling, which is solid for a read-oriented email tool. Missing operations like sending or moving emails are not necessarily required for the apparent scope. A minor gap is the lack of a direct 'list emails in a folder' tool, but search can work around it.