A new MCP server lets Claude Desktop, Claude Code, and Cursor drive Groupthink on your behalf, so the time you already spend on calls and in conversations does more work.
If you spend your day in meetings, the bottleneck on getting value out of them usually isn’t the meeting itself. It’s everything around it. Reading the prep doc. Remembering what the person said last time. Catching up on the call you missed. Pulling action items out of a transcript before they go stale.
Today, that handoff lives in an MCP server that connects Groupthink to whichever AI assistant you already use. Set it up in Claude Desktop, Claude Code, or Cursor. Once it’s connected, your assistant can drive Groupthink directly. You ask, in plain language, and the right thing happens.
You probably already use your AI assistant for drafting and thinking out loud. The MCP server gives it a new kind of context: your actual relationships, your real meetings, your transcripts. So it can answer questions like:
And on the live side, it can act on your behalf:
Live meeting participation. Your assistant can send the Groupthink bot into a Zoom, Google Meet, or Microsoft Teams call. While it’s there, your assistant can read the running transcript, post chat messages, have the bot speak text out loud, save notes back to Groupthink, and pull the bot out when you’re done.
Relationship intelligence. Your assistant can list your relationships, look up a specific person, search your contacts, surface who you’re falling behind on, and pull the next meeting’s attendee context. The same intelligence you see inside the Groupthink app, available wherever you talk to your assistant.
The full tool list with example prompts is in the MCP Server docs.
You’ll need an MCP-compatible AI client. We’ve tested with Claude Desktop, Claude Code, and Cursor; other clients that support remote MCP over HTTP also work.
Open a new conversation in your assistant and ask it something. The first time it calls a Groupthink tool, you’ll know it worked.