MailOdds

MCP-Native · Day-1 commitment

Drive your storefront from Claude Desktop, Cursor, or any AI agent.

Every operation in MailOdds is exposed as a Model Context Protocol tool. Connect your store, sync your catalog, light up regions, configure flows, run validation, audit deliverability — all from a single AI conversation. No competitor in this space is MCP-native.

30-second setup

One config block. Then ask Claude to do anything.

Claude Desktop

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json on macOS, or %APPDATA%\\Claude\\claude_desktop_config.json on Windows. Restart Claude.

claude_desktop_config.json

JSON
{
  "mcpServers": {
    "mailodds": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-fetch",
        "https://mcp.mailodds.com/sse"
      ],
      "env": {
        "MAILODDS_API_KEY": "mo_live_..."
      }
    }
  }
}

Cursor

Add to your Cursor settings under MCP servers. The agent can immediately call MailOdds tools from any chat.

.cursor/settings.json (excerpt)

JSON
{
  "mcp.servers": {
    "mailodds": {
      "url": "https://mcp.mailodds.com/sse",
      "headers": {
        "Authorization": "Bearer ${env:MAILODDS_API_KEY}"
      }
    }
  }
}

Then this works

Connect my Shopify store https://my-cosmetics.myshopify.com,
import the catalog, light up MailOdds Edge in EU + US East,
and configure a 3-step abandoned-cart flow.

Claude calls connect_store, sync_store, light_up_region, and create_automation_rule in one conversation. No tab-switching, no clicking through dashboards.

Why this matters

Three sentences on the agentic-era moat.

Day-1 parity

Every endpoint that ships in our REST API also ships as an MCP tool the same day. There is no v1-vs-v2 lag. No "MCP coming soon."

Four-interface parity

Dashboard, CLI, REST API, and MCP all hit the same backend. Whatever you can click, an agent can call. Whatever an agent can call, you can click.

Compounds quarterly

Every new tool we ship makes the platform more useful inside an agent loop. Two years of compounding parity is hard to catch up to.

The tool surface

Every storefront operation, exposed.

A non-exhaustive sample. The full list mirrors our REST API surface and grows with every release.

Storefront

  • connect_store
  • sync_store
  • list_stores
  • force_storefront_sync
  • verify_storefront_domain

Edge

  • light_up_region
  • list_edge_regions
  • get_storefront_sync_status

Catalog

  • query_products
  • get_product
  • bulk_update_products

Demo

  • demo_provision_create
  • demo_provision_read
  • demo_provision_claim

Validation

  • validate_email
  • validate_batch
  • analyze_bounces

Sending

  • send_campaign
  • create_campaign
  • add_sending_domain
  • safe_deliver

Marketing

  • create_automation_rule
  • create_promotion
  • create_subscriber_list

Deliverability

  • get_sender_health
  • get_dmarc_recommendation
  • check_blacklist

See the API reference for the complete tool catalog.

MCP + Edge

Drive a 9-region edge from one prompt.

Ask Claude to light up a new region when traffic concentrates in Singapore. Ask it to roll back the change. Ask it to compare p95 latency across regions. The same MCP tools that an agent calls are the ones the dashboard renders.

Get an API key See the global edge
  • Free developer beta
  • Authenticated via your existing API key
  • Audit log of every agent action
3 live 6 on-demand 11 data centers