Resources · Claude connector

Claude MeetGeek connectorWhat Claude can do in your MeetGeek account.

The Claude MeetGeek connector exposes 8 tools. 6 read your recorded meetings, 1 imports a recording, 1 is documented by no source at all. Below: what Claude pulls up, what it adds to your account, and what you need set up first.

Open the MeetGeek connector sheetSee the 8 tools

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What it changes once the call ends

Instead of replaying a recording or scrolling through a transcript, you ask Claude what was agreed or who said what, and it fetches the answer from your MeetGeek account while it replies. The connector reaches your meetings, their transcripts, highlights and summaries, and can import a recording you hold a download link for.

Find a decision without rewatching. meetings lists your calls, then transcript returns the full text with speaker names and timestamps, which is where to look for the moment the budget got signed off.

Start the recap from MeetGeek's own material. summary brings back MeetGeek's summary and action items, and highlights the key moments its AI flagged.

A team's month at a glance. teamMeetings lists the meetings of a given team, with filters, and meetingDetails opens the one you need.

Bring an outside meeting in. You have the file from a call MeetGeek never joined: uploadRecording imports it into MeetGeek from a download URL.

What Claude will not do: anything on its own. No recap goes out when a meeting ends, and no tool wakes up when a recording arrives. The eighth tool, insights, is described nowhere, so this page assigns it no capability. For a recap pushed after every call, you want an automation tool, a different job; the Integrations hub covers that side.

Vocabulary

The vocabulary in one minute

Five terms to know before you add MeetGeek to Claude.

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
Tool
One named capability the connector opens to Claude. Claude picks the ones it needs; the directory sheet lists all of them.
Authorization
The step where you hand Claude the access it will use on your account. Granted once per person, and withdrawn the same way.
Approval
The confirmation Claude waits for in the chat before carrying out something that changes your account.
MCP
The shared standard behind connectors; it is what lets an assistant like Claude talk to an outside service.
Connect

Connect MeetGeek to Claude in three steps

  1. 01

    Find MeetGeek

    In Claude Desktop, open Customize, then Connectors, and locate MeetGeek. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it first so each member can connect.

  2. 02

    Start the connection

    Start the installation from its row. Per MeetGeek's official repository, the connector needs an API key from your MeetGeek account settings; enter it when the extension asks. The exact screens depend on Claude Desktop, so follow what it shows. If the link ever breaks, use Disconnect and add it back.

  3. 03

    Check the access you grant

    Check what you hand over before confirming: the API key you enter, not Claude, decides what the connector can reach in MeetGeek. MeetGeek's repository adds that the server runs locally with Node.js, on your own machine.

Tools

All 8 tools, grouped by what they do

MeetGeek gives Claude 8 tools: 6 that read your account, 1 that change something in it, and 1 no official source describes.

Three groups: what Claude reads, what it adds, and what no source describes. Tool names stay exactly as Claude shows them.

  • 6 read
  • 1 write
  • 1 not documented

What Claude reads (6)

6 tools

Six tools that look at your meetings without changing them.

meetings

Lists all your MeetGeek meetings, with pagination as an option.

When it helps
you want to know which calls happened with a given client since September.
Watch out
it lists meetings only; the transcript, highlights or summary of one each come from their own tool.

Sourcegithub.com · October 1, 2026 ↗

meetingDetails

Gets the detailed information on one specific meeting.

When it helps
two meetings share nearly the same title and you need the right one.
Watch out
the details are not the full text of the meeting; that comes from transcript.

Sourcegithub.com · October 1, 2026 ↗

transcript

Retrieves a meeting's complete transcript, with speaker identification and timestamps.

When it helps
your manager disputes a commitment and you want the exact words from the meeting.
Watch out
it only reaches meetings that the account behind your API key can see.

Sourcegithub.com · October 1, 2026 ↗

highlights

Brings back the key moments and standout points that MeetGeek's AI picked out.

When it helps
you missed the team retro and want its three main points before the next one.
Watch out
these are the moments MeetGeek's AI picked, not a full record; the exact wording sits in transcript.

Sourcegithub.com · October 1, 2026 ↗

summary

Provides MeetGeek's generated summary along with the action items that came out of the meeting.

When it helps
the recap of a client workshop is due tonight and you are starting from nothing.
Watch out
the summary and action items are generated by MeetGeek; check the transcript before quoting a commitment.

Sourcegithub.com · October 1, 2026 ↗

teamMeetings

Lists the meetings tied to a given team, with filtering options.

When it helps
the sales lead wants to see her team's client calls over the month.
Watch out
a team's meetings come back only if the account behind your API key has access to them.

Sourcegithub.com · October 1, 2026 ↗

What Claude adds (1)

1 tool

One tool that brings a recording into your account. No source describes its confirmation, so the general rule below applies.

uploadRecording

Approval: see the rule

Brings a meeting recording into MeetGeek from a download URL.

What Claude asks for
no source describes a confirmation specific to this tool; the general approval rule applies.
When it helps
a call ran on a platform MeetGeek did not record, and you have the file.

Sourcegithub.com · October 1, 2026 ↗

Undocumented (1)

1 tool

The directory publishes this name and nothing else. No official text says what it does, and we will not guess from a name.

insights

This name appears on the directory sheet, and that is all anyone knows about it. Neither MeetGeek's repository nor any Claude page describes it, so this page says nothing further.

Watch out
whatever it actually does, the general approval rule covers it.
Approvals

What Claude checks with you first

By default, Claude pauses and asks for your go-ahead before each action it takes on an account for you. The request appears in the chat, right when it matters.

For MeetGeek, no source describes a confirmation tied to a specific tool, so that default rule covers importing a recording and the undocumented tool too. On Team and Enterprise workspaces, owners decide whether members may let certain actions through without being asked every time, and they can cap a connector for the whole organisation, keeping reads and shutting writes. Claude also goes through your own key and never holds more rights than you.

Plans

Which plans it's available on

None of the 819 sheets in the official directory shows plan availability. Connector by connector, that information is not published anywhere.

The general rule is sourced: desktop extensions such as this one install on Claude Desktop, while remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables a connector before members connect. For the current status, the connector's sheet in the official directory is the reference.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: no recap goes out by itself when a meeting wraps up.

Only the publisher documents this connector, through its public repository; neither Claude's help centre nor Anthropic's docs have a page on it. The directory badge is not a security audit, and Anthropic says so on every sheet: it does not choose a publisher's tools and does not vouch for how they behave. Connect what comes from a publisher you know. This one is a desktop extension: the repository says the server runs locally with Node.js, so it lives on your machine. And the sheet's tool list is an observed floor, not a guarantee of what an administrator may open.

Need help

Need help connecting MeetGeek to Claude?

A person reads every message.

FAQ

Claude MeetGeek connector FAQ

01What can Claude do with the MeetGeek connector?
Claude can go back through your MeetGeek meetings from the chat and pull out what you need. Six tools list your meetings and a team's meetings, open one meeting's details, and return its transcript with speakers and timestamps, its highlights, and its summary with action items. A seventh imports a recording from a URL. The eighth, insights, sits on the sheet with no official description, so this page credits it with nothing.
02Can Claude change anything in MeetGeek?
Only one documented tool adds something to your account: it imports a meeting recording from a download URL. The six other described tools only read. The eighth has no source describing it, so nobody can say whether it reads or changes anything. No delete tool appears on the directory sheet, and the import works from a download URL, per MeetGeek's repository. What the sheet shows is an observed floor, though, since an admin can always open further actions.
03Does Claude ask before importing a recording?
By default, yes: Claude asks for confirmation before every action it takes on an account on your behalf. No source describes a confirmation specific to the recording import or to the undocumented tool, so that general rule covers both. On Team and Enterprise workspaces, owners decide whether members can let certain actions through without a prompt, and they can also shut off writes for the whole organisation, with no way for a member to undo that from their own account.
04Which plans is the MeetGeek connector available on?
No official source publishes plan availability for an individual connector, and no directory sheet displays it. Anthropic's general rule says desktop extensions, the family this one belongs to, install on Claude Desktop, and that on Team and Enterprise an Owner or Primary Owner must enable a connector before members can use it. On MeetGeek's side you need an API key. For the current status, check the connector's sheet in the official directory.
05Does Claude see every meeting in my company?
Claude goes through the API key you generated in your MeetGeek account, so it only reaches what that key opens. Meetings belonging to a whole department only come back if your own access covers them. Claude works with the rights of whoever connected it and nothing beyond: what you cannot see in MeetGeek stays out of its view too. On Team and Enterprise, an owner can further restrict what the connector may do for everyone.
06Why isn't the MeetGeek connector responding?
MeetGeek's official repository names three things to check. The API key: the connector needs one generated in your MeetGeek account settings. The setup: the server runs locally with Node.js, as a desktop extension in Claude Desktop rather than a remote connector. And the restart: after any change to the server's code or configuration, the MCP client has to be restarted for the change to take effect, which here means Claude Desktop. The repository gives no other troubleshooting step.
07Claude or an automation tool for MeetGeek?
They do different jobs. Claude helps when you have a question about a past meeting: a decision to find, an exact quote, a summary to rework, an outside recording to bring in. It acts inside the conversation and only when you ask. An automation tool helps when something should happen without you, such as pushing every summary into your CRM after each call. Choose by use case; one does not replace the other.
Same platform

Other docs you might need on this stack.

Browse all integrations