smailr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMAILR_API_KEY | Yes | Your Smailr API key (`nm_...`) | |
| SMAILR_BASE_URL | No | API base URL override (default `https://smailr.com/api/v1`) | https://smailr.com/api/v1 |
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_mailboxesA | List all Smailr mailboxes. Scope: mailbox:read |
| create_mailboxB | Create a new mailbox. Scope: mailbox:write |
| check_addressA | Check whether a mailbox address is available. Scope: mailbox:read |
| get_mailboxA | Get mailbox details by ID. Scope: mailbox:read |
| update_mailboxB | Update a mailbox (settings such as display name, signature, etc.). Scope: mailbox:write |
| delete_mailboxB | Delete a mailbox permanently. Scope: mailbox:write |
| list_mailsB | List mails in a mailbox, optionally filtered by folder. Scope: mail:read |
| get_mailA | Get full details of a single mail. Scope: mail:read |
| update_mailA | Update mail state (e.g. read/unread, flags, folder). Scope: mail:manage |
| delete_mailC | Delete a mail. Scope: mail:manage |
| search_mailsA | Full-text search across mails. Scope: mail:read |
| send_mailC | Send an email from a mailbox. Scope: mail:send |
| upload_attachmentA | Upload a local file as a mail attachment; returns an attachment ID for send_mail. Scope: attachment:write |
| list_contactsB | List contacts. Scope: contact:read |
| create_contactB | Create a contact. Scope: contact:write |
| list_foldersA | List folders of a mailbox. Scope: folder:read |
| create_folderB | Create a folder in a mailbox. Scope: folder:write |
| list_labelsA | List labels. Scope: tag:read |
| create_labelC | Create a label. Scope: tag:write |
| list_rulesA | List incoming-mail filter rules. Scope: filter:read |
| list_signaturesA | List mail signatures. Scope: signature:read |
| get_quotaA | Get storage quota usage. Scope: storage:read |
| get_statsB | Get account statistics. Scope: storage:read |
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 23 tools
Most tools are clearly resource-action pairs, but get_quota and get_stats both cover storage/account usage and list_mails/search_mails could be confused when searching a single mailbox. These are minor boundary cases; the rest are distinct.
All tools use lowercase snake_case verb_noun names (list_, create_, get_, update_, delete_, search_, send_, upload_, check_). Naming is uniform and predictable across all 23 tools.
23 tools is within the heavy range for an MCP server. The email domain is broad enough to justify many of them, but the count feels slightly bloated because several resource areas have only partial operations.
Mailboxes and mails have solid lifecycle coverage, but contacts, labels, and folders only support list/create, while rules and signatures are read-only. Agents cannot update or delete these secondary resources, which is a significant gap for full email management.