MeetGeek MCP server
MeetGeek in any MCP client, through Memtro: MeetGeek does not publish this server. Memtro's MeetGeek connector reads MeetGeek through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
MeetGeek AI meeting notes: recorded meetings with title, time, host and participants, each meeting's AI summary, transcript by speaker, highlights such as action items and next steps, and meeting-level insight scores and themes, plus the teams that share meetings; when you ask, can send the MeetGeek recorder into a live meeting, submit a recording at a URL for analysis, or delete a meeting.
Reads
meetgeek_list_meetingsThe user's recorded meetings, as MeetGeek pages them (order not documented), with start and end; with details true (default) each meeting's title…meetgeek_get_meetingOne meeting's details (title, time, host, participants, language, template) and, with summary true (default), its AI summary and insights text.meetgeek_get_transcriptA meeting's transcript, sentence by sentence with speaker and time, a page at a time.meetgeek_get_highlightsA meeting's highlights as MeetGeek labelled them (tasks, decisions, next steps and so on); type narrows them, e.g. next_steps.meetgeek_get_insightsA meeting's insight scores (engagement, clarity of action items and so on, each with MeetGeek's interpretation), its most discussed themes…meetgeek_list_teamsThe MeetGeek teams the user can share meetings to and the ones whose meetings they can view, with their ids (for meetgeek_list_meetings team_id).
Acts, when you ask
These change something in MeetGeek. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
meetgeek_send_botSends the MeetGeek recorder bot into a live meeting by its join link (Google Meet, Zoom, Teams).meetgeek_upload_recordingAsks MeetGeek to fetch an audio or video file from a public download URL and transcribe and analyse it as a new meeting in the user's account.meetgeek_delete_meetingDeletes a meeting from MeetGeek, with its recording, transcript, summary and highlights, for everyone it was shared with.
Connect it
First connect MeetGeek on Dashboard → Connections, then add Memtro to your client once. The MeetGeek tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared MeetGeek connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › What were the next steps from yesterday's client call?
- › Summarise the product review meeting on Tuesday.
- › What did Dan Fletcher say about pricing in the Northwind call?
- › Which themes came up most in this week's sales calls?
- › Send the recorder into the 3pm Zoom call.
Questions
- Is this an official MeetGeek MCP server?
- No. It is Memtro's MCP server with Memtro's MeetGeek connector behind it: the connector reads MeetGeek through its API with the credentials you connect on Dashboard → Connections, and MeetGeek publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in MeetGeek?
- Only when you ask, and only what it has been granted: send the MeetGeek recorder bot to join a live meeting; submit a recording at a URL for transcription and analysis; delete a meeting and its notes permanently. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.