Skip to main content
Glama
Cresca MCP Server

Cresca MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CRESCA_API_KEYYesYour Cresca API key (`cr_live_...`). Required for tool calls; sent only as `Authorization: Bearer ...` and never logged.
CRESCA_API_URLNoBase URL including `/api/v1`. Must be `https` (plain `http` is allowed only for `localhost`).https://api.cresca.xyz/api/v1

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

Tools for the Cresca transactional email API (https://www.cresca.xyz/docs). send_email and send_batch_emails send real email that cannot be recalled: confirm recipients, sender and content with the user first. delete_template is permanent and publish_template changes what live email sends. Not available through Cresca: outbound webhooks, SMTP relay, attachments by URL, and open/click tracking for API email.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
send_emailA

WARNING: this SENDS REAL EMAIL to real recipients through Cresca and cannot be undone (only a scheduled or still-queued email can be canceled). Confirm the recipients, sender and content with the user before calling it. Each recipient counts toward the plan's monthly email allowance.

POST /emails. Sends one transactional email to up to 50 recipients (to + cc + bcc), with html/text or a published template, optional attachments, tags, custom headers and scheduling up to 30 days ahead.

Works with sending-access and full-access API keys. The from address must be an active sender on a verified domain. Recipients on the suppression list are skipped and the call still succeeds.

idempotency_key is required: build it from the event ("order-confirmation/1042") and reuse it on every retry. If the result says already_sent, the email went out earlier: the task is done, do not retry with a new key. Returns { id }; check delivery with get_email.

Use it for transactional email (password resets, receipts, alerts), not newsletters or promotions: those belong in Cresca campaigns.

send_batch_emailsA

WARNING: this SENDS REAL EMAIL to real recipients through Cresca and cannot be undone (only a scheduled or still-queued email can be canceled). Confirm the recipients, sender and content with the user before calling it. Each recipient counts toward the plan's monthly email allowance.

POST /emails/batch. Sends 1 to 100 different emails in one request. Each item takes the same fields as send_email except attachments and scheduled_at, which batches do not support.

All or nothing: if any email is invalid, nothing is sent and the error names the failing email by zero-based index ("Email 3: ...").

Works with sending-access and full-access keys. idempotency_key is required and covers the whole batch: build it from the event ("weekly-digest/2026-W45") and reuse it on every retry. If the result says already_sent, the batch went out earlier: do not retry with a new key. Returns { data: [{ id }, ...] } in request order.

get_emailA

GET /emails/:id. Returns one email sent through the API: from, to, cc, bcc, reply_to, subject, html, text, created_at, scheduled_at, tags and its latest status as last_event (queued, scheduled, sending, sent, delivered, delivery_delayed, bounced, complained, failed, suppressed or canceled). "delivered" means the receiving server accepted it, not that it reached the inbox. Emails are kept for 30 days. Needs a full-access key. Read-only.

list_emailsA

GET /emails. Lists emails sent through the API, newest first, without html/text bodies (use get_email for those). Cursor pagination: while has_more is true, pass the id of the last item as after for the next page, or the first item's id as before for the previous page. Use after or before, not both. Emails are kept for 30 days. Needs a full-access key. Read-only.

update_scheduled_emailA

PATCH /emails/:id. Changes the send time of an email whose status is still "scheduled"; any other status returns 422 validation_error. The new time is ISO 8601, up to 30 days ahead. WARNING: a time in the past sends the email immediately. Needs a full-access key.

cancel_emailA

POST /emails/:id/cancel. Cancels an email that is still "scheduled" or "queued" so it is never sent; this cannot be undone (send it again to deliver it). Once sending has started it can no longer be canceled and the API returns 422 validation_error. A canceled email does not count toward the monthly allowance. Needs a full-access key.

create_templateA

POST /templates. Creates a template DRAFT (it cannot be sent until publish_template is called). Use {{{VARIABLE}}} placeholders in html, text, subject and preview_text. The template also appears under Transactional > Templates in the Cresca app. Needs a full-access key. Returns { object: "template", id }.

list_templatesA

GET /templates. Lists every template in the account, newest first, including drafts and templates not set up for the API (status "draft", alias null). Content fields show the current draft; version is the published version sends use. Pagination: while has_more is true, pass the last item's id as after. Needs a full-access key. Read-only.

get_templateA

GET /templates/:id. Returns a template by id or alias. html, subject and the other content fields show the current DRAFT; status is "draft" until the first publish, then "published"; version is the published version that sends use. Needs a full-access key. Read-only.

update_templateA

PATCH /templates/:id. Changes a template's DRAFT, overwriting the fields you send (send only the ones to change; same formats as create_template). Live email keeps using the published version until publish_template is called. Send alias: null to remove the alias. Sending html replaces a visual-editor design with plain HTML. Needs a full-access key.

publish_templateA

POST /templates/:id/publish. Copies the current draft (HTML, text, subject, default sender, Reply-To, preview text and variables) into a new published version. EVERY email sent with this template from then on uses the new version, so confirm with the user before publishing a template that is in use. Undeclared placeholders are added as string variables without a fallback. Earlier versions stay in the app's version history. Needs a full-access key. Returns { id, version }.

delete_templateA

DELETE /templates/:id. PERMANENTLY deletes a template, by id or alias, and its version history, from the API and the Cresca app. This cannot be undone. Emails that still reference it fail with 404 not_found, so confirm with the user first. Needs a full-access key.

add_contactsA

POST /contacts. Adds 1 to 1,000 contacts to a marketing contact list, creating the list if it does not exist. Existing contacts get their name updated and are added to the list; nobody is duplicated. Invalid, disposable, role/no-reply, suppressed and duplicate addresses are rejected and listed in errors (with their index); the rest are still added. When the plan's contact limit is reached, summary.limit_reached is true. Imports are limited to 120 requests per 15 minutes. Only add people who agreed to receive marketing email. Needs a full-access key. Does not send any email.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.2/5.0

Scored across 13 tools

Disambiguation5/5

Each tool maps to a distinct resource+action pair, and the two send tools are clearly separated by semantics (one email to many recipients vs. many distinct emails in a batch), as are get_email vs. list_emails and update_scheduled_email vs. cancel_email. Template tools split cleanly along draft-vs-published lifecycle lines, so an agent can pick the right tool from the description alone.

Naming Consistency5/5

All names follow a single snake_case verb_noun convention (send_email, get_email, list_emails, create_template, publish_template, delete_template, add_contacts). The only variation is qualifying modifiers like batch and scheduled, which stay within the same pattern rather than introducing a new convention.

Tool Count5/5

Thirteen tools sit comfortably in the well-scoped range and each one covers a real operation: six email operations, six template lifecycle operations, and one contact import. There is no visible filler or redundant alias tool.

Completeness3/5

Email sending and the template lifecycle are covered end-to-end (send, batch, inspect, list, reschedule, cancel, draft, publish, delete), but the contacts surface is a single write-only add_contacts with no list/get/update/delete or suppression-list management, so an agent cannot verify or clean up contacts it imported. Suppression list handling is also only referenced implicitly, leaving notable dead ends outside the core send path.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues