read-no-evil-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RNOE_HTTP_HOST | No | Bind address for HTTP transport. Default: '0.0.0.0'. | 0.0.0.0 |
| RNOE_HTTP_PORT | No | Port for HTTP transport. Default: '8000'. | 8000 |
| RNOE_LAZY_LOAD | No | Skip model preloading at startup. Set to 'true', '1', or 'yes' to enable. | false |
| RNOE_TRANSPORT | No | Transport protocol: 'stdio' or 'http'. Default: 'stdio'. | stdio |
| RNOE_CONFIG_FILE | No | Path to the YAML configuration file. If not set, searches default locations. | |
| RNOE_ACCOUNT_<ID>_PASSWORD | No | Password for an email account. Replace <ID> with the account id (non-alphanumeric characters replaced with underscores). Example: RNOE_ACCOUNT_GMAIL_PASSWORD. |
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 |
|---|---|
| tasks | {
"list": {},
"cancel": {},
"requests": {
"tools": {
"call": {}
},
"prompts": {
"get": {}
},
"resources": {
"read": {}
}
}
} |
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| delete_emailB | Delete an email by UID. Args: account: Account ID to use (e.g., "work", "personal"). folder: Folder containing the email. uid: Unique identifier of the email. |
| get_emailA | Get full email content by UID. Args: account: Account ID to use (e.g., "work", "personal"). folder: Folder containing the email. uid: Unique identifier of the email. |
| list_accountsA | List all configured email account IDs. Use this to discover which accounts are available before calling other email tools like list_emails, get_email, or list_folders. Returns: A newline-separated list of account IDs. |
| list_emailsB | List email summaries from a folder. Args: account: Account ID to use (e.g., "work", "personal"). folder: Folder to list emails from (default: INBOX). days_back: Number of days to look back (default: 7). limit: Maximum number of emails to return. offset: Number of emails to skip for pagination (default: 0). unread_only: Only return unread emails (default: False). |
| list_foldersA | List all available email folders/mailboxes. Args: account: Account ID to use (e.g., "work", "personal"). |
| move_emailA | Move an email to a target folder. Args: account: Account ID to use (e.g., "work", "personal"). folder: Folder containing the email. uid: Unique identifier of the email. target_folder: Destination folder to move the email to. |
| send_emailA | Send an email with optional attachments. Args: account: Account ID to use (e.g., "work", "personal"). to: List of recipient email addresses. subject: Email subject line. body: Email body text (plain text). cc: Optional list of CC recipients. reply_to: Optional Reply-To email address. attachments: Optional list of file attachments. Each attachment should have: - filename: Name of the file (required) - content: Base64-encoded file content (required if path not provided) - mime_type: MIME type (default: application/octet-stream) - path: File path to read from (required if content not provided) |
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 7 tools
Each tool targets a distinct action (list, get, send, delete, move) on distinct email resources (accounts, folders, emails). There is no overlap; even list_emails and get_email are clearly differentiated by listing summaries vs. getting full content.
All tools follow a consistent verb_noun pattern using snake_case (e.g., list_accounts, get_email, delete_email, move_email, send_email). The naming is predictable and harmonizes across the entire set.
7 tools is well-scoped for an email server. It covers essential operations (list accounts, list folders, list emails, get email, send email, delete email, move email) without unnecessary redundancy or bloat.
The tool surface covers the core email lifecycle: discover accounts/folders, read, send, delete, and move emails. Minor gaps include the lack of mark-as-read/unread, reply, or forward operations, but these are non-critical for basic email handling.