Email Template Tools

The Bizzy MCP server provides 10 tools for managing email templates, sending templated emails and recording who agreed to receive marketing email. These tools are organized into three categories: templates, render & send, and marketing opt-ins.

Templates

CRUD tools for managing reusable email templates. Templates support Mustache syntax for dynamic content in both subject lines and bodies.

createEmailTemplate

Create a new email template with name (max 200 chars), subject (max 1000 chars), body (max 50000 chars), and optional variables. Templates support Mustache syntax for dynamic content. Permission: emailTemplates:write Parameters:

Name	Type	Required	Description
`name`	string	Yes	The name of the email template (1-200 characters)
`subject`	string	Yes	The subject line of the email template (1-1000 characters). Supports Mustache variables.
`body`	string	Yes	The body content of the email template (1-50000 characters). Supports Mustache variables.
`description`	string	No	Optional description of the email template (max 2000 characters)
`variables`	string[]	No	Optional list of variable names used in the template for documentation (max 100 entries, each up to 200 characters)

Returns: The created email template object.

getEmailTemplate

Get a specific email template by ID, including all template details. Permission: emailTemplates:read Parameters:

Name	Type	Required	Description
`id`	string (UUID)	Yes	The ID of the email template to retrieve

Returns: The email template object, or null if not found.

listEmailTemplates

List email templates for the organization with pagination. Supports filtering by status and name. Permission: emailTemplates:read Parameters:

Name	Type	Required	Default	Description
`limit`	number	No	10	Number of email templates to return (1-100)
`offset`	number	No	0	Number of email templates to skip for pagination
`status`	string	No	-	Filter by template status (`active` or `archived`)
`name`	string	No	-	Filter by name (case-insensitive partial match, max 200 characters)

Returns:

{
  "emailTemplates": [...],
  "count": 8,
  "limit": 10,
  "offset": 0
}

updateEmailTemplate

Update an existing email template with new values for any template fields. Name max 200 chars, subject max 1000 chars, body max 50000 chars. Permission: emailTemplates:write Parameters:

Name	Type	Required	Description
`id`	string (UUID)	Yes	The ID of the email template to update
`name`	string	No	The name of the email template (1-200 characters)
`description`	string \| null	No	Description of the email template (max 2000 characters)
`subject`	string	No	The subject line of the email template (1-1000 characters)
`body`	string	No	The body content of the email template (1-50000 characters)
`variables`	string[] \| null	No	List of variable names used in the template for documentation (max 100 entries, each up to 200 characters)
`status`	string	No	Template status (`active` or `archived`)

Returns: The updated email template object.

deleteEmailTemplate

Delete an email template (soft delete). Permission: emailTemplates:delete Parameters:

Name	Type	Required	Description
`id`	string (UUID)	Yes	The ID of the email template to delete

Returns: The deleted email template object.

Render & send

Tools for rendering templates with variable data and dispatching templated emails through the organization’s email pipeline.

renderEmailTemplate

Render an email template by ID with provided data variables using Mustache templating. Returns the rendered subject and the raw rendered body — the delivered email (see sendTemplatedEmail) additionally sanitizes the body (unsafe markup removed) and wraps it in a standard email layout. Permission: emailTemplates:read Parameters:

Name	Type	Required	Description
`templateId`	string (UUID)	Yes	The ID of the email template to render
`data`	Record<string, unknown>	Yes	Key-value pairs of variable data to render into the template

Returns: Object with subject and body strings containing the rendered content.

sendTemplatedEmail

Render an email template with data and send it. Fetches the template, renders subject and body with the provided data, sanitizes the body (scripts, event handlers, and other unsafe markup are removed), wraps it in a standard email-client-compatible layout, auto-generates a plain-text alternative, and sends the email from the specified email address. Permission: emailTemplates.send:write (inherits from emailTemplates unless set explicitly) Parameters:

Name	Type	Required	Description
`templateId`	string (UUID)	Yes	The ID of the email template to use
`data`	Record<string, unknown>	Yes	Template variable data for rendering
`to`	string[]	Yes	Recipient email addresses (at least one); matched case-insensitively and deduplicated. For `marketing`, each gets their own message
`fromEmailAddressId`	string (UUID)	Yes	The email address to send from. Must be active, hosted by Bizzy on a verified domain, and allowed to carry the `purpose`
`purpose`	`transactional` \| `marketing`	Yes	What the message is for. `transactional` services something the recipient is already part of; `marketing` promotes an offer
`cc`	string[]	No	CC email addresses. Refused for `marketing`
`bcc`	string[]	No	BCC email addresses. Refused for `marketing`
`replyTo`	string	No	Reply-to email address

Returns: Object with subject, to, from, rendered, sent and skipped fields. skipped lists recipients the organization must not email, each with a reason; they are left off the send. For marketing, a recipient with no opt-in on record is skipped with reason not_opted_in. When no to recipient remains, nothing is sent and sent is false — cc and bcc recipients receive the message only alongside a to recipient. A marketing send delivers a separate message to each to recipient, ending with the business name, its mailing address and an unsubscribe link. to takes at most 50 addresses after duplicates are removed; split a longer list across calls. to in the result lists who was sent a message. Calling again after a partial failure doesn’t send anyone a second copy. Errors: the address is not found, disabled, a connected Gmail or Outlook mailbox, on a domain whose email setup has not finished, or reserved for another purpose; or, for marketing, cc or bcc is set, to has more than 50 addresses, or the business has no mailing address. The same checks run again at the moment of delivery, so a send that this tool accepts is still refused if the address, the agent’s permission, the recipient’s status or their opt-in changes before the message leaves.

Marketing opt-ins

Marketing email reaches only addresses with a live opt-in: a record of how and when the person agreed, and where the proof is kept. Records can’t be edited; withdraw one and record it again to replace it. Recording an opt-in does not undo an unsubscribe.

recordEmailMarketingOptIn

Record that a person agreed to receive the organization’s marketing email. Record only real, explicit agreement — never bought, scraped or cold-outreach addresses. Permission: emailTemplates.optIns:write. New agents ask before recording, even when template writes are allowed. Parameters:

Name	Type	Required	Description
`email`	string	Yes	The person’s address; matched case-insensitively
`basis`	string	Yes	`express_consent` (they asked for or agreed to marketing email) or `confirmed_opt_in` (they agreed, then confirmed through a link sent to that address)
`source`	string	Yes	Where they agreed: `web_form`, `checkout`, `in_person`, `phone`, `email`, `paper_form` or `other`
`capturedOn`	string	Yes	The date they agreed (`YYYY-MM-DD`), not in the future
`evidence`	string	Yes	Where the proof is kept — a sign-up form link, a signed sheet, a booking reference (max 1000 characters)

Returns: The opt-in record, with id, email, basis, source, capturedOn, evidence, createdAt and withdrawnAt (null). Errors: the address already has a live opt-in (the error names it), the evidence is blank, or the date is in the future.

listEmailMarketingOptIns

List opt-in records, newest first. Withdrawn records are left out unless you ask for them. Permission: emailTemplates.optIns:read Parameters:

Name	Type	Required	Default	Description
`email`	string	No	-	Only records for this address
`includeWithdrawn`	boolean	No	false	Include withdrawn records
`limit`	number	No	10	Number of records to return (1-100)
`offset`	number	No	0	Number of records to skip for pagination

Returns:

{
  "optIns": [...],
  "count": 10,
  "total": 42,
  "limit": 10,
  "offset": 0
}

withdrawEmailMarketingOptIn

Withdraw an opt-in record, for example one recorded by mistake. Marketing email to that address stops, including messages already on their way, until a new opt-in is recorded. The record stays in the list as withdrawn. Permission: emailTemplates.optIns:write Parameters:

Name	Type	Required	Description
`id`	string (UUID)	Yes	The ID of the opt-in to withdraw

Returns: The withdrawn record, with withdrawnAt set. Errors: no record with that ID, or it was already withdrawn.

Getting Started

Agent resources

Templates

createEmailTemplate

getEmailTemplate

listEmailTemplates

updateEmailTemplate

deleteEmailTemplate

Render & send

renderEmailTemplate

sendTemplatedEmail

Marketing opt-ins

recordEmailMarketingOptIn

listEmailMarketingOptIns

withdrawEmailMarketingOptIn

Next steps

Email Address Tools

Authentication

​Templates

​createEmailTemplate

​getEmailTemplate

​listEmailTemplates

​updateEmailTemplate

​deleteEmailTemplate

​Render & send

​renderEmailTemplate

​sendTemplatedEmail

​Marketing opt-ins

​recordEmailMarketingOptIn

​listEmailMarketingOptIns

​withdrawEmailMarketingOptIn

​Next steps

Email Address Tools

Authentication

Templates

createEmailTemplate

getEmailTemplate

listEmailTemplates

updateEmailTemplate

deleteEmailTemplate

Render & send

renderEmailTemplate

sendTemplatedEmail

Marketing opt-ins

recordEmailMarketingOptIn

listEmailMarketingOptIns

withdrawEmailMarketingOptIn

Next steps