Ask Claude and ChatGPT about your meetings with qatip MCP

qatip MCP connects your meetings to Claude, ChatGPT or any other AI assistant that supports MCP. Once it’s connected, you can ask your assistant something like “What did we promise the client last week?” and it answers from your qatip reports and transcripts, naming the meeting each answer came from. It’s a Pro feature and reads only your own meetings.

What is MCP?

MCP stands for Model Context Protocol. It’s an open-source standard for connecting AI applications to outside systems. The project’s site, modelcontextprotocol.io, compares it to a USB-C port: any device can plug into any charger with the same cable, and any assistant that supports MCP can connect to any tool that has an MCP server in the same way.

On their own, Claude and ChatGPT have no idea what was said in your meetings. With qatip MCP connected, the assistant goes to qatip when you ask a question, finds the relevant meetings, reads them, and bases its answer on what’s there. You stop copying meeting notes into the chat by hand. Claude and ChatGPT aren’t the only tools that speak MCP, either. Developer tools like Cursor, Codex and Claude Code can use the same connection, so you can ask the assistant you code with what was said about a feature in yesterday’s planning meeting.

What can the assistant look at through qatip MCP?

The assistant can read your qatip meetings in these ways:

• List your recent meetings by date.
• Search for something that was said in your meetings.
• Open a meeting’s report: summary, decisions, to-dos, open questions.
• Read the transcript and see who said what, line by line.
• Pull up to-dos from all your meetings, or only the open ones.
• List the people in your meetings.

All of it is read-only. The assistant can’t edit a meeting, delete one, or send anything on your behalf.

What can you ask your assistant?

It works best for questions where you remember what was discussed but not which meeting it was in. A few examples:

Decisions and commitments

• “What did we decide about pricing this month?”
• “What did I promise each client in last week’s calls?”
• “Who last moved the release date, and in which meeting?”

Open work

• “List the to-dos still open on me, sorted by due date.”
• “Does Elif have any overdue tasks from our meetings?”
• “Did anything from this week’s meetings end up without an owner?”

Prep and writing

• “I’m meeting the same team tomorrow. Give me a short recap of our last three meetings.”
• “Pull together the objections customers raised in my last two sales calls.”
• “Draft a short email to the team with the decisions from Monday’s meeting.”

That last kind of question is where this gets useful. Your assistant brings its own skills, and qatip brings what was said. qatip’s built-in Ask feature already answers questions across your meetings and shows the moment each answer came from. Drafting a document, or mixing meeting details into some other piece of work, is easier on the assistant’s side.

How do you get better answers?

The assistant bases its answer on what it finds in your meetings, so the better you describe what you want, the more likely it lands on the right one. A few habits help:

1. Give a time frame. Say “this month” or “last week” instead of “recently”, and the assistant narrows its search.
2. Name the person or the company. Ask “What did we discuss with Elif and the procurement team?” rather than “What did we discuss with the client?”
3. Ask for the source. Add “which meeting, and who said it?” and the assistant names the meeting and the speaker, so you can check the transcript if it matters.
4. For an important decision, ask it to read the transcript. The report summary is short, and the exact words live in the transcript.
5. Keep going in the same chat. The assistant remembers its last answer, so a follow-up like “which of these are still open?” narrows the list.

One more thing. When an assistant can’t find something, it sometimes fills the gap with a guess. If an answer doesn’t name a meeting, or the date looks off, ask for the source again.

How do you connect qatip MCP?

You set it up once. With most assistants you don’t paste a key: you sign in with your qatip account and allow access.

Claude (Claude.ai and Claude Desktop)

1. In qatip, open Settings, go to AI assistants and copy the connection address: https://qatip.app/mcp
2. In Claude, open Settings › Connectors › Add custom connector and paste the address.
3. qatip opens in your browser. Sign in, and on the screen that shows what the assistant can read, allow it.
4. Go back to Claude and ask your first question about your meetings.

ChatGPT

1. In ChatGPT, turn on developer mode and create a new connector.
2. Enter https://qatip.app/mcp as its address.
3. Sign in to qatip on the page that opens and allow access.

Claude Code, Cursor, Codex and others

Developer tools connect with a single command. In Claude Code, for example:

claude mcp add --transport http qatip https://qatip.app/mcp

In Codex, codex mcp add qatip --url https://qatip.app/mcp does the same. qatip’s settings screen gives you the exact line to paste for each assistant. If your tool doesn’t support signing in, you can create a personal key on the same screen instead. Only give that key to apps you trust.

Which plan includes qatip MCP?

qatip MCP is a Pro feature and isn’t on the free plan. Pro is $14.99 a month or $119.99 a year, starts with a 7-day free trial, and you can cancel any time. Pro also gives you unlimited questions, a live transcript while people talk, and integrations like Notion, Slack and Linear. The details are on the pricing page. On the free plan, the AI assistants section in Settings tells you the connection is part of Pro, and once you upgrade you connect from the same place.

Privacy: what does the assistant see?

The assistant can only read meetings in the qatip account it’s connected to, which means yours. It can’t reach anyone else’s meetings through this connection. When you connect, the permission screen shows what it can read, and when you remove it in Settings, access stops at that moment.

Keep one thing in mind. When the assistant reads a meeting, that content becomes part of your conversation with the assistant. How that conversation is stored and used is governed by the rules of Claude, ChatGPT or whichever assistant you use. If your company has a policy on AI assistants, check it first.

Nothing changes on qatip’s side. Your meetings are stored in the EU, in Frankfurt, they’re never used to train AI models, and you choose how long the audio is kept.

If you’re thinking about connecting your meetings to an assistant, the qatip MCP page walks through how it works.