chore: update docs

Author: felixnorden

examples/email-mcp/README.md

@@ -1,11 +1,13 @@
 # Email MCP (Durable Object SQL DB + Cloudflare Email)
 
 An MCP server that:
+
 - Sends internal emails via Cloudflare's Email binding (only to verified addresses).
 - Manages email data via Durable Object SQLite storage.
 - Exposes MCP tools and resources to interact with emails.
 
 Features
+
 - Tools:
   - create_test_email(from_addr, to_addr, subject, text) - Create test emails for database testing
   - send_email(to, subject, text) - Send real emails via Cloudflare Email Workers (requires domain setup)
@@ -16,39 +18,47 @@ Features
   - do://database/emails/{id} - Get specific email
 
 Important limitations
+
 - This is for internal email only. Cloudflare’s Send Email binding delivers only to verified recipients on your zone.
 - Not a general outbound SMTP service.
 
 Setup
 
-1) Durable Object SQL Database
+1. Durable Object SQL Database
+
 - No external database setup required! The Durable Object has built-in SQLite storage.
 - Email data is stored in the Durable Object's persistent SQLite database.
 
-2) Email Routing and bindings
+2. Email Routing and bindings
+
 - Verify MAIL_FROM (sender) address in Cloudflare Email Routing.
 - Verify intended recipient addresses or domains (ALLOWED_RECIPIENTS).
 - Add “Send Email” binding named SEND_EMAIL in wrangler.jsonc.
 
-3) Durable Object binding
+3. Durable Object binding
+
 - EMAIL_MCP_SERVER is defined in wrangler.jsonc. No extra setup beyond deploy.
 
-4) Env vars
+4. Env vars
+
 - MAIL_FROM: the verified sender (e.g., no-reply@example.com)
 - ALLOWED_RECIPIENTS: comma-separated emails or @domain rules. Examples:
   - "alice@example.com,bob@example.com,@example.com"
 
 Local development
+
 - Install deps: pnpm i
 - Update wrangler.jsonc vars and bindings.
 - Run: pnpm dev
 
 Deploy
+
 - pnpm deploy
 
 Testing MCP with the Playground
+
 - Start the Playground package or your client.
-- Connect via SSE/WebSocket to this Worker’s /sse (the MCP package already mounts standard endpoints in the DO).
+- Connect via HTTP/SSE to this Worker’s /mcp (the MCP package already mounts standard endpoints in the DO).
 - Call tools:
   - send_email
   - list_emails
@@ -60,9 +70,9 @@ Testing the MCP Server
 
 You can test the core email management functionality immediately:
 
-1. **Connect to MCP server**: 
-   - Local: http://localhost:PORT/sse (where PORT is shown by wrangler dev)
-   - Production: https://your-worker.workers.dev/sse
+1. **Connect to MCP server**:
+   - Local: http://localhost:PORT/mcp (where PORT is shown by wrangler dev)
+   - Production: https://your-worker.workers.dev/mcp
 
 2. **Create test emails**:
    - Tool: `create_test_email`
@@ -76,7 +86,7 @@ You can test the core email management functionality immediately:
    - Copy any full UUID for detailed viewing
 
 4. **Get specific email**:
-   - Tool: `get_email` 
+   - Tool: `get_email`
    - Use: Any UUID from the list_emails results
    - Shows: Complete email details including full content
 
@@ -85,13 +95,15 @@ You can test the core email management functionality immediately:
 To test the `send_email` tool for actual email delivery:
 
 ### Prerequisites:
+
 1. **Own a domain** registered with any provider
 2. **Add domain to Cloudflare** and enable Email Routing
 3. **Verify sender addresses** in Cloudflare Email Routing → Send tab
 4. **Update MAIL_FROM** in wrangler.jsonc to your verified domain
 5. **Update ALLOWED_RECIPIENTS** with addresses you want to allow
 
 ### Setup Steps:
+
 1. **Cloudflare Dashboard** → Your Domain → Email → Email Routing
 2. **Enable Email Routing** (adds required DNS records automatically)
 3. **Add destination addresses** and verify them via email
@@ -107,12 +119,14 @@ To test the `send_email` tool for actual email delivery:
 7. **Test**: Use `send_email` tool with allowed recipients
 
 ### Expected Results:
+
 - **✅ Allowed recipients**: Email sent successfully
 - **❌ Disallowed recipients**: "Recipient not allowed" error
 - **❌ Unverified sender domain**: "domain not owned" error
 
-
 Notes
+
 - Large raw messages: we store only the text and metadata in the Durable Object SQLite database. If you need full raw message storage, consider R2.
 - If you see recipient not allowed, update ALLOWED_RECIPIENTS.
-- The Durable Object SQLite database provides strong consistency and is automatically managed by Cloudflare.
+- The Durable Object SQLite database provides strong consistency and is automatically managed by Cloudflare.
+