MCP Server

Templated ships a Model Context Protocol server, so any MCP-capable client — Claude Desktop, Claude Code, agent frameworks — can create and manage templates in your account.

Bring your own model. Your AI authors the email HTML; Templated stores, renders, and exports it. Template creation via MCP never consumes Templated AI-generation or import credits — the only limit that applies is your plan's template storage cap. The one exception is the optional generate_image tool, which is metered against your AI image credits (see Tools).

Connect

You need an API key: in Templated, go to Integrations → API Keys and create one (tmpl_sk_...). Keys are scoped to a single account with editor permissions.

Option A — stdio (npm package)

Add to your MCP client config (Claude Desktop shown):

{
  "mcpServers": {
    "templated": {
      "command": "npx",
      "args": ["-y", "@templatedemails/mcp"],
      "env": { "TEMPLATED_API_KEY": "tmpl_sk_..." }
    }
  }
}

Environment variables:

Option B — remote (no install)

Point a custom connector at the hosted endpoint:

POST https://app.templated.email/api/mcp
Authorization: Bearer tmpl_sk_...

The remote endpoint is stateless (single JSON responses, no SSE stream) and enforces per-key rate limits: 60 requests/min overall, 20 write tool calls/min.

Tools

create_template and duplicate_template are subject to your plan's template storage cap — the error message says so explicitly when you hit it. That cap is about stored templates, not AI usage: deleting unused templates frees capacity immediately.

generate_image is the one metered tool: it runs on Templated's image model, so each call consumes one of your plan's monthly AI image credits (the same pool the in-app editor uses; paid plans only). Args: prompt (required), aspect (1:1 | 16:9 | 4:5), optional template_id to attach the image to a template. The "never consumes credits" guarantee applies to template authoring — where your model does the work — not to server-side image generation.

Resources

The server exposes context your model should read before authoring:

Prompts

How it relates to the REST API

Every MCP tool is a thin wrapper over the REST API — the same auth, permissions, and limits apply. MCP-created templates appear in your dashboard with source api and open in the HTML editor. To convert one to visual blocks, use the HTML import endpoint (this does consume a design-import credit, since it runs Templated's conversion AI).

Errors