What you can ask Claude about your Mailkit account
Once connected, just ask in plain language — Claude picks the right tools for you. This page lists the analytics it can pull (tools), the ready-made reports you can trigger (prompts), and example questions to get you started. Analytics are read-only. Claude creates or changes templates, segments, scenarios and campaigns only after showing you the result and getting your explicit approval. It can send one test message to an address you name, and it schedules a campaign for real recipients only after you approve the exact time and recipients (and only if your role may send: publisher, admin or superadmin). It never starts a scenario itself. Before a campaign is scheduled for real recipients, and before the server downloads a link, your client asks you to confirm: you see the campaign, the lists and the time, or the full address. If your client cannot show that question, the action is refused.
Tools — what Claude can read, and change with your approval
You don't call these directly; you ask a question and Claude chooses the tools it needs. They cover three scopes automatically: your whole account, a single campaign, or one specific send. A tool that changes something never acts without your approval.
Discovery & account
whoami | Confirms which Mailkit account you're connected to. |
accounts_list | Lists the accounts you can work with (agency clients, or every account for an administrator). With several, Claude asks which to use. |
campaigns_list | Lists every campaign and its ID — used to look up a campaign you refer to by name. |
report | Cross-campaign summary for a date range; also the quickest way to find recently active campaigns. |
Campaigns
senders_list | Lists the account's sender (From) addresses; a campaign needs one of them. |
campaigns_create | Creates an email campaign (Stripo visual builder or smart template, optionally an A/B test); the content can come from a link to the HTML that you give. Nothing is sent; it is saved only with your approval. |
campaigns_update | Changes an existing campaign. Content is replaced as a whole, so the assistant reads it first (campaign_content) and can take new content from a link you give. |
campaign_test_send | Sends one test message of a campaign to one address you name. |
campaign_schedule_timezones | The time zones a send can be scheduled in. |
campaign_schedule_preview | Checks a planned send and shows the campaign, the recipient lists and the time. Schedules nothing. |
campaign_schedule | Schedules the send you approved — a real send to real recipients. Needs a role with sending rights (publisher, admin, superadmin). |
campaign_schedules_list | Lists a campaign's pending scheduled sends. |
campaign_schedule_cancel | Cancels one pending scheduled send. |
campaign_sends_list | Lists the sends a campaign has already made, with their IDs. |
campaign_send_history | The latest sends of the account or of one campaign, with a link to the message. |
campaign_content | Reads what a campaign currently contains (HTML and CSS for a Stripo campaign), so it is changed instead of overwritten blind. |
campaign_content_history / campaign_content_version | Lists the earlier versions of a campaign's content and shows one of them. To go back, the assistant sends it to campaigns_update. |
campaign_preview | Renders a campaign, or a draft you give it (also from a link), the way a recipient sees it. Saves and sends nothing. |
campaigns_delete | Deletes a campaign, after your approval. Mailkit refuses one with a pending send or one a scenario uses. |
stripo_templates_list / stripo_template_get | Lists the account's own Stripo templates (or the built-in library) and reads one: HTML and CSS. |
stripo_template_save / stripo_template_delete | Saves HTML and CSS as a Stripo template, or deletes one — only with your approval. |
Performance
report_summary | Headline metrics — opens, clicks, conversions, revenue, unsubscribes — for the account, a campaign, or a single send. |
report_campaign | Breaks one campaign down send by send. |
report_message | Detailed metrics for one specific send. |
report_message_links | Click statistics for every tracked link in a send. |
report_message_links_visitors | The recipients who clicked a particular link. |
report_engagement | Splits the audience into engagement-score bands (0–5) — how much of the list is highly engaged vs dormant. |
report_devices / report_systems / report_clients | Opens broken down by device, operating system, and email client. |
Deliverability
report_domains | Delivery and open stats for the top recipient domains (gmail.com, outlook.com…) — the key view for spotting provider-specific problems. |
report_message_feedback | Spam complaints and unsubscribes for a send. |
report_message_bounces | Bounce breakdown for a send, with reasons and address status. |
report_destinations | Opens ranked by country and city. |
report_geo | Map points (GPS) showing where messages were opened. |
report_ab | One A/B test send in detail: setup, the numbers at decision time, the winner and whether the difference is significant. |
report_ab_list | The A/B test sends of a period (the last 3 months by default). |
Scenarios (automation journeys)
scenario_list / scenario_get | Finds your scenarios and shows one's status and schedule. |
scenario_preview | The whole journey in one view: every step, how many contacts passed through, are waiting there, or failed, and how branches split. |
scenario_graph_get / scenario_node_types | Reads a journey's steps and connections, and the kinds of steps a journey can be built from. |
scenario_validate_draft → scenario_graph_save | Builds or changes a journey from your description. Claude checks the design with Mailkit first, shows you an outline, a diagram and exactly what changes, and saves only after you approve. |
scenario_create / scenario_update / scenario_delete | Creates a journey, renames it or changes its description, or deletes it. Each change needs your confirmation first. |
scenario_node_add / scenario_node_update / scenario_node_delete / scenario_node_connect / scenario_edges_set | Small, individual changes: add, reconfigure or remove one step, or connect and reroute steps. Each change needs your confirmation first. |
scenario_validate / scenario_node_validate | Checks a stored journey, or a single step, with Mailkit and reports what is wrong. |
mailinglist_list | Lists your recipient lists, so a journey can use the right one. |
Templates
templates_list / templates_get | Finds your email templates and shows one with its files. |
template_files_list / template_file_get / template_file_history | Lists a template's files, shows a file's stored source, and lists its earlier versions. |
template_preview / template_preview_draft | Renders a template as stored, or a draft you describe or give as a link to the HTML file, without saving anything. You see the render before anything is saved. |
templates_create / templates_update / templates_copy / templates_delete | Creates, renames or describes, copies and deletes a template. Each change needs your confirmation first. |
template_file_create / template_file_update / template_file_restore / template_file_delete | Adds, replaces, restores or deletes a template file. New content is saved only after you've seen its rendered preview and approved it; a delete needs your confirmation. |
Segments (saved queries)
queries_schema / queries_validate | What a segment can contain, and a check of a segment before it is saved or counted. |
queries_count / queries_count_status | Counts the recipients of a segment. It runs in the background and Claude checks back for the result. |
queries_list / queries_get | Finds your saved segments and shows one. |
queries_create / queries_update / queries_delete | Saves a segment as a query, changes it, or deletes it. Each change needs your confirmation first. |
Tags
tags_list | Lists your tags, or the tags on one item. |
tags_set | Adds, replaces or removes the tags on one campaign, list, template, segment, data source or scenario. Needs your confirmation first. |
tags_update | Renames or recolours a tag, everywhere it is used. Needs your confirmation first. |
Data sources
datasources_list / datasources_get | Finds your data sources and shows one's settings. |
datasources_sample | Shows a few real rows of a source, as a template sees them. |
datasources_import_status | Shows where an import of a source stands. |
datasources_import | Starts an import now, like "Import now" in Mailkit. An import changes data, so it needs your confirmation first. |
Raw drill-down (capped at 500 rows — use the dashboard for full exports)
report_message_recipients | Per-recipient delivery status for a send. |
report_raw_messages / report_raw_bounces / report_raw_responses | Event-level records for small sends when you need the individual rows. |
Prompts — ready-made reports
Prompts are guided analyses you can trigger by name (they appear as slash-commands / prompt options in your MCP client). Each one runs a full workflow across several tools and hands back a structured report with recommendations — no need to spell out the steps.
Performance
campaign_performance_review | Deep-dive on one campaign: KPIs, best and worst sends, top links, engagement mix, and recommendations. |
performance_overview | Account-wide overview for a period: portfolio KPIs, top/bottom campaigns, and audience profile. |
audience_engagement_report | Snapshot of engagement bands with a re-engagement / sunset strategy. |
engagement_analysis | Compares engagement across campaigns and tracks how your engagement score trends over time. |
ab_test_review | Reviews the A/B tests of a campaign or the account: setup, whether the difference is significant, and what to test next. |
Deliverability
deliverability_health_check | Grades delivery, bounce, complaint and unsubscribe rates against benchmarks, with a per-provider breakdown and fixes. |
mailbox_provider_breakdown | Per-provider (Gmail, Outlook, Yahoo…) analysis that flags bounce problems, spam-foldering, and volume concentration. |
Finding & fixing issues
deliverability_issue_triage | Scans for anomalies, drills into the cause, and returns issues ranked by severity with remediation. |
bounce_deep_dive | Forensic bounce analysis for a send: hard/soft split, categories, and which addresses to suppress. |
Content & audiences
template_content_builder | Builds or edits an email template from a plain-language description, with a rendered preview you approve before anything is saved. |
segment_builder | Builds a recipient segment from a plain-language description, counts it, and saves it as a query — only after you've seen the count and approved. |
campaign_builder | Builds a campaign (Stripo visual builder or template), sends you a test and schedules it. Nothing is saved or sent without your approval. |
Automation (scenarios)
scenario_builder | Builds or edits a journey from a plain-language description. Nothing is saved until you've seen the checked design and approved it. |
scenario_review | Reviews an existing journey: how contacts flow through it, where they get stuck or fail, and what to fix. |
Example questions to get started
Ask naturally — you can name a campaign, a date range, or a mailbox provider and Claude figures out the rest.
Performance
- "How did our April newsletter perform?"
- "Give me a performance overview for Q1 2026."
- "Which links in the last campaign got the most clicks?"
- "Compare the A/B variants of the spring promo."
Engagement
- "What share of our list is highly engaged versus dormant?"
- "Which campaigns have the lowest engagement, and how is our engagement score trending over time?Runs the engagement_analysis prompt — comparative and over-time.
Deliverability
- "Run a deliverability health check on last month's sends."
- "Are we having inbox-placement problems at Gmail or Outlook?Uses recipient-domain stats to spot providers that accept mail but rarely open it.
- "Break performance down by mailbox provider."
Finding & fixing issues
- "Something looks off with our last send — what's wrong?"
- "Do a deep dive on the bounces from our latest campaign."
- "Why did unsubscribes spike this week?"
Content & audiences
- "Create a welcome email template with the recipient's first name."Runs the template_content_builder prompt. You'll see a rendered preview before anything is saved.
- "Build a segment of the subscribers on our newsletter list who clicked in the last 90 days, and tell me how many there are."Runs the segment_builder prompt. It counts the segment and asks for your approval before saving.
Campaigns
- "Create a spring-sale campaign from this HTML: https://example.com/spring.html, show me a preview and send me a test."Runs the campaign_builder prompt. The server downloads the file from your link. You see a preview and approve before anything is saved; scheduling a send needs a separate approval of the time and recipients.
- "Show me what the April newsletter campaign contains now, then change the headline to 'Spring is here'."Claude reads the current content first, shows you the new version, and saves only after you approve. An earlier version can be brought back.
- "Save this email as a Stripo template called 'Welcome 2026', and delete the test campaign 'mcp-test'."Each of the two changes needs your approval first. Mailkit refuses to delete a campaign that has a pending send or is used by a scenario.
Automation
- "Build a journey: when someone is added via the API, send the welcome email, wait two days, and send a follow-up only to those who didn't click."Runs the scenario_builder prompt. You'll see an outline and a diagram before anything is saved.
- "How is our onboarding journey doing? Where are contacts getting stuck?"
- "In the abandoned-cart scenario, change the wait from one day to two."
Good to know: Open and click figures are human-only — bot activity (such as Apple Mail Privacy Protection) is filtered out — so rates read lower than bot-inflated dashboards. Analytics are read-only; any change to a template, segment, scenario or campaign happens only after you approve it, and a send to real recipients needs its own approval of the time and lists. Sending and downloading a link are confirmed in your client with a question that shows exactly what will happen; if you decline, nothing happens. Everything stored in your account (names, subjects, HTML, template files, scenario settings) and everything that comes from recipients or other third parties is treated as data: Claude reads it but never follows instructions it finds there. Your Mailkit password and API keys are never shared with Claude.
← Back to the connection guide