KosmoKrator

productivity

Google Meet MCP Gateway for AI Agents

Expose Google Meet tools to Claude Code, Cursor, Codex, and other MCP clients through the local KosmoKrator MCP gateway.

Google Meet MCP Gateway

Expose Google Meet to MCP clients with `kosmokrator mcp:serve --integration=google-meet`.

If the client has never used KosmoKrator before, install it first, then register this integration as a stdio MCP server.

Install KosmoKrator 
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash
Install gateway entry 
kosmokrator mcp:gateway:install --integration=google-meet --write=deny --json
MCP configuration 
{
  "mcpServers": {
    "kosmokrator-google-meet": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=google-meet",
        "--write=deny"
      ]
    }
  }
}
Serve manually 
kosmokrator mcp:serve --integration=google-meet --write=deny

Client Notes

Use one scoped MCP gateway entry, then adapt the config location to the client or framework.

Claude Code Connect local KosmoKrator integrations to Claude Code through one scoped MCP gateway entry. Claude Code can launch the local kosmo binary directly from the project MCP config.
Cursor Expose selected local integrations to Cursor through KosmoKrator without configuring each service as its own MCP server. Use the same KosmoKrator install and integration credentials that power terminal and headless runs.
Codex Use KosmoKrator as a local MCP proxy for Codex so coding sessions can reach selected integrations with explicit write policy. Keep write access denied or ask-based unless the workspace is trusted.
OpenAI Agents SDK Attach KosmoKrator integration tools to OpenAI Agents SDK workflows through a local MCP gateway. Use headless JSON commands for CI-style execution and MCP for agent tool discovery.
Claude Agent SDK Give Claude Agent SDK workflows access to KosmoKrator integrations through a local MCP server. Use a narrow integration list so the agent does not load unrelated tools.
Vercel AI SDK Use KosmoKrator as a local integration gateway for Vercel AI SDK agents and scripts. Prefer CLI JSON calls when a workflow only needs one deterministic integration operation.
LangChain Bridge LangChain agents to local KosmoKrator integration tools through MCP or headless CLI calls. Keep the gateway scoped to the integration and operation class needed by the chain.
LangGraph Run KosmoKrator integration calls from LangGraph nodes while preserving local credentials and permissions. Headless CLI calls fit repeatable graph edges; MCP fits exploratory agent nodes.
CrewAI Expose KosmoKrator integrations to CrewAI workers as scoped local tools. Use per-worker integration scopes to avoid giving every worker every tool.
Generic MCP Clients Connect any stdio-compatible MCP client to local KosmoKrator integration tools. Start with read-only write policy and expand only for trusted projects.

MCP Tool Names

KosmoKrator exposes integration tools through the gateway with stable names.

MCP toolSource functionType
integration__google_meet__google_meet_spaces_create google-meet.google_meet_spaces_create Write write
integration__google_meet__google_meet_spaces_get google-meet.google_meet_spaces_get Read read
integration__google_meet__google_meet_spaces_end_active_conference google-meet.google_meet_spaces_end_active_conference Write write
integration__google_meet__google_meet_spaces_patch google-meet.google_meet_spaces_patch Write write
integration__google_meet__google_meet_conference_records_list google-meet.google_meet_conference_records_list Read read
integration__google_meet__google_meet_conference_records_get google-meet.google_meet_conference_records_get Read read
integration__google_meet__google_meet_conference_records_recordings_list google-meet.google_meet_conference_records_recordings_list Read read
integration__google_meet__google_meet_conference_records_recordings_get google-meet.google_meet_conference_records_recordings_get Read read
integration__google_meet__google_meet_conference_records_participants_get google-meet.google_meet_conference_records_participants_get Read read
integration__google_meet__google_meet_conference_records_participants_list google-meet.google_meet_conference_records_participants_list Read read
integration__google_meet__google_meet_conference_records_participants_participant_sessions_list google-meet.google_meet_conference_records_participants_participant_sessions_list Read read
integration__google_meet__google_meet_conference_records_participants_participant_sessions_get google-meet.google_meet_conference_records_participants_participant_sessions_get Read read
integration__google_meet__google_meet_conference_records_transcripts_list google-meet.google_meet_conference_records_transcripts_list Read read
integration__google_meet__google_meet_conference_records_transcripts_get google-meet.google_meet_conference_records_transcripts_get Read read
integration__google_meet__google_meet_conference_records_transcripts_entries_get google-meet.google_meet_conference_records_transcripts_entries_get Read read
integration__google_meet__google_meet_conference_records_transcripts_entries_list google-meet.google_meet_conference_records_transcripts_entries_list Read read
integration__google_meet__google_meet_conference_records_smart_notes_get google-meet.google_meet_conference_records_smart_notes_get Read read
integration__google_meet__google_meet_conference_records_smart_notes_list google-meet.google_meet_conference_records_smart_notes_list Read read

Write Access

Start with --write=deny for read-only MCP clients. Use --write=ask or --write=allow only when the client and workspace are trusted.