create_meeting_spaceLABSCO SUMMARY
Meeting bookkeeping rather than meeting content — it answers who was in the room, not what was said.
The scheduling half is thin on purpose: open a space, change its access setting, end it. The attendance half is where it earns a place — conference records break down to individual participants and then to each continuous join-and-leave interval, which is what you need to reconstruct a meeting after the fact. The tool list stops there; nothing in it reaches transcripts, recordings or chat.
What it is
A hosted MCP server over the Google Meet API. One half creates, updates and ends meeting spaces; the other half reads the conference records those meetings leave behind, down to each participant and each stretch of time they were connected.
What you get
- Create a meeting space and get its join link back
- Read a space's current details, including its access setting
- Change a space's configuration — for instance who is allowed to join
- End an active space, which disconnects everyone in it
- List past conference records for the connected account, or fetch one by name
- List the participants on a conference record, or read one participant's details
- Read each continuous join-and-leave interval a participant had, singly or as a list
- Page through and filter record and participant lists using the Meet API's own filter expressions
Requirements
Reached as a hosted endpoint on MewCP rather than started on your machine. You connect a Google account over OAuth in the MewCP dashboard, and that credential has to carry the Meet permissions for whatever the agent calls. Usage draws on the credits in the account.
Setup effort
Add the hosted endpoint plus a key — paste it into your client, then supply credentials
USE CASES
01
Starting a meeting from inside a conversation
Create a space and hand back the join link, then read the space again to confirm its access setting before you send it out.
02
Answering who actually attended
Find the conference record for the meeting, then list the participants it recorded.
03
Checking how long someone stayed
Read one participant, then walk their sessions — each one is a single continuous stretch of being connected.
04
Closing a room that was left open
Read the space to confirm it is the right one, then end it and disconnect whoever is still in it.
05
Tightening who can join a space you already created
Patch the space's access configuration without recreating it or reissuing the link.
10 tools
Listed in project docs. Your client may show a different list.
get_meeting_spaceend_meeting_spaceupdate_meeting_spaceget_conference_recordlist_conference_recordsget_participantlist_participantsget_participant_sessionlist_participant_sessionsBEFORE YOU INSTALL
What to know first
Tools you get
10 tools named in the project's documentation.
Requires
- A MewCP account and its API key (MEWCP_KEY, dashboard → Developer) — the Hobby tier is free (unlimited servers, 20K actions/month)
- The Google Meet server enabled in your MewCP toolset — the gateway only reaches servers you have enabled
Where it runs
All 3 documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
Server setup
ENDPOINT URL
https://gateway.mewcp.com/personal/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
VS Code
VS CODE · JSON
{
"servers": {
"mewcp": {
"type": "http",
"url": "https://gateway.mewcp.com/personal/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MEWCP_KEY>"
}
}
}
}Cursor
CURSOR · JSON
{
"mcpServers": {
"mewcp": {
"url": "https://gateway.mewcp.com/personal/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MEWCP_KEY>"
}
}
}
}Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mewcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://gateway.mewcp.com/personal/mcp",
"--transport",
"http-only",
"--header",
"Authorization: Bearer <YOUR_MEWCP_KEY>"
]
}
}
}
