MCP server for the Dyspatch API — manage email, SMS, push, voice, and live activity templates from any MCP-compatible AI client.

• Node.js 20+
• A Dyspatch account and API key — see Creating an API Key

The server supports two transports: stdio (default, for process-based MCP clients) and HTTP (for network-accessible deployments).

claude mcp add dyspatch -e DYSPATCH_API_KEY=your_key -- npx dyspatch-mcp

Restart Claude Code after running this command.

Add to your Claude Desktop config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "dyspatch": {
      "command": "npx",
      "args": ["dyspatch-mcp"],
      "env": {
        "DYSPATCH_API_KEY": "your_api_key_here"
      }
    }
  }
}

Restart Claude Desktop after saving.

This is useful when you want the server running persistently in the background, or when you need to connect multiple clients to the same instance.

Step 1 — Start the server:

DYSPATCH_API_KEY=your_key npx dyspatch-mcp --http

Or, if installed locally:

DYSPATCH_API_KEY=your_key PORT=3000 pnpm start:http

The server will listen on http://localhost:3000/mcp.

Step 2 — Point Claude Desktop at it:

{
  "mcpServers": {
    "dyspatch": {
      "type": "http",
      "url": "http://localhost:3000/mcp"
    }
  }
}

Restart Claude Desktop after saving.

command: npx dyspatch-mcp
env:     DYSPATCH_API_KEY=your_key

Start the server as above, then configure your client to connect to http://localhost:3000/mcp using the MCP streamable HTTP transport.

Audit your template library. Ask the AI to list all templates across every channel type, summarize what each one does, and flag any with a stale updatedAt date. Tools: list_templates, get_template

Preview a template before sending. Render any published template with real or sample variable data to review the compiled HTML/text output without leaving your AI client. Tools: list_templates, render_template

Manage the approval workflow. List all drafts, filter to those in PENDING_APPROVAL state, review their compiled content, then approve or reject them in bulk — useful for release-day sign-offs. Tools: list_drafts, get_draft, approve_draft, reject_draft

Set up localization for a new market. Create localizations for a new language across multiple drafts, seed them with translated strings, and lock the drafts for translation handoff — all in a single conversation. Tools: list_drafts, upsert_localization, set_translations, lock_draft_for_translation

Organize templates with tags. Create workspace-scoped tags (e.g. "onboarding", "transactional") and assign them to matching templates to make your template library easier to navigate. Tools: create_tag, list_templates, assign_tag

Duplicate a draft and submit it for approval. Copy an existing draft to use as the starting point for a new variant. Once you've edited the content in Dyspatch, come back to the AI to submit it for approval. Tools: duplicate_draft, get_draft, submit_draft

Tools that operate on templates, drafts, or localizations require a type parameter:

To use the server from this repository in Claude Code, add a .mcp.json file at the project root. The server is run directly from source using tsx (no build step required).

If DYSPATCH_API_KEY is already set in your shell (e.g. via source .env), reference it directly:

{
  "mcpServers": {
    "dyspatch": {
      "command": "npx",
      "args": ["tsx", "src/index.ts"],
      "env": {
        "DYSPATCH_API_KEY": "${DYSPATCH_API_KEY}"
      }
    }
  }
}

Verify the server is registered with /mcp in Claude Code.

Email compiled content is base64-encoded. The subject, html, ampHtml, and text fields returned by get_template and get_draft are base64-encoded. Use render_template to get decoded output with variables substituted.

Draft workflow. Drafts move through states: IN_PROGRESS → PENDING_APPROVAL → Published. Use submit_draft to request approval, approve_draft or reject_draft to act on the request. Drafts can only be edited while in IN_PROGRESS.