Connect your AI Agents to Google Meet in minutes
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.
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}
11Open 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}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 }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}FAQs on using Merge's Google Meet MCP server
FAQs on using Merge's Google Meet MCP server
Ready to try it out?
Whether you're an engineer experimenting with agents or a product manager looking to add tools, you can get started for free now
