MCP server for interacting with your LINE Official Account
Nothing to run from here
Meeting Agents is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
8
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
AI agents that join live Google Meet, Teams, and Zoom calls as speaking participants.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http meeting-agents-mcp https://mcp.mainroom.ai/mcp
# 2 — ask your agent for something these tools do
# about_mainroom, list_agent_templates, send_demo_agent and 5 more
Meeting Agents costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MAAll 1 server
mainroom1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http meeting-agents-mcp https://mcp.mainroom.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
List Mainroom's built-in agent types (facilitator, timekeeper, sales support, mock interviewer, ...).
No parameter schema on file.
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 ha
| Parameter | Type | Required | Notes |
|---|---|---|---|
| meeting_url | string | yes | Full join URL of the live meeting (https://meet.google.com/..., https://...zoom.us/j/..., https://teams.microsoft.com/l/meetup-join/...). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| meeting_url | string | yes | Full join URL of the live meeting (Google Meet, Zoom, Microsoft Teams, or Webex). |
| agent_name | string | yes | The display name for your meeting body (e.g. 'Claude', 'Atlas — Research Agent'). Shown on the tile and the roster. |
| instructions | string | yes | Persona + mission, second person ('You are... You're joining this call to...'). Include what you know and how to behave. Up to 2000 chars. |
| intro | string | no | Optional one-paragraph welcome posted into the meeting chat when you join (say who you are and why you're there). |
| voice | string | no | TTS voice (default alloy). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | The user's Mainroom API key (mr_...). |
| meeting_url | string | yes | Full join URL of the live meeting (Google Meet, Zoom, Microsoft Teams, or Webex). |
| principal_name | string | yes | The user's name as the room knows them (e.g. 'Taylor'). The delegate speaks of them by this name. |
| brief | string | no | What the user wants the room to know: their positions, context, what they'd say if asked. The delegate relays this and nothing beyond it. Up to 4000 chars. |
| questions | array | no | Up to 10 questions the user needs answered on this call. The delegate asks each at a natural moment and records the answer. |
| persona_name | string | no | The delegate's own first name (default Reese). |
| voice | string | no | TTS voice (default sage). |
| rehearse | boolean | no | Set up the delegate and a session WITHOUT joining any meeting — to check the brief and the setup. Nothing is dispatched. |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | The user's Mainroom API key (mr_...). |
| session | string | no | Session id from delegate_to_meeting (or from this tool's list). Omit to list recent sessions. |
| lines | integer | no | How many recent transcript lines to include (default 40). |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | The user's Mainroom API key (mr_...), from the History page in the app. |
| query | string | no | Optional name filter (account, team, or person). |
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 decid
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | yes | The user's Mainroom API key (mr_...). |
| relationship | string | yes | Account / team / person name, or a key from list_relationships. |
| sessions | integer | no | How many recent sessions to include in the timeline (default 6). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Meeting Agents or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Meeting Agents can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.