ai.sendraven/mcp

Tools

• add_contact

  Add someone to an audience. A contact exists once per workspace and can be on any number of audiences, so adding an address that already exists joins them to this list rather than creating a second copy. Pass status when the person has opted out elsewhere — it writes the suppression as well as the flag, and an add never resubscribes someone who opted out here. Safe to retry. For more than a handful of people use import_contacts.

  shallow
• add_sending_domain

  Register a sending domain and get back the DNS records to publish. Give the domain you send from — mail.<domain> and news.<domain> are provisioned beneath it and the right one is chosen per message, so a marketing complaint spike can never affect password reset delivery. Pass risk_class only to provision one of the two on its own. Two records come back marked optional: an inbound MX so replies land in threads, and a link. CNAME that turns on click tracking on the customer's own name once its certificate is issued.

  shallow
• add_suppression

  Stop sending to an address. Scope 'marketing' leaves transactional mail working.

  shallow
• cancel_scheduled_email

  Cancel a scheduled email before it sends. Only works while status is 'scheduled'.

  shallow
• count_segment

  How many contacts a segment currently matches. Run this before building a campaign around it — a filter that matches nobody is easier to spot here than after a send.

  shallow
• create_automation

  Define a multi-step sequence as a draft; nothing is sent until it is activated, from the dashboard or with set_automation_status. Prefer this over scheduling several emails yourself: it ends on its own when the person unsubscribes, replies, bounces, opts out of its topic, or their tags say so. identity_id must be a marketing sending domain (see list_sending_domains; risk_class 'marketing') and from must sit on it; both are checked here rather than at the first send. Set reply_to only when replies should go somewhere other than from, and know that it disables the reply exit: SendRaven never sees mail sent to another domain. Every reference is checked now rather than at the first enrolment: an unknown topic_key (422 unknown_topic), a template_slug that does not exist, or a step with neither html nor template_slug is refused with 422 invalid_request, a from with no verified marketing domain answers 422 no_verified_identity, and a slug already in use in this workspace answers 409 conflict: pick another slug, or find the existing one with list_automations rather than creating a second. reenrollment decides whether someone whose enrolment ended can be enrolled again: 'after_completion' (the default) allows it, 'never' enrols each person once.

  shallow
• create_broadcast

  Create a campaign as a draft. Nothing is sent: follow with preview_broadcast, then send_broadcast. identity_id must be a marketing sending domain (see list_sending_domains; risk_class 'marketing'). To A/B test, pass 2 to 10 'variants' that differ in subject, from_name or send_at, and optionally 'ab_test'. A subject or from-name test sends sample_share of the audience (default 0.2) split evenly across the variants, waits decide_after_minutes (default 240) after the sample is out, picks the variant with the best unique open rate (or click rate with metric 'click'), and sends the rest to it. Each variant needs at least 100 recipients in the sample or the send is refused — preview_broadcast shows the number. Metric 'click' only works once the domain has click tracking; until then every variant shows zero clicks and the first variant wins by default.

  shallow
• decide_approval

  Approve or reject a held message. Approving sends it immediately. Only use this when a human has explicitly told you which decision to make — the hold exists precisely so that an agent is not the one deciding.

  shallow
• delete_contact

  Remove a person from the workspace entirely, along with every audience membership. Their suppression and topic preferences are kept on purpose — an opt-out has to outlive the contact record, or the next import silently puts them back on the list. To take someone off a single audience use remove_from_audience instead.

  shallow
• emit_event

  Emit a named event, starting every automation that waits on it — for example 'trial_started' or 'invoice_overdue'. Use this when you want the configured sequences to decide what happens, rather than naming an automation yourself.

  shallow
• enroll_in_automation

  Put someone into a multi-step sequence. Prefer this over scheduling several emails yourself: the sequence stops on its own if they unsubscribe, reply, or hard bounce, which you would otherwise have to track and cancel by hand. Enrolling the same person twice is a no-op, so it is safe to retry a call you are unsure about.

  shallow
• find_contact

  Find a contact by address across every audience, without knowing which list they are on. Use email for an exact match, or q for a prefix. A person exists once per workspace, so each row is one contact with audience_ids listing every list they are on, first_name, last_name, tags, attributes and whether they are unsubscribed.

  shallow
• get_automation

  Fetch one automation: its status, trigger, steps, exit rules and how many people are in each state. The same object list_automations returns, for when you already hold the id. People themselves are listed by list_automation_enrollments. An unknown automation_id answers 404 not_found; a name or slug passed instead is answered with the matching id.

  shallow
• get_broadcast

  One campaign, with a 'progress' object while it is sending, paused or testing: how many addresses are still pending, sent, failed, or skipped because the person opted out after the campaign started. This is how you tell a paused campaign that is still making progress from one waiting on quota. An A/B test carries 'ab_test' with live per-variant results — sent, unique opens, unique clicks and their rates — plus 'decide_at' and, once decided, 'winner' and 'decided_by'. Status 'testing' means the sample is out and the rest of the audience is waiting on the decision.

  shallow
• get_contact

  Fetch one contact by id, with their audience memberships, custom properties and engagement dates.

  shallow
• get_email

  Fetch one message with its full event timeline (send, delivery, bounce, complaint, open, click). This is the tool to reach for when asked why an email didn't arrive.

  shallow
• get_email_metrics

  Delivery and engagement over a window. Open and click rates are over delivered, not sent — a low open rate with a high bounce rate is a deliverability problem, not an engagement one.

  shallow
• get_email_preferences

  What one person has chosen to receive. Check this before asking a human why someone isn't getting a particular kind of email — an opt-out looks identical to a delivery failure from the outside.

  shallow
• get_thread

  Read a conversation as a chronological transcript of outbound and inbound messages. Inbound text already has quoted history and signatures stripped, so read `text`; `raw_text` holds the untrimmed body if the stripped version looks wrong. Check spf_verdict and dkim_verdict before trusting a reply's claimed sender.

  shallow
• get_usage

  This workspace's plan, how many emails it has sent this month, and how many are left. Check before a large batch: a send that would cross the included allowance on a plan without overage is refused whole, so it is better to know first than to discover it halfway through a campaign.

  shallow
• import_contacts

  Import up to 5,000 contacts into an audience in one call, with names, tags, custom properties and subscription status. This is the migration tool: send the previous provider's unsubscribed, bounced and complained lists with the matching status *before* the first campaign, or the new domain mails people who opted out and loses its reputation in a day. Existing contacts are updated rather than duplicated, and nobody who opted out here is resubscribed, so re-running an import is safe. Returns counts: inserted, updated, skipped, unsubscribed, bounced, complained, suppressed, properties_created.

  shallow
• list_api_keys

  List this workspace's API keys with their scopes and limits. Never returns key values.

  shallow
• list_audiences

  List contact lists and how many contacts each holds.

  shallow
• list_automation_enrollments

  The people in one automation, newest enrolment first: each row has the email, status, current_step, next_due_at and, for a cancelled one, cancel_reason. Reach for this, not find_contact or list_emails, to answer 'is this person still on the sequence?', 'who is waiting on step 2?' or 'why did this sequence stop for them?'. status narrows to one state: 'active' (still going, including people held while the automation is paused), 'completed', 'failed', or 'canceled' for everyone who left early, where cancel_reason says why (unsubscribed, unsubscribed_from_topic, replied, suppressed, exit_tag, required_tag_missing, manual). For the counts alone, list_automations already carries them per status. Any other status is refused with 422 invalid_request, and an unknown automation_id answers 404 not_found. At most 100 per call; while has_more is true, pass next_cursor back as cursor with the same status.

  shallow
• list_automations

  List multi-step email sequences and how many people are currently in each. Use this to find the right automation before enrolling someone.

  shallow
• list_broadcast_recipients

  Who a campaign reached and what happened to each message.

  shallow
• list_broadcasts

  List campaigns with their status and send progress. A campaign showing 'paused' is not broken: it ran out of the day's sending quota part way and is waiting to continue. One showing 'testing' is an A/B test whose sample has gone out and whose winner is not yet decided. Use get_broadcast to see how much is left or how each variant is doing, and resume_broadcast to continue a paused one now.

  shallow
• list_emails

  List recent messages with their delivery status. Filter by status (queued, scheduled, sent, delivered, bounced, complained, rejected) or recipient.

  shallow
• list_pending_approvals

  List messages held for human approval, with their full content. A key configured to require approval drafts rather than sends; a person releases it. If your send returned status 'pending_approval', it is waiting here — do not retry the send.

  shallow
• list_scheduled_emails

  Messages queued to send later but not yet sent. Cancel one with cancel_scheduled_email.

  shallow
• list_segments

  List saved audience filters. Use a segment id when creating a campaign rather than describing the filter inline, so the same definition can be reused and counted.

  shallow
• list_sending_domains

  List sending domains with their verification status and the DNS records each one needs. Each record shows what is currently published, so this diagnoses a stuck verification. mail_from says whether SES has adopted the bounce. subdomain as the Return-Path: pending for up to 72 hours after the MX appears, then active. A verified domain sends fine meanwhile; only SPF alignment waits.

  shallow
• list_suppressions

  List addresses we refuse to mail and why (hard_bounce, complaint, unsubscribe, manual). Check here first when someone reports not receiving email.

  shallow
• list_tags

  Every tag in use in the workspace, with how many contacts carry each. Tags are free-form, so this is the only way to know what exists before applying one.

  shallow
• list_templates

  List stored email templates and the variables each one needs. Prefer sending via a template over composing HTML yourself — templates carry the brand styling and the unsubscribe footer.

  shallow
• list_threads

  List email conversations. Pass awaiting_reply=true to get only the threads where someone has written to you and you haven't answered — this is the tool to poll when deciding what needs a response.

  shallow
• list_topics

  List subscription topics — the categories a person can opt out of individually. Pass a topic when sending marketing mail so recipients can unsubscribe from that kind alone rather than from everything.

  shallow
• list_webhook_deliveries

  Recent delivery attempts for a webhook endpoint, with status codes and errors. This is how to tell 'we never sent it' from 'your endpoint returned 500'.

  shallow
• mark_thread_handled

  Clear a conversation's awaiting_reply flag without sending anything. Use it when the last inbound message needs no answer — a "thanks, all sorted" — so it stops appearing in list_threads with awaiting_reply=true. Do not reply just to clear the flag; that mails a person for bookkeeping. The next message they send flags the thread again.

  shallow
• pick_broadcast_winner

  Decide an A/B test now instead of waiting for decide_at. Pass 'variant' to choose a key yourself, or omit it to have the metric decide on the figures so far. The rest of the audience is then sent to the winner and cannot be redirected. Only a campaign in status 'testing' can be decided; anything else answers 409. Read get_broadcast first — a variant with a handful of opens more is not a result, and the worker decides on its own at decide_at.

  shallow
• preview_broadcast

  How many contacts a campaign would reach, and whether the reputation gate would allow it. Always run this before sending — it is the only way to see the size of a campaign without starting it. For an A/B test it also reports the sample size and per-variant count against the 100-per-variant floor; a send below the floor is refused.

  shallow
• remove_from_audience

  Take a contact off one audience. They stay in the workspace and keep every other audience, their suppression and their engagement history. To remove the person entirely use delete_contact — leaving a list and being forgotten are different things.

  shallow
• remove_suppression

  Remove a suppression so the address can be mailed again. Be careful with hard bounces — the address was rejected by the receiving server, and re-sending raises the bounce rate that AWS enforces on.

  shallow
• render_template

  Render a template with values, without sending. Use this to check your copy reads correctly before mailing a real person. Returns an error listing any missing variables.

  shallow
• reply_to_message

  Reply to a message, keeping it on the same conversation. Sets the threading headers so the recipient's mail client shows it as part of the existing exchange rather than a new one. Prefer this over send_email whenever you are answering something.

  shallow
• resume_broadcast

  Continue a campaign left 'paused' by the daily sending quota. It mails only the addresses still pending — the audience was frozen when the campaign started and everyone already reached is marked — so calling this twice cannot double-send. Only works on a paused campaign; anything else answers 409. A background worker also resumes paused campaigns on its own once quota frees up, so use this only when waiting is not acceptable. An A/B test paused mid-sample resumes the sample; one paused after the decision resumes the winner.

  shallow
• send_broadcast

  Send a campaign now, or schedule it with scheduled_at. This mails every contact in the segment and cannot be undone once started — run preview_broadcast first. A campaign bigger than the day's remaining quota is not rejected: it sends what it can and stops as 'paused', then continues later. That is expected, not an error to retry. An A/B test sends its sample, goes to 'testing', and sends the rest to the winner after decide_after_minutes or when pick_broadcast_winner is called. A send-time test is scheduled by its variants' send_at and does not accept scheduled_at.

  shallow
• send_email

  Send a transactional email, immediately or scheduled. Use scheduled_at with a relative phrase like 'in 3 days' or an ISO timestamp. The From domain must already be verified.

  shallow
• send_template_email

  Send an email built from a stored template. Variable values are HTML-escaped on substitution, so they are safe to fill from user-supplied text.

  shallow
• set_automation_status

  Activate, pause or return an automation to draft. A new automation is a draft and sends nothing until it is set to 'active'. Pausing ('paused' or 'draft') holds everyone on their current step: nobody is sent a step and nobody new is enrolled, but nobody's sequence ends, and setting 'active' again continues each person from where they were, with steps that came due meanwhile going out from the next worker run at the usual pace. So pause, rather than delete, to fix a step: a step's content is read when it is sent. Activating does not re-check the sending domain; if it is no longer verified each enrolment fails at its next step. Returns the automation. Only ask for this when a person wants the sequence started or stopped: activating starts mail to everyone it enrols.

  shallow
• set_email_preferences

  Set which topics a person receives. Only do this when they have actually asked — silently re-subscribing someone who opted out is what generates spam complaints.

  shallow
• suppress_many

  Stop sending to many addresses at once — the path for importing another provider's unsubscribe list before a first campaign. Without it, everyone who already opted out there gets mailed again here.

  shallow
• tag_contact

  Add or remove tags on a contact. Tags are flat labels — vip, beta, churned — as opposed to custom properties, which are declared fields with a value. They are lower-cased and spaces become hyphens, so VIP and vip are the same tag. Tagging reaches the person across every audience they are on. Call list_tags first to see what the workspace already uses, rather than inventing a synonym for an existing tag.

  shallow
• update_automation

  Change the rules that take someone out of a sequence (topic_key, exit_tags, required_tags, exit_on_reply), its reply_to, or its reenrollment. Steps and the trigger are fixed once created. A reenrollment change applies from the next enrolment; nobody already enrolled is touched. Fields left out keep their value; a null topic_key or reply_to, or an empty tag list, clears it. People already enrolled see the change from their next step, so a mistaken edit can be put back before it has ended anyone's sequence. Clear reply_to to have replies threaded in SendRaven again and stop the drip on their own. A topic_key that names no existing topic is refused with 422 unknown_topic, any field other than these is refused with 422 invalid_request, and an unknown automation_id answers 404 not_found.

  shallow
• update_contact

  Update a contact. Attributes are merged, so sending one field does not clear the rest.

  shallow
• verify_sending_domain

  Re-check a domain's DNS records now instead of waiting for the background monitor. Also restarts bounce-path (mail_from) verification when SES gave up before the MX record existed.

  shallow

Embed this server’s score

Tool count and median score across every tool in this server’s corpus — honest in a way a single cherry-picked tool’s badge wouldn’t be.

[![Vouch score](https://vouch.tools/api/servers/bc28120a-b577-4b6e-a921-571d2ea530ee/badge.svg)](https://vouch.tools/servers/bc28120a-b577-4b6e-a921-571d2ea530ee)