Connect your AI to Mailchimp

Give Claude, ChatGPT, Mistral or any MCP client secure access to Mailchimp — no official Mailchimp MCP server required. Proxoria turns Mailchimp's API into tools your AI can use, with per-user authentication and write actions gated by your approval.

What your AI can do with Mailchimp

Once connected, these tools appear automatically in your AI assistant:

  • list_audiencesread-only

    List audiences (lists) of the account.

  • list_membersread-only

    List members (subscribers) of an audience.

  • add_memberwrite · needs approval

    Add (or subscribe) a contact to an audience. Writes to Mailchimp, so it goes through the confirmation guardrail when enabled.

  • list_campaignsread-only

    List campaigns, optionally filtered by status.

  • get_campaign_reportread-only

    Get the performance report of a campaign: opens, clicks, bounces, unsubscribes, plus `list_stats` (this audience's own averages) and `industry_stats` (the sector's) — the two figures that tell you whether a result is good, rather than merely what it is.

  • create_audiencewrite · needs approval

    Create an audience. Mailchimp demands the details that make a mailing lawful, so they must come from the customer and cannot be invented: a physical postal address shown in every footer, the reminder telling recipients why they are hearing from you, and the default sender identity. Note that Mailchimp bills contacts per audience — the same person in two audiences counts twice.

  • add_memberswrite · needs approval

    Add several contacts to an audience in one call. Each contact's `status` is a statement about consent: 'pending' asks them to confirm by email, 'subscribed' asserts they already agreed. It defaults to 'pending' — only say 'subscribed' when the customer confirms they hold that consent.

  • get_memberread-only

    Get everything Mailchimp holds on one contact: status and unsubscribe reason, merge fields, tags, language, VIP flag, source, its own average open and click rates, a 1-to-5 rating, location — and the consent trail (signup and opt-in IP and timestamp, marketing permissions). Addressed by email; the contact id is derived here.

  • get_member_activityread-only

    Get a contact's recent activity — the campaigns they opened, clicked or bounced on. Narrow it with `activityFilters` to ask only for the events that matter, rather than reading the whole feed to find them.

  • search_membersread-only

    Search contacts across every audience by name or email, without knowing which audience they belong to.

  • list_segmentsread-only

    List an audience's segments and tags — how the audience is actually cut up for targeting.

  • get_segmentread-only

    Get one segment, with how many contacts it currently holds and — for a rule-based segment — the conditions behind it. Read an existing segment before writing one: its `options` show the exact shape a condition takes for each field type.

  • create_segmentwrite · needs approval

    Create a segment of an audience, in one of two shapes. Give `emails` for a static segment — a fixed list you fill yourself, which is what a tag is. Give `match` and `conditions` for a rule-based segment, which Mailchimp recalculates on its own as contacts change. A condition's exact shape depends on the field it tests, so copy one from an existing segment read with get_segment rather than guessing.

  • update_segmentwrite · needs approval

    Rename a segment or replace its conditions. Mailchimp requires the name on every call, even when only the conditions change — so pass the current name if you are not renaming it. Replacing the conditions replaces them entirely.

  • update_segment_memberswrite · needs approval

    Add or remove contacts of a static segment, up to 500 of each per call. Only works on a static segment: a rule-based one has no fixed membership to edit, change its conditions with update_segment instead. Addresses absent from the audience are ignored rather than created.

  • search_tagsread-only

    Search an audience's tags by name, or list them all when no name is given. Call this before add_member_tags: Mailchimp creates a tag silently when the name does not match an existing one, so a difference of case or spelling quietly makes a second tag nobody notices.

  • add_member_tagswrite · needs approval

    Tag or untag a contact. Each tag carries its own status, so one call can both add and remove. Tags are the everyday way to segment in Mailchimp — a contact added without one is hard to reach again.

  • create_campaignwrite · needs approval

    Create a campaign. It is born as a draft and stays one: this connector exposes no way to send or schedule, because that reaches thousands of people and cannot be undone. Give it content with set_campaign_content, then a human sends it from Mailchimp.

  • update_campaignwrite · needs approval

    Change a draft campaign's subject, sender, preview text or recipients, without touching its content. Only a campaign that has not been sent can be changed.

  • get_campaign_contentread-only

    Get a campaign's content, in HTML and plain text.

  • set_campaign_contentwrite · needs approval

    Set a campaign's content — raw HTML, plain text, or a template with its sections filled in. Replaces whatever was there. The campaign remains a draft until a human sends it.

  • list_templatesread-only

    List the email templates of the account.

  • get_templateread-only

    Get one template — its name, category and when it was last edited.

  • create_templatewrite · needs approval

    Create a template from raw HTML. Mailchimp's API only creates Classic templates: the result will not open in the drag-and-drop editor, so the customer will have to come back here — or to raw HTML — to change it. Mark the parts a campaign should fill with mc:edit attributes, otherwise the template has no editable sections.

  • update_templatewrite · needs approval

    Replace a template's name and HTML. Despite being a PATCH, Mailchimp requires both every time — there is no way to amend part of a template, so read it first and send back the whole thing. Classic templates only, like create_template.

  • list_campaign_reportsread-only

    List the reports of sent campaigns. Bound the period with `sinceSendTime` and `beforeSendTime` to compare one quarter against another — Mailchimp has no comparison endpoint, so this is how a trend gets built.

  • get_campaign_open_detailsread-only

    List who opened a campaign, contact by contact — the report to cross with a CRM to find who is paying attention. Automated opens are excluded by default; since mail apps began preloading images, counting them overstates interest.

  • get_campaign_click_detailsread-only

    List the links of a campaign and how many contacts clicked each one.

  • get_campaign_email_activityread-only

    Replay every recorded action of a campaign contact by contact — opens, clicks and bounces, each with its timestamp. The heaviest report of the connector: prefer get_campaign_open_details or get_campaign_click_details for a plain answer, and use this with `since` to pick up only what has happened since a given moment.

  • get_campaign_recipientsread-only

    List who a campaign was sent to, with each contact's delivery status.

  • get_campaign_abuse_reportsread-only

    List the spam complaints a campaign drew. Small, and the earliest warning that deliverability is slipping.

  • get_audienceread-only

    Get one audience: its name, the postal address and permission reminder Mailchimp shows in every footer, the default sender identity, and its stats — member count, unsubscribes, average open and click rate, and when it last sent.

  • update_audiencewrite · needs approval

    Change an audience's settings. The contact block and the permission reminder are what make a mailing lawful and appear in every footer, so they come from the customer and are never invented. Only the fields you give are touched.

  • list_audience_abuse_reportsread-only

    List the spam complaints raised against this audience, across all its campaigns. A rising count here is the earliest sign that deliverability is about to suffer.

  • get_audience_abuse_reportread-only

    Get one spam complaint: who reported it, on which campaign, and when.

  • get_audience_activityread-only

    The audience's recent activity, day by day: sends, opens, clicks, subscribes, unsubscribes and bounces. The shape of the list's health over time rather than one campaign's numbers.

  • list_audience_email_clientsread-only

    Which email clients this audience actually reads in, with a count per client. Worth checking before deciding how much a rendering quirk matters.

  • list_member_tagsread-only

    List the tags on one contact. Give the email address; Mailchimp's own identifier is derived from it.

  • list_segment_membersread-only

    List the contacts a segment currently contains. For a rule-based segment this is evaluated when you ask, so it can differ from the last time you looked.

  • add_segment_memberwrite · needs approval

    Add one contact to a static segment. Rule-based segments decide their own membership and reject this.

  • get_campaignread-only

    Get one campaign: its type, status, audience or segment, subject, sender, schedule, and the counts it has accumulated. Read this before changing anything — status tells you whether it is still a draft.

  • list_campaign_feedbackread-only

    List the internal review comments left on a campaign by the team, before it went out. Not customer feedback — this is the draft's comment thread.

  • get_campaign_feedbackread-only

    Get one review comment on a campaign, with who wrote it and which block it points at.

  • get_campaign_send_checklistread-only

    Mailchimp's own pre-flight check on a draft: what is still missing, what is only a warning, and whether the campaign is ready to send. The right thing to read before telling anyone a draft is finished.

  • search_campaignsread-only

    Search campaigns by name, subject or content across the account. The way to find a campaign when all you have is a phrase from it.

  • list_merge_fieldsread-only

    List an audience's merge fields — the custom fields a contact can carry, with their tag, type and whether they are required. Read this before adding contacts: the tags are what `mergeFields` expects, and an invented one is silently dropped.

  • get_merge_fieldread-only

    Get one merge field with its type, default value and options.

  • list_interest_categoriesread-only

    List an audience's interest categories — the groups a contact can opt into, as they appear on the signup form.

  • get_interest_categoryread-only

    Get one interest category, with how it is presented on the form.

  • list_interestsread-only

    List the interests inside a category, with the number of subscribers who picked each. Their ids are what a segment condition on interests refers to.

  • get_interestread-only

    Get one interest and how many subscribers it holds.

  • list_member_notesread-only

    List the notes left on a contact by the team. Free text that decides nothing, and often where the context behind a contact's status actually lives.

  • get_member_noteread-only

    Get one note on a contact, with its author and date.

  • add_member_notewrite · needs approval

    Add a note to a contact. It is internal, visible to the team in Mailchimp, and never sent to the contact.

  • list_automationsread-only

    List the classic automations of the account — the sequences that fire on their own, such as a welcome series. Each carries its status, the audience it runs on and its aggregate report.

  • get_automationread-only

    Get one automation: its trigger, its status, the audience or segment it targets, and how it has performed since it started.

  • list_automation_emailsread-only

    List the emails that make up an automation, in order, each with its delay and its own figures. This is how you see which step of a sequence loses people.

  • get_automation_emailread-only

    Get one email of an automation, with its delay, its content settings and its report.

  • list_automation_email_queueread-only

    List the contacts currently waiting for one automation email — who is mid-sequence, and when each is due to receive it.

  • get_automation_email_subscriberread-only

    Where one contact stands in an automation email's queue. Give the email address; Mailchimp's identifier is derived from it.

  • list_automation_removed_subscribersread-only

    List the contacts taken out of an automation before it finished. The complement of the queue: who dropped out of the sequence.

  • get_automation_removed_subscriberread-only

    Check whether one contact was removed from an automation, and when.

  • list_campaign_foldersread-only

    List the folders campaigns are filed in, with how many each holds. The way to find a campaign by where it was put rather than by its name.

  • get_campaign_folderread-only

    Get one campaign folder and its campaign count.

  • list_template_foldersread-only

    List the folders templates are filed in, with how many each holds.

  • get_template_folderread-only

    Get one template folder and its template count.

  • list_marketing_audiencesread-only

    List audiences through Mailchimp's newer contact-oriented endpoints. These are the same audiences `list_audiences` returns; what differs is the shape of the response and the fact that contacts here are addressed by their own id rather than by a hash of their email.

  • get_marketing_audienceread-only

    Get one audience through the newer endpoints. The id is the same as an audience's list id.

  • list_audience_contactsread-only

    List an audience's contacts through the newer endpoints, each with its own contact id. Use `list_members` instead when you need the merge fields, tags and consent history — that response is richer.

  • get_audience_contactread-only

    Get one contact by its contact id, which is not the hash the member endpoints use. Take it from list_audience_contacts.

  • list_connected_sitesread-only

    List the websites connected to the account, each with its domain and whether its tracking pixel is installed and firing.

  • get_connected_siteread-only

    Get one connected site, with its store link and the state of its script.

  • list_facebook_adsread-only

    List the Facebook and Instagram ads run from Mailchimp, with their status, budget, audience and results.

  • get_facebook_adread-only

    Get one Facebook or Instagram ad: its creative, its targeting, its spend and what it returned.

  • get_campaign_abuse_reportread-only

    Get one spam complaint against a campaign: who raised it and when.

  • get_campaign_adviceread-only

    Mailchimp's own read on a campaign's numbers — where it beat or missed the account's and the industry's averages, in plain sentences. Useful as a second opinion, not as a verdict.

  • get_campaign_link_clicksread-only

    The figures for one link in a campaign: total clicks, unique clicks, and its share of all clicks. The link id comes from get_campaign_click_details.

  • list_link_clickersread-only

    Who clicked one particular link, and how many times each. This is the report that turns a click rate into a list of people to follow up.

  • get_link_clickerread-only

    Whether one contact clicked a particular link, and how often.

  • get_campaign_domain_performanceread-only

    How a campaign performed per recipient domain — gmail.com against outlook.com and the rest, with opens, clicks and bounces for each. Where a deliverability problem shows itself, because it almost always affects one mailbox provider and not the others.

  • get_campaign_ecommerce_activityread-only

    The products bought after a campaign, with revenue per product. Only meaningful when a store is connected and its orders are synced.

  • get_campaign_eepurlread-only

    How the campaign's public archive page and its social shares performed: views, likes, and referrers.

  • get_member_email_activityread-only

    One contact's timeline for one campaign: every open, every click and every bounce, timestamped. The finest grain the API offers on a single person.

  • get_campaign_locationsread-only

    Where a campaign was opened, by country and region, with a count for each.

  • get_member_open_detailsread-only

    Whether one contact opened a campaign, how many times and when. Bear in mind that image preloading inflates opens, so a single machine open proves little.

  • get_campaign_recipientread-only

    Whether one contact was sent a campaign, and what became of it — delivered, bounced, or held.

  • list_campaign_sub_reportsread-only

    The individual reports of a multi-variant campaign — an A/B test or an RSS series — each with its own figures. Reading only the parent report of such a campaign averages the variants together and hides which one won.

  • list_campaign_unsubscribesread-only

    Who unsubscribed because of this campaign, with the reason each gave. The most direct feedback a campaign produces, and the least read.

  • get_campaign_unsubscriberead-only

    The unsubscribe of one contact on one campaign, with its reason and timestamp.

  • list_facebook_ad_reportsread-only

    The report for every Facebook and Instagram ad: spend, reach, clicks and the revenue Mailchimp attributes to it.

  • get_facebook_ad_reportread-only

    The report for one ad, with its audience and what it returned.

  • get_facebook_ad_ecommerce_activityread-only

    The products bought after one ad, with revenue per product.

  • list_landing_page_reportsread-only

    The report for every landing page: visits, unique visitors, subscribes and conversion rate.

  • get_landing_page_reportread-only

    The report for one landing page, with its traffic and what it converted.

  • list_survey_reportsread-only

    The report for every survey: how many were started, how many finished, and the drop-off between.

  • get_survey_reportread-only

    The report for one survey, with its completion figures.

  • list_survey_question_reportsread-only

    The per-question report of a survey: how many answered each, and where people gave up.

  • get_survey_question_reportread-only

    The report for one survey question.

  • list_survey_question_answersread-only

    The individual answers to one survey question. For a free-text question this is the raw material worth summarising rather than counting.

  • list_survey_responsesread-only

    The responses to a survey, one per respondent, with who submitted each where the survey identified them.

  • get_survey_responseread-only

    One survey response in full, question by question.

  • list_all_ordersread-only

    Every order across every connected store, newest first. The account-wide view, when you do not want to walk store by store.

  • list_storesread-only

    List the connected stores. A store is what Mailchimp attributes orders and revenue to, and it is tied to one audience.

  • create_storewrite · needs approval

    Connect a store to Mailchimp. The id is yours to choose and is how your own system refers to it afterwards. Mailchimp requires `id`, `list_id`, `name` and `currency_code`.

  • get_storeread-only

    Get one store by id.

  • update_storewrite · needs approval

    Change a store. Only the fields you send are touched.

  • delete_storewrite · needs approval

    Delete a store from Mailchimp. It takes the figures that hang off it with it, and cannot be undone.

  • list_cartsread-only

    List the carts of a store. Carts include the abandoned ones, which is what an abandoned-cart automation acts on.

  • create_cartwrite · needs approval

    Add a cart to a store. The id is yours to choose and is how your own system refers to it afterwards. Mailchimp requires `id`, `currency_code`, `customer`, `order_total` and `lines`.

  • get_cartread-only

    Get one cart by id.

  • update_cartwrite · needs approval

    Change a cart. Only the fields you send are touched.

  • delete_cartwrite · needs approval

    Delete a cart from Mailchimp. It takes the figures that hang off it with it, and cannot be undone.

  • list_cart_linesread-only

    List the lines of a cart.

  • add_cart_linewrite · needs approval

    Add a cart line to a cart. The id is yours to choose and is how your own system refers to it afterwards. Mailchimp requires `id`, `product_id`, `product_variant_id`, `quantity` and `price`.

  • get_cart_lineread-only

    Get one cart line by id.

  • update_cart_linewrite · needs approval

    Change a cart line. Only the fields you send are touched.

  • delete_cart_linewrite · needs approval

    Delete a cart line from Mailchimp. It takes the figures that hang off it with it, and cannot be undone.

  • list_store_customersread-only

    List the customers of a store. A store customer is not an audience contact; Mailchimp links the two by email address.

  • create_store_customerwrite · needs approval

    Add a store customer to a store. The id is yours to choose and is how your own system refers to it afterwards. Mailchimp requires `id` and `opt_in_status`.

  • get_store_customerread-only

    Get one store customer by id.

  • update_store_customerwrite · needs approval

    Change a store customer. Only the fields you send are touched.

  • upsert_store_customerwrite · needs approval

    Create a store customer, or replace it entirely if its id already exists. Unlike an update, anything you leave out is cleared. Mailchimp requires `id`.

  • delete_store_customerwrite · needs approval

    Delete a store customer from Mailchimp. It takes the figures that hang off it with it, and cannot be undone.

  • list_store_ordersread-only

    List the orders of a store. Orders are what turn a campaign's opens and clicks into revenue in the reports.

  • create_orderwrite · needs approval

    Add a order to a store. The id is yours to choose and is how your own system refers to it afterwards. Mailchimp requires `id`, `customer`, `currency_code`, `order_total` and `lines`.

  • get_orderread-only

    Get one order by id.

  • update_orderwrite · needs approval

    Change a order. Only the fields you send are touched.

  • upsert_orderwrite · needs approval

    Create a order, or replace it entirely if its id already exists. Unlike an update, anything you leave out is cleared. Mailchimp requires `id`.

  • delete_orderwrite · needs approval

    Delete a order from Mailchimp. It takes the figures that hang off it with it, and cannot be undone.

  • list_order_linesread-only

    List the lines of an order.

  • add_order_linewrite · needs approval

    Add a order line to an order. The id is yours to choose and is how your own system refers to it afterwards. Mailchimp requires `id`, `product_id`, `product_variant_id`, `quantity` and `price`.

  • get_order_lineread-only

    Get one order line by id.

  • update_order_linewrite · needs approval

    Change a order line. Only the fields you send are touched.

  • delete_order_linewrite · needs approval

    Delete a order line from Mailchimp. It takes the figures that hang off it with it, and cannot be undone.

  • list_productsread-only

    List the products of a store. The catalogue Mailchimp draws on for product blocks and recommendations.

  • create_productwrite · needs approval

    Add a product to a store. The id is yours to choose and is how your own system refers to it afterwards. Mailchimp requires `id`, `title` and `variants`.

  • get_productread-only

    Get one product by id.

  • update_productwrite · needs approval

    Change a product. Only the fields you send are touched.

  • upsert_productwrite · needs approval

    Create a product, or replace it entirely if its id already exists. Unlike an update, anything you leave out is cleared. Mailchimp requires `id`.

  • delete_productwrite · needs approval

    Delete a product from Mailchimp. It takes the figures that hang off it with it, and cannot be undone.

  • list_product_imagesread-only

    List the images of a product.

  • add_product_imagewrite · needs approval

    Add a product image to a product. The id is yours to choose and is how your own system refers to it afterwards. Mailchimp requires `id` and `url`.

  • get_product_imageread-only

    Get one product image by id.

  • update_product_imagewrite · needs approval

    Change a product image. Only the fields you send are touched.

  • delete_product_imagewrite · needs approval

    Delete a product image from Mailchimp. It takes the figures that hang off it with it, and cannot be undone.

  • list_product_variantsread-only

    List the variants of a product. A variant is a size, a colour, a format.

  • create_product_variantwrite · needs approval

    Add a product variant to a product. The id is yours to choose and is how your own system refers to it afterwards. Mailchimp requires `id` and `title`.

  • get_product_variantread-only

    Get one product variant by id.

  • update_product_variantwrite · needs approval

    Change a product variant. Only the fields you send are touched.

  • upsert_product_variantwrite · needs approval

    Create a product variant, or replace it entirely if its id already exists. Unlike an update, anything you leave out is cleared. Mailchimp requires `id` and `title`.

  • delete_product_variantwrite · needs approval

    Delete a product variant from Mailchimp. It takes the figures that hang off it with it, and cannot be undone.

  • list_promo_rulesread-only

    List the promotion rules of a store. The rule holds the discount; the codes under it are what customers type.

  • create_promo_rulewrite · needs approval

    Add a promotion rule to a store. The id is yours to choose and is how your own system refers to it afterwards. Mailchimp requires `id`, `description`, `amount`, `type` and `target`.

  • get_promo_ruleread-only

    Get one promotion rule by id.

  • update_promo_rulewrite · needs approval

    Change a promotion rule. Only the fields you send are touched.

  • delete_promo_rulewrite · needs approval

    Delete a promotion rule from Mailchimp. It takes the figures that hang off it with it, and cannot be undone.

  • list_promo_codesread-only

    List the promo codes of a rule.

  • create_promo_codewrite · needs approval

    Add a promo code under a rule. The id is yours to choose and is how your own system refers to it afterwards. Mailchimp requires `id`, `code` and `redemption_url`.

  • get_promo_coderead-only

    Get one promo code by id.

  • update_promo_codewrite · needs approval

    Change a promo code. Only the fields you send are touched.

  • delete_promo_codewrite · needs approval

    Delete a promo code from Mailchimp. It takes the figures that hang off it with it, and cannot be undone.

Example prompts

Just ask your AI in plain language — it picks the right Mailchimp tool:

  • “List audiences (lists) of the account — from Mailchimp, in plain language.”
  • “List members (subscribers) of an audience — from Mailchimp, in plain language.”
  • “List campaigns, optionally filtered by status — from Mailchimp, in plain language.”
  • “Get the performance report of a campaign: opens, clicks, bounces, unsubscribes, plus `list_stats` (this audience's own averages) and `industry_stats` (the sector's) — the two figures that tell you whether a result is good, rather than merely what it is — from Mailchimp, in plain language.”

How it works

  1. Create your Proxoria account and add your MCP endpoint to Claude or ChatGPT.
  2. Connect Mailchimp with your API key — each user connects their own account, credentials encrypted at rest.
  3. Your AI instantly gets the Mailchimp tools. Write actions wait for your approval in the dashboard before anything changes.

Frequently asked questions

Does Mailchimp have an official MCP server?
You don't need one. Proxoria exposes Mailchimp to your AI through the Model Context Protocol, so you can use it from Claude, ChatGPT, Mistral or any MCP-compatible client — no official Mailchimp MCP server required.
What can my AI do with Mailchimp through Proxoria?
It gets 161 tools: list_audiences, list_members, add_member, list_campaigns, get_campaign_report, create_audience, add_members, get_member, get_member_activity, search_members, list_segments, get_segment, create_segment, update_segment, update_segment_members, search_tags, add_member_tags, create_campaign, update_campaign, get_campaign_content, set_campaign_content, list_templates, get_template, create_template, update_template, list_campaign_reports, get_campaign_open_details, get_campaign_click_details, get_campaign_email_activity, get_campaign_recipients, get_campaign_abuse_reports, get_audience, update_audience, list_audience_abuse_reports, get_audience_abuse_report, get_audience_activity, list_audience_email_clients, list_member_tags, list_segment_members, add_segment_member, get_campaign, list_campaign_feedback, get_campaign_feedback, get_campaign_send_checklist, search_campaigns, list_merge_fields, get_merge_field, list_interest_categories, get_interest_category, list_interests, get_interest, list_member_notes, get_member_note, add_member_note, list_automations, get_automation, list_automation_emails, get_automation_email, list_automation_email_queue, get_automation_email_subscriber, list_automation_removed_subscribers, get_automation_removed_subscriber, list_campaign_folders, get_campaign_folder, list_template_folders, get_template_folder, list_marketing_audiences, get_marketing_audience, list_audience_contacts, get_audience_contact, list_connected_sites, get_connected_site, list_facebook_ads, get_facebook_ad, get_campaign_abuse_report, get_campaign_advice, get_campaign_link_clicks, list_link_clickers, get_link_clicker, get_campaign_domain_performance, get_campaign_ecommerce_activity, get_campaign_eepurl, get_member_email_activity, get_campaign_locations, get_member_open_details, get_campaign_recipient, list_campaign_sub_reports, list_campaign_unsubscribes, get_campaign_unsubscribe, list_facebook_ad_reports, get_facebook_ad_report, get_facebook_ad_ecommerce_activity, list_landing_page_reports, get_landing_page_report, list_survey_reports, get_survey_report, list_survey_question_reports, get_survey_question_report, list_survey_question_answers, list_survey_responses, get_survey_response, list_all_orders, list_stores, create_store, get_store, update_store, delete_store, list_carts, create_cart, get_cart, update_cart, delete_cart, list_cart_lines, add_cart_line, get_cart_line, update_cart_line, delete_cart_line, list_store_customers, create_store_customer, get_store_customer, update_store_customer, upsert_store_customer, delete_store_customer, list_store_orders, create_order, get_order, update_order, upsert_order, delete_order, list_order_lines, add_order_line, get_order_line, update_order_line, delete_order_line, list_products, create_product, get_product, update_product, upsert_product, delete_product, list_product_images, add_product_image, get_product_image, update_product_image, delete_product_image, list_product_variants, create_product_variant, get_product_variant, update_product_variant, upsert_product_variant, delete_product_variant, list_promo_rules, create_promo_rule, get_promo_rule, update_promo_rule, delete_promo_rule, list_promo_codes, create_promo_code, get_promo_code, update_promo_code, delete_promo_code. For example, list audiences (lists) of the account.
Is the Mailchimp connector read-only?
No — it can also make changes. Write actions go through Proxoria's confirmation guardrail by default: your AI proposes them, and you approve each one from your dashboard before anything is written to Mailchimp.
How do I connect Mailchimp to my AI?
Create a Proxoria account, connect Mailchimp with your API key, and add your Proxoria MCP endpoint to Claude or ChatGPT. Your AI instantly gains the Mailchimp tools.

Ready to connect Mailchimp to your AI?

Set it up in minutes — no code, secure by default.

Get started free

About Proxoria. Proxoria connects AI assistants — Claude, ChatGPT, Mistral and any Model Context Protocol (MCP) client — to the business apps you already use, turning each app's API into tools your AI can call, with per-user authentication and write actions gated by human approval.