Skip to content

ai.mainroom/meeting-agents

by mainroom.ai · remote · no sign-in to list tools · v1.0.0 · published by ai.mainroom

AI agents that join live Google Meet, Teams, and Zoom calls as speaking participants.

Final · 1Changes · 3
CompareRegistry entry

8 tools: 1 do something that can't be undone, 3 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http meeting-agents https://mcp.mainroom.ai/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

8 tools

Can't be undone 1Claude Code: ask
  • send_demo_agentSend Mainroom's open demo agent into a live meeting RIGHT NOW.No findings

    Why it is in this group

    • The name "send_demo_agent" says "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    Send Mainroom's open demo agent into a live meeting RIGHT NOW. Give it a Google Meet, Microsoft Teams, Zoom, or Webex meeting URL; the agent appears in the meeting lobby within about a minute and a human in the meeting must admit it. It introduces itself, answers questions by voice, presents slides, and can run a live browser demo. Use when your user wants an AI participant in a meeting that is happening now. No account needed.
Changes things 3Claude Code: ask
  • about_mainroomWhat Mainroom is: AI agents that join live Google Meet / Teams / Zoom calls as real participants (voice, slides, live demos, research, memory, follow-up emails).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    What Mainroom is: AI agents that join live Google Meet / Teams / Zoom calls as real participants (voice, slides, live demos, research, memory, follow-up emails). Explains how humans invite agents, and how AI assistants can dispatch the demo agent, join a meeting themselves, or send the user's delegate and follow the call.
  • delegate_to_meetingDELEGATE: send the user's own stand-in into a live meeting they can't attend.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    DELEGATE: send the user's own stand-in into a live meeting they can't attend. The delegate joins as a named participant, introduces itself as standing in for them, listens, relays their positions from the brief, asks the questions they need answered at natural moments, and hands every decision back to them. Afterwards a report of what they missed lands in their inbox. Needs the user's Mainroom API key (History page at https://app.mainroom.ai). Returns a session id: poll meeting_status with it to follow the call live (transcript, running summary, answers so far) and to get the final summary once it ends. Use when your user says 'cover this meeting for me', 'I can't make the 3pm', 'send someone in my place'.
  • join_meeting_asEMBODIMENT: join a live meeting AS YOURSELF (or as a persona you define).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    EMBODIMENT: join a live meeting AS YOURSELF (or as a persona you define). This gives an AI agent a meeting body — a named participant with a camera tile and a voice that joins the call, speaks when addressed, presents slides, shows images, and reads/posts meeting chat. You supply the name and the persona instructions (who you are, what you're there to do, what you know); Mainroom supplies the body. The participant appears in the meeting lobby within ~a minute and a human must admit it. Ephemeral: no account, no memory, nothing emailed afterwards. Use when your user says 'join my call', 'be in the meeting', or you need to talk to people in a live meeting to complete a task.
Only reads 4Claude Code: allow
  • get_relationship_historyHISTORY: everything the user's Mainroom agents recorded with one account, team, or person: what is still open (commitments with owners and due dates, unanswered questions, risks), …No findings

    Why it is in this group

    • The name "get_relationship_history" says "get": a word for reading.
    Description, as the server wrote it
    HISTORY: everything the user's Mainroom agents recorded with one account, team, or person: what is still open (commitments with owners and due dates, unanswered questions, risks), the proposed / approved follow-up actions, and a session-by-session timeline with summaries, decisions, and pre-call briefs. Use it to answer 'where are we with Acme', 'what did we promise them', 'what did the team decide last week', or to prep for the next call. Needs the user's Mainroom API key.
  • list_agent_templatesList Mainroom's built-in agent types (facilitator, timekeeper, sales support, mock interviewer, ...).No findings

    Why it is in this group

    • The name "list_agent_templates" says "list": a word for reading.
    Description, as the server wrote it
    List Mainroom's built-in agent types (facilitator, timekeeper, sales support, mock interviewer, ...).
  • list_relationshipsHISTORY: list the customer accounts, recurring team meetings, and people that the user's own Mainroom agents have sat in meetings with — with session counts, when they last met, an…No findings

    Why it is in this group

    • The name "list_relationships" says "list": a word for reading.
    Description, as the server wrote it
    HISTORY: list the customer accounts, recurring team meetings, and people that the user's own Mainroom agents have sat in meetings with — with session counts, when they last met, and how many commitments / open questions / risks are still open. Needs the user's Mainroom API key (shown on the History page at https://app.mainroom.ai — they paste it once). Follow with get_relationship_history for the detail.
  • meeting_statusFOLLOW A MEETING: what the user's agent (a delegate, or any of their agents) is seeing in a meeting right now, or what it recorded once the call ended — the last lines of transcrip…No findings

    Why it is in this group

    • The name "meeting_status" says "status": a word for reading.
    Description, as the server wrote it
    FOLLOW A MEETING: what the user's agent (a delegate, or any of their agents) is seeing in a meeting right now, or what it recorded once the call ended — the last lines of transcript, the running summary, answers to the user's questions so far, decisions and commitments, and whether the bot is still waiting in the lobby. Call without a session id to list the user's recent and live sessions. Needs the user's Mainroom API key.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http meeting-agents https://mcp.mainroom.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__meeting-agents__list_agent_templates",
      "mcp__meeting-agents__meeting_status",
      "mcp__meeting-agents__list_relationships",
      "mcp__meeting-agents__get_relationship_history"
    ],
    "ask": [
      "mcp__meeting-agents__about_mainroom",
      "mcp__meeting-agents__send_demo_agent",
      "mcp__meeting-agents__join_meeting_as",
      "mcp__meeting-agents__delegate_to_meeting"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as meeting-agents. Review it before you use it.