Agent skill
google-meet
Google Meet API integration with managed OAuth. Create meeting spaces, list conference records, and manage meeting participants. Use this skill when users want to interact with Google Meet.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/google-meet
Metadata
Additional technical details for this skill
- author
- maton
- version
- 1.0
SKILL.md
Google Meet
Access the Google Meet API with managed OAuth authentication. Create and manage meeting spaces, list conference records, and retrieve participant information.
Quick Start
# Create a meeting space
curl -s -X POST 'https://gateway.maton.ai/google-meet/v2/spaces' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-d '{}'
Base URL
https://gateway.maton.ai/google-meet/{native-api-path}
Replace {native-api-path} with the actual Google Meet API endpoint path. The gateway proxies requests to meet.googleapis.com and automatically injects your OAuth token.
Authentication
All requests require the Maton API key in the Authorization header:
Authorization: Bearer YOUR_API_KEY
Environment Variable: Set your API key as MATON_API_KEY:
export MATON_API_KEY="YOUR_API_KEY"
Getting Your API Key
- Sign in or create an account at maton.ai
- Go to maton.ai/settings
- Copy your API key
Connection Management
Manage your Google OAuth connections at https://ctrl.maton.ai.
List Connections
curl -s -X GET 'https://ctrl.maton.ai/connections?app=google-meet&status=ACTIVE' \
-H 'Authorization: Bearer YOUR_API_KEY'
Create Connection
curl -s -X POST 'https://ctrl.maton.ai/connections' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-d '{"app": "google-meet"}'
Get Connection
curl -s -X GET 'https://ctrl.maton.ai/connections/{connection_id}' \
-H 'Authorization: Bearer YOUR_API_KEY'
Response:
{
"connection": {
"connection_id": "21fd90f9-5935-43cd-b6c8-bde9d915ca80",
"status": "ACTIVE",
"creation_time": "2025-12-08T07:20:53.488460Z",
"last_updated_time": "2026-01-31T20:03:32.593153Z",
"url": "https://connect.maton.ai/?session_token=...",
"app": "google-meet",
"metadata": {}
}
}
Open the returned url in a browser to complete OAuth authorization.
Delete Connection
curl -s -X DELETE 'https://ctrl.maton.ai/connections/{connection_id}' \
-H 'Authorization: Bearer YOUR_API_KEY'
Specifying Connection
If you have multiple Google Meet connections, specify which one to use with the Maton-Connection header:
curl -s -X POST 'https://gateway.maton.ai/google-meet/v2/spaces' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Maton-Connection: 21fd90f9-5935-43cd-b6c8-bde9d915ca80' \
-d '{}'
If omitted, the gateway uses the default (oldest) active connection.
API Reference
Spaces
Create Space
POST /google-meet/v2/spaces
Content-Type: application/json
{}
Response:
{
"name": "spaces/abc123",
"meetingUri": "https://meet.google.com/abc-defg-hij",
"meetingCode": "abc-defg-hij",
"config": {
"accessType": "OPEN",
"entryPointAccess": "ALL"
}
}
Get Space
GET /google-meet/v2/spaces/{spaceId}
Update Space
PATCH /google-meet/v2/spaces/{spaceId}
Content-Type: application/json
{
"config": {
"accessType": "TRUSTED"
}
}
End Active Call
POST /google-meet/v2/spaces/{spaceId}:endActiveConference
Conference Records
List Conference Records
GET /google-meet/v2/conferenceRecords
With filter:
GET /google-meet/v2/conferenceRecords?filter=space.name="spaces/abc123"
Get Conference Record
GET /google-meet/v2/conferenceRecords/{conferenceRecordId}
Participants
List Participants
GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/participants
Get Participant
GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/participants/{participantId}
Participant Sessions
List Participant Sessions
GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/participants/{participantId}/participantSessions
Recordings
List Recordings
GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/recordings
Get Recording
GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/recordings/{recordingId}
Transcripts
List Transcripts
GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/transcripts
Get Transcript
GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/transcripts/{transcriptId}
List Transcript Entries
GET /google-meet/v2/conferenceRecords/{conferenceRecordId}/transcripts/{transcriptId}/entries
Code Examples
JavaScript
// Create a meeting space
const response = await fetch(
'https://gateway.maton.ai/google-meet/v2/spaces',
{
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Authorization': `Bearer ${process.env.MATON_API_KEY}`
},
body: JSON.stringify({})
}
);
const space = await response.json();
console.log(`Meeting URL: ${space.meetingUri}`);
Python
import os
import requests
headers = {
'Content-Type': 'application/json',
'Authorization': f'Bearer {os.environ["MATON_API_KEY"]}'
}
# Create a meeting space
response = requests.post(
'https://gateway.maton.ai/google-meet/v2/spaces',
headers=headers,
json={}
)
space = response.json()
print(f"Meeting URL: {space['meetingUri']}")
Notes
- Spaces are persistent meeting rooms that can be reused
- Conference records are created when a meeting starts and track meeting history
- Access types:
OPEN(anyone with link),TRUSTED(organization members only),RESTRICTED(invited only) - Recordings and transcripts require Google Workspace with recording enabled
Error Handling
| Status | Meaning |
|---|---|
| 400 | Missing Google Meet connection |
| 401 | Invalid or missing Maton API key |
| 429 | Rate limited (10 req/sec per account) |
| 4xx/5xx | Passthrough error from Google Meet API |
Resources
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?