Using the MCP with Claude

As of October 20, 2026.

Claude is the assistant the Moonbrush MCP server is built and tested with. This page shows how to connect it and what to ask, job by job. Every prompt is ready to copy: replace the parts in square brackets with your own words. What the server is, and what it never does, is on The Moonbrush MCP server.

Connect

1. Add the server. On claude.ai or in Claude Desktop, open Settings, then Connectors, and add a custom connector with this address: https://mcp.moonbrush.ai/mcp. In Claude Code, run:

   claude mcp add --transport http moonbrush https://mcp.moonbrush.ai/mcp

   then claude mcp login moonbrush, or open /mcp inside Claude Code and sign in there.

2. Sign in as yourself. Moonbrush’s own sign-in page opens. Use your own Moonbrush email and password, the ones you use in the app. If your login has two-factor authentication on, type the code from your authenticator app.

3. Start a chat. Claude is now connected as you, with the same workspaces and the same role you have in the app.

Check where you are

Start with:

• Which Moonbrush workspace am I in, and what can I do here?
• Switch me into [client name].

The session opens by saying who is signed in and where:

You’re signed in as [your name] ([your email]). Your agency is Moonbrush. You’re working in [the workspace].

Clients you can work in: [each client, by name].

Before any change, I’ll ask your yes and name the client.

Every answer after that names the workspace. The server’s own menu also offers ready starts: Start with a client, Plan an audience, What needs my yes and Where does the campaign stand.

1. Onboard a client

• Claude onboards a client in the app’s order: the client’s record, the Outcome, the tracking tag, then the note you send the client. Ask where onboarding stands at any time, and Claude names the next step.
• A new client takes two things, as the app’s New client does: its name and its website. One yes covers it, and with a website Moonbrush starts reading the site as soon as the client is added.
• Reading the client’s website is a paid run under the platform’s cost cap: Claude says the cost and waits for your yes. Each line it finds carries a label: Confirmed, Our reading, Waiting for a yes, or We looked and it was not there.
• The kickoff asks Moonbrush’s own questions, word for word, one at a time, and files each answer as the client’s, from their marketing lead. A person named in an answer is written as their role, never their name.
• Files never go through the chat. Claude gives you a one-time link that works for a short time; you drop the file in the app, in your browser, then tell Claude it is in.

Try:

• Make a new client: [client name], [their website].
• Where does onboarding stand for [client name], and what's next?
• Read [client name]'s website, [their website], into their record.
• Run the kickoff for [client name] with me, one question at a time.
• Give me a link to drop [client name]'s media brief into their record.
• In [client name], make the Outcome: [what we want people to do]. Then set up their tracking tag for their web team.

2. Build audiences

• Claude starts from the question the brief really asks (what people tend to do, who they are, or what they are in the middle of right now), then builds from what Moonbrush serves today, says why each signal fits, and labels every assumption.
• For a brief with several audience groups it plans first: it asks the size you need and where the ads will run, counts every group and how many are left once the earlier groups are taken out, and builds nothing until you say yes to the plan.
• Every count is Moonbrush’s own. For a large audience, Moonbrush says the cost and asks its own yes first. A list you upload is matched in two paid steps, each on its own yes.
• A do-not-contact list is kept out when an audience is built, and out of every list after. Nobody on it is ever named.
• Once an audience is built, Claude can say who is in it: age, top states, income and gender, as the app’s Analysis page shows them.

Try:

• Plan the audiences for [client name] from this brief: [paste the brief or your call notes].
• Build one audience for [client name]: [who, in your words]. Count it before you save.
• I have a list of [what the list is] for [client name] to target from. Give me the link to upload it.
• Keep [client name]'s do-not-contact list, [list name], out of the audiences we build.
• In [client name], who is in the [audience name] audience?

3. Run a campaign

• A campaign is made as a draft for one Outcome, with your audiences as its ad groups. The flight and budget come from your words, or from the client’s media brief. One campaign per Outcome, unless you give a reason for a second.
• Taking it live runs Moonbrush’s go-live check first. If anything is missing (an audience still building or too small, an ad group with no ad), Claude says exactly what, and nothing changes.
• Pause, resume, end, a new budget, new dates, an audience swap or a widened audience each change the plan in Moonbrush, on its own yes. Claude then tells you the matching step to take in the ad platform’s console; say “done” and it notes your word. Pausing in Moonbrush does not stop spend in the ad platform: that step is yours.
• The campaign’s package is built in Moonbrush, and you download it in the app. The first download is the hand-over.

Try:

• In [client name], make a campaign called [campaign name] for the [Outcome name] Outcome, with [audience name] and [audience name] as its ad groups, flight [first day] to [last day], budget [amount].
• In [client name], bring in the ad image for the [campaign name] campaign and put it on [audience name].
• In [client name], is the [campaign name] campaign ready to go live? If it is, take it live.
• In [client name], pause the [campaign name] campaign.
• In [client name], build the package for the [campaign name] campaign and tell me where to download it.

4. Report

• The client weekly is one document a week, named by the Sunday the week ends. Claude checks which inputs are in (Moonbrush’s close for the week, the ad platform’s delivery report, the client’s tag), builds the version, and shows it the way the client will read it.
• Every number comes from Moonbrush with its source and its date; a dash means not in yet, never zero. Claude writes the words only and never types a number.
• Claude makes the weekly’s Word file and gives you a link to drop it into Drive. You send it yourself; say so, and Claude marks it sent.
• An Outcome speaks one number: “did it from our ads”, in Moonbrush’s own sentence. Claude never promises a result.

Try:

• In [client name], is this week's client weekly ready? Tell me what's still missing.
• In [client name], here is the delivery report for the [campaign name] campaign, covering [first day] to [last day]. Give me the link to bring it in.
• In [client name], build this week's client weekly and show it to me the way the client will read it.
• In [client name], how many did it from our ads for the [Outcome name] Outcome?
• In [client name], how is the [campaign name] campaign doing? Show me its campaign table and its readout.

Cleaning up

• One thing at a time. Claude first says what goes and what stays, then asks you to type the workspace’s name and the item’s own name.
• An Outcome is archived, never deleted: its list stops refreshing, everything it learned stays, and you can restore it.
• A deleted audience can be restored for a limited time, from Deleted in the app.
• A campaign’s delete is for good, and only when Moonbrush allows it (it keeps a campaign with history). A campaign has no archive.
• A line removed from the client’s record is kept in its history. A share link can’t be taken back: it stops working on its day.

Try:

• In [client name], what happens if I delete the [audience name] audience?
• In [client name], archive the [Outcome name] Outcome.
• In [client name], restore the [Outcome name] Outcome.
• In [client name], remove the line in the client's record that says [what it says].

What it won’t do

• Change anything without your yes. Every save, upload or switch of workspace, like every other change, asks your yes first, with the workspace named. Every client works the same way.
• Touch an ad platform. Nothing Claude does through the server sends anything to an ad platform. It changes the plan in Moonbrush and tells you the step to take there yourself.
• Name a person. Claude never shows anyone on a list: no names, no rows, no contact details, not even in a sample.
• Move people out of Moonbrush. No export, no download, no push. The package is downloaded by you, in the app.
• Send anything. Claude installs no tag and sends nothing to the client. The note to the client, any link for their marketing lead and the weekly are yours to send.
• Some things are the app’s alone: renaming an audience or an Outcome, connecting Google Drive, a new tag key or stopping the tag, and any campaign setting beyond the ones above.

FAQ

How do I sign in? With your own Moonbrush email and password, the same as the app, on Moonbrush’s own sign-in page. Claude never sees your password.

Where is my code? In your authenticator app, the same one you use for the app. Type it on the sign-in page.

Which login should I use? Your own, the one you use in the app, never a shared one. A Moonbrush platform administrator’s login reads everywhere and changes nothing.

Why does every change ask for the workspace’s name? A chat works in one workspace at a time, and every change lands there. Your yes to a question that names it exactly is how Claude knows you mean that workspace: a name that doesn’t match changes nothing. Some Claude apps also show a confirmation box, which Claude can neither see nor answer. If Claude says this app can’t ask for your yes, reading and planning still work, and the change is made from Claude Code or in the app.

Claude says the platform is busy. Moonbrush is busy with other reads; try again in a minute. Claude never retries on its own.

I was signed out in the middle of a chat. Your Moonbrush session ended (a password change or a sign-out everywhere ends it). Sign in to the server again from your connector settings.

The Moonbrush MCP serverWhat it is, how sign-in works, what leaves the platform through it, and its claims.