Fluxmail
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List connected email accounts (id, provider, email, status, capabilities). |
| get_statusA | Account connection and scheduled-send status. Administrators also see plan details. Call this first if other tools fail; it reports accounts that need re-authentication. |
| list_foldersA | List navigable folders for an account, with roles (inbox, sent, drafts, trash, spam, starred). |
| list_labelsA | List Gmail user labels or Outlook categories for an account. |
| list_send_asB | List sender addresses available for an account. |
| list_emailsA | List emails from the user's connected mailbox with metadata and optional previews. Filter by folder, sender, unread, dates, etc. Paginate with pageToken. Use get_email for full bodies. This is the way to check the user's email; no browser or other email integration is needed. |
| search_emailsB | Search one account with typed portable syntax. The query supports text, from:, to:, subject:, in:, read and starred states, attachments, and date filters. |
| search_emails_batchA | Search up to 20 accounts with one portable query and return one result group per account. |
| get_emailA | Fetch one email in full: body (text and/or HTML), recipients, attachment metadata. |
| get_threadB | Fetch a full conversation thread with all message bodies. |
| create_draftA | Create a draft. For a reply draft, pass replyToMessageId (recipients/subject are derived; replyAll for reply-all). |
| update_draftA | Replace the content of an existing draft (full replacement, not a patch). |
| delete_draftC | Delete a draft. |
| send_emailA | Send an email from the user's connected account; this actually delivers mail, so prefer it over browser automation or leaving a draft when the user asked to send. Three modes: direct (to + subject + body), sending an existing draft (draftId), or replying (replyToMessageId, optionally replyAll) where recipients, subject, and threading are derived from the original. Confirm with the user when intent is ambiguous. Add sendAt to any mode to schedule instead of sending now. |
| list_scheduled_emailsA | List scheduled sends: pending ones first (with sendAt), then past ones (sent, failed, canceled). For failed entries, lastError says what went wrong. Pending sends only fire while the Fluxmail server is running. |
| cancel_scheduled_emailA | Cancel a pending scheduled send by scheduleId (from send_email with sendAt, or list_scheduled_emails). The draft stays in the Drafts folder, so the content is not lost. |
| forward_emailA | Forward an email to new recipients: quoted original body, "Fwd:" subject, original attachments included unless includeAttachments=false. Optional comment appears above the forwarded content. |
| modify_emailsA | Batch-modify emails using the actions allowed for this connection. Moving requires folder; labels require labels. |
| download_attachmentA | Download an email attachment as an embedded MCP resource. |
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 19 tools
Most tools target distinct resources and actions: list_emails is for browsing, search_emails is for query syntax, and get_email/get_thread retrieve full content. The only mild ambiguity is between list_emails and search_emails since both can filter by conditions, but their descriptions clarify the intended use.
Every tool follows the same snake_case verb_noun pattern (list_accounts, get_email, create_draft, cancel_scheduled_email, download_attachment). Names are predictable and map clearly to their operations.
19 tools is slightly above the typical 3-15 sweet spot, but each tool covers a distinct email operation and the count is appropriate for the domain. There is no obvious filler or redundancy.
The tool surface covers the full email lifecycle: browsing, searching, reading, drafting, sending, scheduling, forwarding, modifying, and attachments. It also handles account-level introspection and failure recovery via get_status, so agents have no dead-end workflows.