Merge Unified's Google Meet integration Merge Agent Handler's Google Meet MCP server

Connect your AI Agents to Google Meet in minutes

Merge lets you securely connect your agents to Google Meet and thousands of tools instantly

Start building for free

Read docs

Google Meet

Learn more about Merge Agent Handler

Available tools

list_conference_records

List past Google Meet conferences with filtering and pagination. Returns meeting history including start/end times and associated spaces. Requires admin privileges.

get_conference_record

Get details of a specific Google Meet conference. Returns start/end times, expiration date, and associated space. Use to access participants, recordings, or transcripts.

list_participants

List participants in a Google Meet conference. Returns join/leave times and user identification. Supports filtering and pagination for attendance tracking.

get_participant

Get details of a specific participant. Returns join/leave times and identification (Google account, anonymous, or phone user).

list_participant_sessions

List all connection sessions for a participant. Returns start/end times for each join/leave. Useful for tracking reconnections and total participation time.

get_participant_session

Get details of a specific participant session. Returns exact connect/disconnect timestamps for precise attendance tracking.

list_recordings

List recordings for a Google Meet conference. Returns Google Drive URLs, timestamps, and status. Recordings are automatically saved to Drive.

get_recording

Get details of a specific recording. Returns Google Drive URLs for viewing and downloading, timestamps, and recording status.

create_space

Create a new Google Meet meeting space. Generates a unique meeting URI and code. Configure access: OPEN (public), TRUSTED (organization-only), or RESTRICTED (invite-only).

get_space

Get details of a Google Meet space. Returns meeting URI, code, access settings, and active conference status.

update_space

Update Google Meet space settings. Modify access type (OPEN, TRUSTED, RESTRICTED) or entry point access. Use update_mask to specify fields to update.

end_active_conference

End the active conference in a Google Meet space. Disconnects all participants and finalizes recordings/transcripts. The space remains available for future meetings.

list_transcripts

List transcripts for a Google Meet conference. Returns Google Docs URLs, timestamps, and status. Transcripts are automatically saved to Docs.

get_transcript

Get details of a specific transcript. Returns Google Docs URLs for viewing and downloading, timestamps, and transcription status.

list_transcript_entries

List transcript entries with speaker attribution and timestamps. Each entry contains text, speaker ID, language, and timing. Useful for searching meeting content.

get_transcript_entry

Get details of a specific transcript entry. Returns text, speaker, language, and exact timestamps. Useful for citations and speaker verification.

validate_credential

Validate Google Meet credentials. Verifies credentials during setup.

View all tools by creating a free account See more tools

How to set up Merge Agent Handler

In an mcp.json file, add the configuration below, and restart Cursor.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5      "headers": {
6        "Authorization": "Bearer yMt*****"
7      }
8    }
9  }
10}
11

Copy Code

Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.

Make sure Claude is using the Node v20+.

Learn more in the official documentation ↗

1{
2  "mcpServers": {
3    "agent-handler": {
4      "command": "npx",
5      "args": [
6        "-y",
7        "mcp-remote@latest",
8        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9        "--header",
10        "Authorization: Bearer ${AUTH_TOKEN}"
11      ],
12      "env": {
13        "AUTH_TOKEN": "yMt*****"
14      }
15    }
16  }
17}

Copy Code

Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.

Learn more in the official documentation ↗

1{
2    "mcpServers": {
3      "agent-handler": {
4        "command": "npx",
5        "args": [
6          "-y",
7          "mcp-remote@latest",
8          "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9          "--header",
10          "Authorization: Bearer ${AUTH_TOKEN}"
11        ],
12        "env": {
13          "AUTH_TOKEN": "<ah-production-access-key>"
14        }
15      }
16    }
17  }

Copy Code

In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".

You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.

Learn more in the official documentation ↗

1{
2  "inputs": [
3    {
4      "type": "promptString",
5      "id": "agent-handler-auth",
6      "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7      "password": true
8    }
9  ],
10  "servers": {
11    "agent-handler": {
12      "type": "stdio",
13      "command": "npx",
14      "args": [
15        "-y",
16        "mcp-remote@latest",
17        "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18        "--header",
19        "Authorization: Bearer ${input:agent-handler-auth}"
20      ]
21    }
22  }
23}

Copy Code

FAQs on using Merge's Google Meet MCP server

What is a Google Meet MCP server?

It’s an MCP server that lets your agents access data and functionality from a Google Meet instance via tools. Your agents can invoke these tools to get recordings, add participants to a meeting, review transcripts, and more.

Google doesn’t offer an MCP server purpose built for Google Meet, but you can use one from a third-party platform, like Merge Agent Handler.

How can I use a Google Meet MCP server?

Here are just a few use cases (these use cases can also apply to other video conferencing MCP servers):

Meeting lifecycle automation: Your agent can create and manage Google Meet links as part of a broader scheduling workflow. For example, when a deal hits “Technical deep dive,” your agent can generate a meeting link, attach it to the calendar invite, and post it to the deal channel

Meeting prep and attendee context: Your agent can pull relevant context (e.g., docs) and generate a pre-read tailored to the meeting type and attendees. For example, before a customer QBR, your agent can compile last quarter’s goals, open issues, and renewal timeline into a one-page brief

Cross-team visibility and knowledge capture: Your agent can publish summaries and decisions to the right places so people who didn’t attend stay aligned. For example, after a product feedback call, your agent can post the top requests and verbatim quotes to the product feedback hub and link them to the relevant initiative

Operational analytics and trends: Your agent can analyze patterns across meetings to surface recurring blockers, themes, and follow-through. For example, across sales calls, your agent can summarize top objections and quantify which ones correlate with stalled opportunities

What makes Merge Agent Handler’s Google Meet MCP server better than alternative Google Meet MCP servers?

Merge Agent Handler provides several platform-level advantages:

End-to-end authentication management: Merge handles credential collection, token management, and re-authentication flows through a built-in Link UI, reducing implementation overhead

Enterprise-grade security with DLP: All tool inputs and outputs are scanned for sensitive data, with configurable rules to block, redact, or flag risky interactions

Real-time observability and audit logs: Every tool call is logged and fully searchable, enabling debugging, compliance audits, and performance monitoring across agent workflows

Connector Studio for extensibility: Developers can modify existing connectors or create custom tools, ensuring flexibility beyond prebuilt integrations

Evaluation Suite for pre-production testing: Tool behavior can be validated against expected outcomes before deployment, improving reliability and success rates

Can I set custom security rules for Google Meet tool calls in Merge Agent Handler?

Yes. Merge Agent Handler includes a Security Gateway with data loss prevention (DLP) that allows you to set a wide range of custom security rules. Here are a few examples:

Control who can join: Block or require approval if a Meet invite includes external domains (or isn’t on an allowlist like @customer.com). For example, prevent adding @gmail.com guests to customer calls

Restrict recording and transcripts: Block enabling recording / transcription / meeting notes capture unless the meeting is tagged “Customer-approved” (or attendees have consented). For example, allow recording for internal training, block for sensitive support escalations

Prevent link sharing outside approved channels: Detect Meet links being posted to public Slack channels / external email and redact or replace with an access request flow. For example, only allow sharing Meet links in a deal’s private channel

Participant identity checks: Require that all attendees are authenticated (signed in) and block “anyone with the link” style access. For example, prevent anonymous joins on customer roadmap reviews

Limit what meeting content can be exported: If meeting summaries/transcripts are generated, redact PII/secrets (emails, phone numbers, API keys) before writing to systems

How can I start using Merge Agent Handler’s Google Meet MCP server?

You can follow these steps:

1. Sign up for Merge Agent Handler.

2. Connect the Google Workspace account the agent will use and ensure it has the required permissions for your intended actions.

3. Add the Google Meet MCP server to your MCP client/runtime (e.g., Claude Desktop, Cursor, or your Agent Handler setup) and verify auth and tool availability

4. Implement one narrow workflow first (e.g., create a Meet link when a meeting is scheduled and write it back to the invite/CRM/Slack/Notion).

5. Configure Security Gateway guardrails before wider use (e.g., external attendee allowlists, recording/transcription approval, and safe link-sharing rules).

6. Test end-to-end in a sandbox with both normal and “rule-triggering” scenarios, then iterate.

7. Roll out gradually, monitor logs/policy events, and tighten rules as you scale.