Use Claude with your meeting notes

Seven prompts for Claude

These are the same seven prompts as on our ChatGPT page, with one change: the transcript goes inside <transcript> tags. Anthropic recommends XML tags to keep instructions and pasted material apart (Claude docs: use XML tags). Paste the transcript where it says so.

1. Minutes

The meeting transcript is in <transcript> tags. Each line has the speaker's name.
Write the minutes in English with three sections: Decisions, Action items (task, owner, due date), Open questions.
Only use what is in the transcript. If an owner or date is not said, write "not said".
Keep each line under 20 words.

<transcript>
PASTE THE TRANSCRIPT HERE
</transcript>

2. Action items only

From the transcript in <transcript> tags, list every task someone agreed to do.
Format each line as: owner | task | due date | the exact quote where they agreed.
Leave out ideas nobody took.

<transcript>
PASTE THE TRANSCRIPT HERE
</transcript>

3. Follow-up email

Using only the transcript in <transcript> tags, write a short follow-up email to the participants.
Thank them in one line, list decisions and next steps with owners, and ask one open question.
Under 150 words. Plain, friendly tone. Put the email inside <email> tags.

<transcript>
PASTE THE TRANSCRIPT HERE
</transcript>

4. What did I miss?

I joined this meeting at 10:20. The transcript is in <transcript> tags.
Summarize what happened before 10:20 in 5 bullets, and tell me if anything was asked of me.

<transcript>
PASTE THE TRANSCRIPT HERE
</transcript>

5. Minutes in another language

The meeting in <transcript> tags was in Spanish. Write the minutes in English.
Keep names and numbers exactly as said. For each decision, add the original Spanish quote.

<transcript>
PASTE THE TRANSCRIPT HERE
</transcript>

6. Disagreements

In the transcript in <transcript> tags, find the points where people disagreed.
For each one: who held which view, and was it resolved?

<transcript>
PASTE THE TRANSCRIPT HERE
</transcript>

7. Ask one question

Answer only from the transcript in <transcript> tags: what did we decide about the price?
Quote the lines you used. If the transcript does not say, answer "not in the transcript".

<transcript>
PASTE THE TRANSCRIPT HERE
</transcript>

Each prompt says to use only what is in the transcript. Keep that line, and keep the quotes: they are how you check the answer.

Where the transcript comes from

Prompts do nothing without a good transcript, and “good” means a name on every line. The built-in transcripts of Teams, Zoom and Google Meet belong to the organizer: someone has to turn them on, and often only the organizer can download the file. If you were a guest, you may not get one at all.

Trippi Notes writes your own transcript from the meeting tab, with names and times, and has a button that opens the meeting in Claude. For one meeting, that is the fastest way. For many meetings, connect the journal.

Connect your meeting journal to Claude

Trippi Notes has an MCP server for your meeting journal. MCP is the standard way for an assistant like Claude to use outside tools. Once it is connected, Claude can search your meetings, read their summaries and transcripts, and keep your task list, when you ask it to.

1. 1Sign in and open your journal. MCP reads the meetings in your Trippi Notes journal on our server, so you need to be signed in to your Trippi account and have meetings in the journal.
2. 2Create a key. In the journal, open the Tasks view and find the block “Your journal in Claude, ChatGPT and Cursor (MCP)”. Type what the key is for, such as Claude, and press Create a key.
3. 3Copy the address right away. The journal shows the key once, inside a ready address for Claude and a ready command for Claude Code. Copy it now; it is not shown again.
4. 4Add it to Claude. In Claude, open Customize → Connectors, choose Add custom connector, paste the address and press Add.
5. 5Turn it on in a chat. In a chat, press + at the bottom left, open Connectors and switch Trippi Notes on. Then ask about your meetings.

Custom connectors work on Claude’s Free, Pro, Max, Team and Enterprise plans; on Free you can add one. On Team and Enterprise, an owner adds the connector under Organization settings → Connectors first, and then each person connects it (Claude help: custom connectors).

Claude Code

The same block in the journal shows a ready command for Claude Code. It has this shape, with your own key in place of the placeholder (Claude Code docs: MCP):

claude mcp add --transport http trippi-notes https://api.gettrippi.app/api/mcp/notes --header "Authorization: Bearer YOUR_KEY"

Other MCP clients that accept a remote server by address can use the same address. In ChatGPT, custom MCP connections depend on your plan and on developer mode (OpenAI help).

What Claude can do with it

The server gives Claude five tools. These are their exact names, so you can recognize them when Claude asks to use one:

• search_meetings — finds meetings by words said, title, summary or tasks. With no words, it returns the latest meetings.
• get_meeting — reads one meeting: participants, summary, decisions, open questions, tasks with owners and due dates, your own notes, and, when asked, the transcript. A long transcript comes back cut to its first 600 lines.
• list_tasks — open tasks from every meeting: all, only yours, the ones you gave to others, or overdue.
• update_task — changes a task’s status (open, in progress, done), owner or due date.
• add_task — adds an open task to a meeting.

So you can ask things like “What did we promise the client in September?”, “Which of my tasks are overdue?”, or “Mark the pricing task from Tuesday’s call as done.” Claude picks the tools; you see which ones it used.

Keep the key safe

• The key opens your whole journal and lets the holder change your tasks. Do not share it, and do not paste the address into documents or chats.
• Make one key per assistant. You can have up to ten, and each shows when it was last used.
• To cut access, press Revoke next to the key in the same journal block. The assistant stops working with your journal at once.
• We keep only a fingerprint of each key and when it was last used. Details are in our privacy policy.