Cloudflare Email MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLOUDFLARE_API_TOKEN | No | Optional - Cloudflare API token, detected automatically from wrangler | |
| CLOUDFLARE_ACCOUNT_ID | No | Optional - Cloudflare account ID, detected automatically from wrangler |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kv_keys_listA | List keys in a Cloudflare KV namespace with optional prefix filtering and pagination |
| kv_keys_countA | Count total keys in a KV namespace with optional prefix filter |
| kv_key_getA | Get the value of a single key from a KV namespace |
| kv_key_putB | Write a key-value pair to a KV namespace |
| kv_key_deleteA | Delete a key from a KV namespace |
| kv_keys_bulk_getB | Get values for multiple keys from a KV namespace |
| email_transfer_foldersB | Transfer emails from approved IMAP folders to their mapped KV namespaces |
| email_list_foldersA | List IMAP folders and show which ones are approved for auto-sync to KV |
| email_folder_statsC | Get email processing statistics for a specific folder |
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 9 tools
Every tool has a clear, distinct purpose: KV operations are separated into list/count/get/put/delete/bulk_get, and email operations are separated into transfer/list/stats. There is no ambiguity between tools, even the single-key vs bulk-key get tools are clearly differentiated.
The naming pattern is mostly consistent: KV tools use 'kv_' prefix plus resource (key/keys) plus action (list/get/put/delete), and email tools use 'email_' prefix plus action or noun. Slight inconsistencies exist like 'email_folder_stats' being noun-based rather than verb-based, and 'kv_keys_bulk_get' differs slightly in word order from 'kv_key_get'.
The 9 tools cover two clear functional areas—KV key-value storage and email-to-KV transfer—without unnecessary overlap or bloat. This is within the ideal range for a purpose-built server.
The KV tools cover the core CRUD operations (get, put, delete, list, count) and add a useful bulk read. The email tools provide list, transfer, and stats, but lack configuration operations like approving folders or updating mappings, which are minor gaps that can be worked around via external configuration.