MaBrain

EP1 · With a client

Your AI was about to give the client a date that no longer stood

You create your first brain with three documents, see which one each answer comes from, and use a rule to decide which source wins.

The video is in Spanish.

Everything we used in the video, so you can repeat it step by step. Bodegas Ribera is a fictional client and all documents are examples.

What you'll build

Clara manages the Bodegas Ribera account at an agency. Her AI tells the client the website ships on 30 November. But at the last meeting they agreed on 15 December, and her AI doesn't know that. By the end of these steps, your AI checks the client's brain, shows you both dates with their citations and follows the rule you set.

At the end, your AI answers something like:

“Careful: the proposal says 30 November, but in the 8 October minutes delivery moved to 15 December. Following your rule ‘the most recent minutes win over the proposal’, it's 15 December.”
Minutes · 8 October 2026Proposal · 18 September 2026

What you need

The three documents

Download them and upload them in this order, one at a time. For each one you'll say what it is and its date. They're in Spanish, as in the video.

  1. Signed proposal

    Type: ContractDate: 18 September 2026

    The proposal signed with the client: scope and delivery on 30 November 2026.

  2. Follow-up minutes

    Type: Minutes and emailsDate: 8 October 2026

    The follow-up meeting: delivery moves to 15 December 2026.

  3. Tone guide

    Type: Internal policyDate: No date

    How the agency writes to clients: friendly, short sentences, how to sign off.

The project instruction

Create a Claude project (for example “Bodegas Ribera”) and paste this into its instructions. In the video it goes in right before step 7; you can add it now.

Before writing anything on behalf of the agency (emails or messages to clients), check my MaBrain brain “Bodegas Ribera · web”.
If two sources don't match, show me both with their citations.
If the brain has a rule that applies, follow it and mention it in the chat; in the email to the client, don't cite it as a source.
If the brain doesn't know something, don't make it up: log it as an open question.
Express certainty only in words (Verified, Supported, Inferred or Unconfirmed), never in numbers.

Copy each request as is. If Claude asks for confirmation, accept it. The AI won't always use the same words: look at the dates and the citations.

  1. Connect MaBrain to Claude

    In Claude's sidebar, open Customize → Connectors → + Add → Add custom connector (claude.ai/customize/connectors). Enter the name MaBrain and paste this address:

    https://api.mabra.in/mcp

    Press Continue, leave everything as it is and press Add; then press Connect and sign in with your email. The red notice “This connector was suggested by an external link…” is normal if you sign in without loading the page first. Check that it works:

    Which brains do I have in MaBrain?
    What you should seethe list of your brains (empty if it's your first time).
    Not what you see?

    If Claude says it doesn't have MaBrain, open the chat's tools menu and check the connector is on.

  2. Without a brain: the problem

    In a chat outside the project with the connector off, attach only propuesta.pdf:

    Here's the proposal we signed with Bodegas Ribera. Write an email to Javier Ortega confirming the website delivery date.
    What you should seea flawless email saying 30 November. Your AI doesn't know it changed at the meeting.
    Not what you see?

    If the email says 15 December, that chat has MaBrain: open one outside the project with the connector off.

  3. Create the brain

    Inside the project, with the connector on:

    Create a new brain in MaBrain called “Bodegas Ribera · web”. Keep its facts in English.
    What you should seethe brain, empty, in Your brains.
    Not what you see?

    If it asks for confirmation, accept it. If the name gives an error, use “Bodegas Ribera web” and change the name in the project instruction too.

  4. Your three documents, one at a time

    1. Attach propuesta.pdfType: ContractDate: 18 September 2026
    Here's the proposal we signed with Bodegas Ribera on 18 September 2026. Save it to my brain as a contract, with that date. Its link is https://mabra.in/tutorial/ep1/propuesta.pdf
    Wait until it says it's saved (30 seconds to a minute). Then the next one.
    2. Attach acta-08-10.pdfType: Minutes and emailsDate: 8 October 2026
    Here are the minutes of the follow-up meeting with Bodegas Ribera on 8 October 2026. Save them as minutes and emails, with that date. Its link is https://mabra.in/tutorial/ep1/acta-08-10.pdf
    Wait until it says it's saved (30 seconds to a minute). Then the next one.
    3. Attach guia-tono.pdfType: Internal policyDate: No date
    Here's our tone guide for writing to clients. Save it as an internal policy. Its link is https://mabra.in/tutorial/ep1/guia-tono.pdf
    What you should seethe three documents saved, each with its type. The facts come out in English, even though the PDFs are in Spanish. When you save the minutes, your AI may already warn you that they clash with the proposal. In step 5 you'll see both dates, each with its citation.
    Not what you see?

    If it says it's busy or still processing the previous one, wait and send the same message with the same file again.

    If it suggests another type or doesn't keep the date, correct it with the request's words, for example:

    Save them as minutes and emails, dated 8 October 2026.
  5. Ask for the date

    What delivery date do we have with Bodegas Ribera? Check my brain.
    What you should seeboth dates, each with its citation: the proposal says 30 November 2026 and the minutes, 15 December 2026. Your source order puts a contract before minutes, so it gives 30 November. That's exactly what you fix in step 6.
    Not what you see?

    If only one date shows up:

    What do the proposal and the minutes say about the delivery date?
  6. Decide which source wins

    Add this rule to my brain: the most recent minutes win over the proposal.

    It shows you the exact sentence and asks you to confirm it:

    Yes, save it.
    What you should seethe rule saved in Your rules. Your brain hands it to your AI with both sources, and your AI is the one that applies it when it answers.
    Not what you see?

    If it saves it without showing you the sentence, open it in Your rules on mabra.in and check it says the same.

  7. New chat, same request

    With the project instruction in place, open a new chat in the project:

    Write an email to Javier Ortega, from Bodegas Ribera, confirming the website delivery date.
    What you should seebefore the email, “Careful: the proposal says 30 November, but in the 8 October minutes delivery moved to 15 December”, your rule mentioned and the minutes' citation. The email says 15 December, in the agency's tone. The rule isn't in the email.
    Not what you see?

    If it doesn't check the brain, add:

    Check my brain first.

    If the email doesn't follow the guide, add “Use our tone guide.”. If it writes the certainty as numbers, ask for “words only”. If it still says 30 November, check the minutes were saved with their date (step 4) and the rule is in Your rules.

  8. What it doesn't know

    Same chat:

    Has Javier approved the shop screens yet?
    What you should see“I don't know this”, and on mabra.in, Open questions: 1.
    Not what you see?

    If it doesn't log it, or it infers something from the minutes (that Lucía will send them on 22 October):

    If it's not in my brain, log it as an open question.
  9. Now, with your own

    Think of a real client or project: a contract and the emails that came after, a proposal and what was agreed at a meeting.

    Create a brain in MaBrain called “[client or project]”. Here's [document] from [date]: save it with that date. Then tell me three facts in it I should check before writing to the client.

Advanced layer

For developers and for anyone already moving fast. You don't need it to follow the episodes.

All tutorials