NewAI assistants over MCP

Work in Moonbase from your AI assistant

Draft campaigns, build segments and create automations from the assistant you already use.

Use cases

What you can ask it to do

Your assistant works with the same campaigns, segments and automations you build in Moonbase. Ask in plain words, check what it made, and carry on in the app or in the conversation. Campaigns and automations it writes start as drafts.

Campaigns

Draft a campaign

You ask
“Write a campaign for Helios owners about version 2.0, with a 20% upgrade coupon for each of them. Show me the email, then schedule it for Tuesday morning.”
  • Writes the campaign as a draft, with a coupon block that gives every recipient their own code create_campaign
  • Shows you the email as a customer would get it, drawn right in the conversation where your assistant supports it preview_campaign
  • Tells you how many it will reach, and sends a test to your own inbox get_campaign_audience send_test_campaign
  • Schedules it once you say yes, for 10:00 in each customer's own time zone, if you connected it with Everything your role allows schedule_campaign

More about campaigns

The Moonbase dialog for sending the Helios 2.0 campaign: a 20% upgrade code of their own for each recipient, Schedule chosen for 3 November 2026 at 10:00, delivered at the best time for each customer (10:00 in their own time zone), and a test to send yourself first

Customer segments

Build a segment

You ask
“How many Helios owners haven't opened it in two months and have spent at least €100? If it's over a thousand, save them as a segment.”
  • Writes the rule from your sales and license data and tries its count before saving anything preview_rule
  • Saves it as a segment that keeps itself up to date create_group
  • Adds customers to a list, or takes them off, when you name them change_list_members

More about segments

The live preview of the Helios owners who went quiet segment: 1,284 customers match, with a sample of five of them and what each has spent

Automations

Set up an automation

You ask
“When someone cancels a subscription, ask them why. Two weeks later, if they haven't come back, send them 30% off.”
  • Writes the trigger, steps and emails in one go and saves the automation as a draft create_automation
  • Shows each email before it is ever sent preview_automation_email
  • Once it is on, reports who entered and finished, who opened each email and what it earned get_automation_stats get_automation_revenue

More about automations

The draft automation Ask why subscribers cancel in the Moonbase builder: when a customer cancels a Helios Synth subscription, email to ask why, wait 14 days, and if they have not subscribed again, make them a personal 30% coupon and email it

Access

Three levels of access

Everyone on your team connects an assistant for themselves. It can do what their role in the account allows at the time, and no more than they approved, and it stops when they leave the team. When you connect it, you choose how far it can go.

Read only

It can look things up, but change nothing.

  • Find customers and what they own
  • Read campaigns and automations with their figures
  • Query sales, MRR, licensing and email analytics

Look things up

Read and editDefault

It can also draft campaigns and automations, change lists and give licenses, but not refund, send, revoke or delete anything.

  • Draft campaigns and automations, and send tests to your team
  • Make lists and segments
  • Give licenses, extend trials and create coupons

Draft and prepare

Everything your role allows

It can also refund orders, send campaigns, turn on automations, cancel subscriptions, revoke licenses and delete.

  • Send and schedule campaigns
  • Turn on automations and add customers to them
  • Refund orders, cancel subscriptions and revoke licenses

Send, refund and delete

You stay in control

  • Even with Everything your role allows, Moonbase tells your assistant to say what will happen, and to whom, and to ask you before it sends, refunds, revokes or cancels.
  • Stopping something always works with Read and edit: it can pause, unschedule or cancel a campaign, and pause or turn off an automation.
  • If you ask for something the connection was not given, Moonbase refuses it and says how to allow it, so your assistant can tell you what it needs.
  • What it changes is recorded as you, and Moonbase emails you when an assistant is connected, with what it can do.
  • Disconnect stops one within seconds. People with the Developer role see everyone's assistants under Integrations, and can disconnect any of them.
What an assistant connected to Moonbase can reach, area by area, and that it cannot refund, send, revoke or delete

Also in the conversation

Answers from your own figures

The same connection reads your dashboard's analytics and the rest of your account. Ask how last month's launch went, which country is growing fastest or which devices a customer's license is on, and the answer comes from the numbers you see in Moonbase.

Sales and MRR
Revenue, units, subscriptions, MRR and churn, by product, country or channel, counted the way your dashboard counts them.
Customer support
Find a customer by email or name, see what they own and what Moonbase emailed them, and resend a receipt.
Licenses and trials
See which devices a license is activated on, give a license or extend a trial.
Prices and discounts
Create a coupon, put a discount on one product or run a promotion across several.
Email results
Deliveries, opens and clicks, by campaign or by kind of email.
Product funnel
From download to trial, purchase and activation, product by product.

How to connect it

Moonbase runs an MCP server at https://mcp.moonbase.sh. Add it to any assistant that supports MCP connectors. There is no API key to copy: you sign in to Moonbase as yourself.

  1. Step 01

    Add Moonbase to your assistant

    In your assistant's settings, add a connector with the address https://mcp.moonbase.sh. Depending on the assistant, it is called a custom connector, an integration or an MCP server.

  2. Step 02

    Pick an account and how far it goes

    Your assistant opens Moonbase. Sign in, choose the account and one of the three levels, and connect. Read and edit is the default.

  3. Step 03

    Ask

    Start with something small, like who bought Helios Synth last week, and work up to campaigns and automations.

Read the setup guide in our help center

The page Moonbase opens when an assistant connects, here Claude: how far it can go, with Read and edit chosen over Read only and Everything your role allows, the Helio Audio account, and Connect to Helio Audio

“As a solo indie dev, Moonbase has been one of the most valuable tools in my entire stack. I honestly don't know how I would've launched my plugin business without it.”

Moe Chaieb

time off audio · Read the letter

Frequently asked questions

Any assistant that lets you add an MCP connector, such as Claude or Cursor. Add https://mcp.moonbase.sh as a connector (some assistants call it a custom connector, an integration or an MCP server) and sign in to Moonbase. Assistants that can show apps in the conversation draw email previews right there; others get the email's subject and text.

Not unless you let it. Connected with Read and edit, the default, it cannot send or schedule campaigns, turn on automations, refund orders, cancel subscriptions, revoke licenses or delete anything, so the campaigns and automations it writes stay drafts for you to look over in Moonbase. Those actions need "Everything your role allows", and even then Moonbase tells the assistant to say what will happen and ask you first.

No. It acts as you, within what your role in the account allows at the time and no more than you approved when connecting. A role change reaches it within a minute, and it stops working when you leave the team.

No. Anyone on the team can connect their own assistant, whatever their role, by signing in to Moonbase when the assistant asks. There is no key or token to copy. API keys are for your own systems.

Yes. It works with customers, orders, licenses, subscriptions, trials, coupons, campaigns, automations, lists and segments, and your figures, as far as the role of the person who connected it allows.

Under Account settings, User, where Connected apps lists the assistants you connected, what each can do and when it was last used. Disconnect stops one within seconds. People with the Developer role also see everyone's under Account settings, Integrations, and can disconnect any of them.

Works with any assistant that supports MCP

Connect your assistant to Moonbase

Create a free account, add mcp.moonbase.sh to your assistant and choose how far it can go. You can change that, or disconnect it, at any time.