Skip to main content
Glama
Cloudflare Email MCP Server

Cloudflare Email MCP Server

Cloudflare Email MCP Server

A comprehensive Model Context Protocol server for Cloudflare KV operations and automated email processing from ProtonMail Bridge to Cloudflare KV namespaces.

Features

KV Operations

  • Key Management: List, count, get, put, delete keys in any KV namespace

  • Pagination: Handle large datasets with cursor-based pagination

  • Bulk Operations: Retrieve multiple keys efficiently

Email Processing

  • Automated Transfer: Move emails from specific IMAP folders to corresponding KV namespaces

  • UUID v5 Body IDs: Deterministic body identification with separate storage

  • Folder Mapping: Pre-configured mappings for court, government, and legal correspondence

  • Status Tracking: Pending/processed status for workflow management

Related MCP server: own-domain-mcp

Architecture

Two-Tier Storage

Court KV Namespace:
├── Key: 2026.02.09_casework_ico_org_uk_10-30-45
└── Value: {
    "from": "casework@ico.org.uk",
    "to": "rose@mobicycle.ee", 
    "subject": "Your complaint reference IC-...",
    "body": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
    "namespace": "ICO Complaints",
    "status": "pending"
}

Body KV Namespace (by year):
├── Key: f47ac10b-58cc-4372-a567-0e02b2c3d479
└── Value: { "text": "Dear Ms Liu..." }

Folder Mappings

Automatically processes emails from:

  • Courts: Appeal, Chancery, Admin Court, King's Bench, Supreme, etc.

  • Government: GLD, US State Dept, Estonian Government

  • Complaints: HMCTS, ICO, PHSO, Bar Standards, Parliament

  • Parties: Liu Litigation, HK Law, Lessel Property, etc.

Setup

Prerequisites

  • Bun runtime

  • ProtonMail Bridge running locally

  • Cloudflare account with KV access

  • Wrangler CLI configured

Authentication

The server uses Wrangler OAuth tokens automatically:

wrangler auth login

Installation

bun install
bun run build
bun start

Usage

MCP Tools

KV Operations

// Count keys in a namespace
kv_keys_count({
  namespace_id: "your-namespace-id",
  prefix: "email:"
})

// List keys with pagination  
kv_keys_list({
  namespace_id: "your-namespace-id",
  prefix: "2026.02",
  limit: 100,
  cursor: "next-page-cursor"
})

// Get/set individual values
kv_key_get({ namespace_id: "...", key: "..." })
kv_key_put({ namespace_id: "...", key: "...", value: "..." })

Email Processing

// Transfer emails from approved folders
email_transfer_folders({
  folders: ["INBOX/Courts/Supreme"],
  since: "2026-02-01T00:00:00Z",
  dry_run: true
})

// Check processing stats
email_folder_stats({
  folder_name: "INBOX/Complaints/ICO"
})

// List all folders and their approval status
email_list_folders()

Configuration

Approved Folders

Only pre-configured folders automatically sync to KV:

  • Legal correspondence folders

  • Court communications

  • Government agencies

  • Complaint systems

KV Namespaces

  • Court namespaces: One per jurisdiction

  • Body storage: Separated by year (email-bodies-2026)

  • Account mapping: Bridge gRPC account information

Development

Project Structure

src/
├── index.ts           # Main MCP server with stdio transport
├── cloudflare-api.ts  # KV operations via Cloudflare API
└── email-processor.ts # IMAP to KV sync logic

dist/                  # Built JavaScript
README.md             # This file
package.json          # Dependencies and scripts

Building

bun run build    # TypeScript compilation
bun run dev     # Watch mode

Testing

# Dry run email processing
email_transfer_folders({ dry_run: true })

# Test KV operations
kv_keys_count({ namespace_id: "test-namespace" })

Integration

Claude Code MCP Configuration

Add to Claude Code MCP settings:

{
  "mcpServers": {
    "cloudflare-email": {
      "command": "bun",
      "args": ["start"],
      "cwd": "/path/to/this/directory"
    }
  }
}

Environment Variables

# Optional - detected automatically from wrangler
CLOUDFLARE_API_TOKEN=your-token
CLOUDFLARE_ACCOUNT_ID=your-account-id

Automation

Bridge Integration

Works with ProtonMail Bridge gRPC for account mapping:

  • Automatic token capture on Bridge restart

  • Account structure pushed to KV

  • Prevents email double-counting

Workflow

  1. Bridge receives emails in configured folders

  2. MCP server syncs new emails to KV namespaces

  3. AI triage system processes pending emails

  4. Status updates track workflow progress

License

Internal MobiCycle OÜ project - Not for public distribution

Available Tools

9 tools
email_folder_statsC

Get email processing statistics for a specific folder

Inputs: folder_name (required).

email_list_foldersA

List IMAP folders and show which ones are approved for auto-sync to KV

Inputs: no named parameters.

email_transfer_foldersB

Transfer emails from approved IMAP folders to their mapped KV namespaces

Inputs: limit, since, dry_run, folders.

kv_key_deleteA

Delete a key from a KV namespace

Inputs: key (required), namespace_id (required).

kv_key_getA

Get the value of a single key from a KV namespace

Inputs: key (required), namespace_id (required).

kv_key_putB

Write a key-value pair to a KV namespace

Inputs: key (required), value (required), namespace_id (required), metadata.

kv_keys_bulk_getB

Get values for multiple keys from a KV namespace

Inputs: keys (required), namespace_id (required).

kv_keys_countA

Count total keys in a KV namespace with optional prefix filter

Inputs: namespace_id (required), prefix.

kv_keys_listA

List keys in a Cloudflare KV namespace with optional prefix filtering and pagination

Inputs: namespace_id (required), limit, cursor, prefix.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 9 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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'.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to send, read, search, and organize emails via ProtonMail using Proton Bridge. Supports MCP-compatible clients like Claude and Cursor.
      18
      19 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provisions own-domain email for families using Cloudflare's API, enabling automatic setup of email routing, catch-all forwarding, and verified destinations.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Cloudflare Worker implementation of the Cypht email MCP, providing eight email tools for account management, email sending, listing, viewing, searching, and deletion via IMAP.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying and retrieving email messages from an IMAP mailbox via MCP tools, with an indexed storage backend on Cloudflare.
      39 npm
      MIT