gifos-mcp
The server lets an agent create/join GifOS meetings, run a transcribing bot, post chat text, retrieve transcripts, and manage basic meeting state.
Create meeting links with a topic and optional informational start time; nothing joins automatically.
Start a bot in a created meeting or join an existing GifOS meeting by link, optionally with a password and topic.
Mute or unmute the bot’s transcription in a meeting.
Share text or links into meeting chat as the bot, up to 2,000 characters.
Get the live or saved transcript as plain text.
End the bot’s participation and save the transcript; other participants remain.
List meetings this server created or joined and check connector/browser/meeting status.
Note: this schema does not expose the README’s scheduling, recording, room/admin-password management, guard, agenda, stage, or app tools.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@gifos-mcp create a GifOS meeting and send the note-taking bot"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
gifos-meet-mcp: GifOS meetings for Grok Bot
In short, for agents (the full briefing is below):
Rooms are open (anyone with the link) or admin (a host; the admin password's signature is in the link). Asked for an admin room with no password? Leave
host_passwordout: the server makes a strong one, keeps it (0600) and signs the bot in.Links are capabilities: share them only with invitees. Never put a password in chat, an invite or a link unless the user asks.
The user's credentials GIF (subscription or pass) unlocks their plan: hand it over by path (
use_credentials,guard_room). It works in one meeting at a time.You are the bot's brain:
wait_linesto listen, thensend_chatorsayto answer.Something failed? See the failure table.
What people say, and what to do. Map requests by meaning, in any language ("una llamada", "ein Meeting", "uma reunião" are all "a call"); answer in the user's language. Don't ask what these defaults answer. "Room password" = who may enter; "admin password" = the host's, kept private by the server.
The user says | Do this |
"a call", "a meeting", "set up a zoom / hangout / video chat / conference", "a quick call", "a test call" |
|
"with a password", "a private call", "a call nobody else can get into" | Also |
"send me info to join", "send me the link" | The join link + the room password (if any) + one line: "Open the link in a browser, type the password when asked." Or the |
"a meeting for my team at 3pm tomorrow" |
|
"a recurring weekly standup" | As above, plus |
"make it public", "anyone can join" | An open room: |
"a big call", "a webinar", "30 people" | An open room (no limit), or an admin room with the user's $5/$10 plan ( |
"it says the room is full" | A free admin room is at 5 (or $2 at 20). Use an open room, or the user's $5/$10 plan ( |
"lock it", "change the password" | Set the room password with |
"kick someone out", "remove X" | No remove tool here, and GifOS keeps no ban list. In an admin room the host taps Remove on that person's tile: the room password changes and everyone else gets the new one. Tell the user how, or lock the room for newcomers (row above). |
"who's in the call?" |
|
"take notes", "transcribe", "what did they say?", "summarize the meeting" | The bot transcribes from the moment it joins. |
"record it" | Recording is on by default ( |
"send me the notes" | Put them in your reply, or send them with the user's own mail connector; this server sends nothing. |
"join my meeting at " |
|
"join and say hi", "introduce yourself", "answer questions" |
|
"be quiet", "stop listening", "leave" | Quiet: just don't |
"end the meeting", "close the room" |
|
"use my subscription", "here's my GifOS file", "I have a pass" |
|
"why can't they see video?" | With no room password, everyone stays blurred: set one. On a network that blocks direct links, the free plan carries sound but not video over TURN; a paid plan carries video. |
"make me the host", "give me admin" |
|
"share my screen" | A person's own action: the Share screen button (Alt+S) in their meeting. In an admin room the host may first need to allow guests to share. The bot cannot share a screen for them. |
How GifOS meetings work, for agents
Read this before calling any tool. The tool descriptions and the server's MCP instructions say the same, shorter.
Rooms. A GifOS meeting is a room, reached by its link. There are two kinds:
An open room: anyone with the link joins. It has no host and no door limit. Anyone inside may set its room password while nobody holds it. A subscriber on the $5 or $10 plan, or a staff pass, can capture it ("Make me admin"); from then on only the captor sets its password, until the captor's ticket stops renewing.
An admin room: a room with a host. What makes it one is the admin (host) password: its signature goes into the link (
/meet/<room>/<verifier>). There is no admin room without one. Only the host sets the room password, lets people on the stage, runs the agenda and blurs guests. The door lets in 5 people on the free plan, 20 on $2, no limit on $5 and $10. The room closes 5 minutes after the last host leaves.The user gave an admin password: pass it as
host_password. It is used for that call only, never kept.The user gave none: do not invent one and do not ask. Leave
host_passwordout. The server makes a strong random one, keeps it in<GIFOS_MCP_HOME>/host-passwords.json(mode 0600) and signs the bot in with it. Tell the user it was made and where it is kept. Show it only if the user asks (get_host_password).
The room password is a different thing: it decides who may ENTER, in either kind of room. Guests type it. It goes in the invite text, never in the link. With no room password, GifOS shows nobody clear video (everyone is blurred); a room password is what makes clear video possible.
Links. A meeting link is a capability: anyone holding it can join. Share it only with the people the user invites, through the user's own mail or calendar (this server sends nothing). An admin room's link carries only the verifier, never the admin password. Never put any password (admin, room, the bot's own) in chat, an invite or a link unless the user asks for that.
Credentials.
The bot's own name and password (
GIFOS_BOT_NAME,GIFOS_BOT_PASSWORD, else a stored pair inbot.json) are its identity: whoever has the pair can command the bot. Never show them.The user's credentials GIF is a GifOS subscription file (Settings > Subscription) or a pass. It is the plan itself: bigger admin rooms, video over TURN on networks that block direct links, and open-room capture on $5, $10 or a staff pass. Hand it over by path or base64 with
use_credentials(any meeting),credentialsonguard_room, orGIFOS_CREDENTIALSat start. It is read once, put only into the bot's own browser, and never logged or returned. Never paste its bytes in chat or ask the user to. A plan works in one meeting at a time: joining a second meeting moves it there, and the first loses it within minutes.
The bot's role. The bot joins as a tile labelled 🤖 bot, transcribes, and says or writes only what you give it
(say, send_chat). You are its brain: follow the room with wait_lines (blocks until a new line) or
tail_lines, and answer with send_chat (text) or say (spoken). With talk: true the bot itself answers lines
addressed to it, and wait_for_speech hands you each one; with talk off it never answers on its own.
Etiquette: an open room's chat allows one line per 10 seconds per person, so batch replies; keep lines short; do
not speak over people. Consent: every participant always sees 📝 Transcribing, and ⏺ recording on the bot while it
records (GIFOS_ALWAYS_RECORD=1 by default). Tell the user before recording people who did not expect it; mute
stops note-taking and end_meeting takes the bot out.
Holding a room (guard). guard_room keeps the bot in a room as its admin: an open room by capture with a
credentials GIF that may capture, an admin room by its host password. It keeps the room password as set (none by
default), blurs guests and greets newcomers. Copies of the same bot on several computers (siblings: same name,
password and credentials, GIFOS_BOT_SIBLING=1, a different rank) are all admins at once; one leads (greets,
answers), and if it dies the next leads with no gap in the hold; a restarted copy comes back as an admin. Removing
someone means setting a room password: everyone inside keeps it, the removed person does not get it. GifOS keeps
no ban list (a person can change browsers), so a room kept with no password removes nobody.
Privacy and cost. Sound and video go peer to peer between participants; the GifOS relay only introduces them and carries no content. Transcripts, recordings and this server's files stay on this computer. TURN (a paid relay for media) is used only when a network blocks direct links: free plans get everything but video over it. Do not join rooms, poll or repeat calls without need: every join and capture touches GifOS servers.
Failure modes.
The tool says | What it means | Do this |
| No admin password was given or kept for that room. | For a new room, leave |
The door asks for a password / | The room has a room password. | Ask the user for it; pass it as |
|
| End a meeting first, or schedule the join. |
| Another copy uses the same bot identity. | Give this server its own |
| The site is older than 0.9.26. | Use gifos.app or a 0.9.26 site. |
| Joining that room took the bot's browser down. | Wait the minutes it names; tell the user. |
| This network blocks direct links. | TURN carries it when the site offers it; with no plan, sound only. |
| The credentials' plan moved to another meeting, or someone else holds the open room. | Use one meeting per plan; the guard takes the room back when the other hold lapses. |
| The credentials file is wrong. | Ask the user to export it again from Settings > Subscription. |
Related MCP server: Grok Web MCP
Recipes for agents
Exact tool calls. Ids and links come from the previous answer.
A free admin room named "test" with room password "test password" (no admin password given):
{ "tool": "create_meeting", "arguments": { "name": "test", "type": "admin", "room_password": "test password" } }The answer has link, invite (send its text yourself) and host_password: { "made": true, "kept_in": "…/host-passwords.json" }.
Tell the user: "I made a strong admin password for the room and kept it in <kept_in>; ask me if you want to see it."
To put the bot in the room as its host:
{ "tool": "start_meeting", "arguments": { "meeting_id": "<meeting_id>", "room_password": "test password" } }The answer says bot_is_host: true. A free admin room lets in 5 people; a $2 plan 20; $5 and $10 no limit.
Hold an open room with a credentials GIF (a $5/$10 subscription file or a staff pass, on this computer):
{ "tool": "guard_room", "arguments": { "link": "https://gifos.app/meet/<room>", "credentials": "/path/to/credentials.gif" } }The bot joins, takes the room ("Make me admin"), keeps it with no password and greets newcomers. guard_status shows
its role (lead, coadmin, taking, held-by-other); stop_guard stops it.
Use your pass or subscription in any meeting (the bot joins with your plan: a paid room plan, TURN on blocked networks):
{ "tool": "use_credentials", "arguments": { "path": "/path/to/credentials.gif" } }or { "gif_b64": "<the file, base64>" } when the file is not on this computer. Then join as usual.
Join someone else's meeting:
{ "tool": "join_meeting", "arguments": { "link": "https://gifos.app/meet/<room>", "password": "<room password, if any>" } }If they want the bot to run the room as host, add "host_password": "<their admin password>" (used once, never kept).
Then wait_lines / get_transcript to follow it, send_chat or say to speak, leave_meeting to go.
How it works
Grok Bot ──MCP (stdio)──▶ gifos-meet-mcp ──▶ headless Chromium (one profile in ~/.gifos-mcp)
(the brain) └─ GifOS desktop
├─ Meeting Bot (window.MeetingBot v2): joins, captions, speaks
└─ Offline Captions (Whisper): speech to textGrok Bot is the brain. The server has no language model. On every join Meet Bot is handed
respond_to_commandandspeak, both off (and never the oldconversation_voice,llm,tts, orsttfields). Turning the microphone on and transcribing does not make the bot answer. talk:true does: it turns those two switches on so the bot answers a line addressed to it, and it hands you that line.wait_for_speechblocks until one arrives, and a talk notification carries the same line. You can stillsaya line of your own. With talk left off, the bot does not answer.Scheduling without joining.
create_meetingmints a link and returns every invite detail (title, start and end with time zone, join link, description, how guests get in, who does what, ready-to-send text). Nothing joins and nothing is sent: Grok Bot sends the invite through the user's own mail or calendar.Fast replies.
wait_linesreturns the moment someone says something (captions are copied every 300 ms), withto_bot: trueon lines addressed to the bot.sayspeaks a line at once.Speech is Kokoro (kokoro-js 1.2.1), running in this process with its default voice
af_heart;saytakes an optionalvoicefor one line. Speech to text is GifOS Whisper in the headless browser. The bot writes down each participant who is unmuted, credited by name, and never its own machine's microphone.
Quick start
You need Node.js 20 or newer, git, and Google Chrome or Microsoft Edge (see The browser below).
This is the exact command the plugin's .mcp.json runs (stdio):
npm_config_ignore_scripts=true ONNXRUNTIME_NODE_INSTALL_CUDA=skip \
npx -y npm@11.6.2 exec -y -- github:nwcnwc/gifos-meet-mcp#30c2fe85a92bbe53bd5f84cfd2aa86901c2617bdIt speaks MCP over stdio, so on its own it waits for a client. npm@11.6.2 exec is there because the npm in
Node 22 (10.9) fails on any npx github: package; with npm 11 or newer, npx -y github:nwcnwc/gifos-meet-mcp
(the newest commit) works directly. The first run downloads about 700 MB of packages (Kokoro and ONNX Runtime).
or from a clone:
git clone https://github.com/nwcnwc/gifos-meet-mcp.git && cd gifos-meet-mcp
npm install --ignore-scripts
node bin/gifos-meet-mcp.js # stdio
node bin/gifos-meet-mcp.js --http # or streamable HTTP on http://127.0.0.1:19520/mcpInstall scripts are not needed and should be off. This package and gifos-mcp-core have none. Three
dependencies of kokoro-js do: onnxruntime-node would download CUDA libraries from GitHub on Linux x64,
sharp checks for a system libvips, protobufjs checks its version. The CPU build of ONNX Runtime and sharp's
prebuilt binary ship inside the packages, so --ignore-scripts loses nothing. The plugin's .mcp.json sets
npm_config_ignore_scripts=true and ONNXRUNTIME_NODE_INSTALL_CUDA=skip.
The browser. The server drives the browser already on your computer: GIFOS_CHROME if set, else Google
Chrome, else Microsoft Edge, else a Chromium that npx playwright install chromium installed earlier. It never
downloads or installs a browser. With none of these it stops and says what to install.
Grok Bot setup
As a plugin, this repository has .grok-plugin/plugin.json, .mcp.json and skills/gifos-meet/SKILL.md.
By hand, add a local (stdio) MCP server:
{
"mcpServers": {
"gifos-meet": {
"type": "stdio",
"command": "npx",
"args": ["-y", "npm@11.6.2", "exec", "-y", "--", "github:nwcnwc/gifos-meet-mcp#30c2fe85a92bbe53bd5f84cfd2aa86901c2617bd"],
"env": { "npm_config_ignore_scripts": "true", "ONNXRUNTIME_NODE_INSTALL_CUDA": "skip", "GIFOS_URL": "https://gifos.app" }
}
}
}That pin is the same commit as .mcp.json (the code commit just before the commit that pins it). It runs through npm 11 (npm@11.6.2 exec) because the npm that ships with Node 22 (10.9) cannot run a package straight from GitHub with npx ("GitFetcher requires an Arborist constructor").
The server warms up as soon as Grok Bot starts it (about 10 seconds, plus first-run downloads), so the first join does not wait. It must be running at meeting time for a scheduled join: run it on an always-on machine.
--http [port] listens on 127.0.0.1 only, checks the Host header, and requires Authorization: Bearer <token> when GIFOS_MCP_HTTP_TOKEN is set.
Endpoints, downloads and credentials
What | Where | When | Size |
GifOS site |
| every start | — |
GifOS relay | GifOS's default relay, or | while in a meeting (it only introduces peers) | — |
Meeting Bot and Offline Captions apps | the GifOS store on | first start | small |
Whisper model | through the Offline Captions app | first transcription | about 77 MB |
Kokoro weights |
| first start, kept in | about 92 MB; each file is checked against its pinned SHA-256 |
npm packages | the npm registry and GitHub (gifos-mcp-core) | install | — |
Credentials. The only secret this server holds is the bot's own name and password, which open Meeting
Bot's admin meeting. They are generated once into GIFOS_MCP_HOME/bot.json (mode 0600), or come from
GIFOS_BOT_NAME/GIFOS_BOT_PASSWORD. A host password passed to create_meeting is used for that call only;
a room password passed to schedule_meeting or join_meeting is stored in schedule.json (mode 0600) so a
restart can rejoin, and is never returned. The server reads no other secret, sends no telemetry, and never
sends email or calendar invites.
How the bot looks. The operator chooses the bot's name and picture: GIFOS_BOT_NAME and
GIFOS_BOT_PICTURE in the server's env, or the set_bot_profile tool, which Grok Bot can call. The picture is
read from a file on this computer and kept in GIFOS_MCP_HOME/bot-picture.json (mode 0600); it is sent to rooms
like any person's picture and nowhere else.
Environment variables
Variable | Default | What it does |
|
| The GifOS site (0.9.25 or newer; 0.9.26 for the agenda, app and stage tools). |
| GifOS default | A custom relay ( |
| generated | The name people see on the bot's tile (3 to 40 characters). Set alone, it keeps the stored password. |
| generated | The bot's password (the secret half). A |
| none | Path to the bot's picture: a GIF, PNG, JPEG or WebP file, at most 256 KB. Rooms show it on the bot's tile like anyone's picture. |
|
| The store app for speech to text. |
|
| Browser profile, bot credential, |
| none | Path of a GifOS credentials GIF (a subscription file or a pass). Read once at start; the bot joins every meeting with that plan (as |
| none | A guard config: rooms the bot holds as their admin from the start (Guard a room). |
|
|
|
|
|
|
| Chrome, then Edge | A Chrome or Chromium binary to use instead. |
|
| How long to wait for GifOS steps such as joining. |
| none | Bearer token for |
|
|
|
|
| Every meeting the bot starts or joins is recorded. |
|
| Every join turns captions on. |
|
| Long meetings: the recording is saved to disk as a new segment file every this many minutes. |
|
|
|
| none | A folder for screenshots of the bot's screens. |
|
| How often captions are copied from Meet Bot into the lines. |
|
|
|
|
| Kokoro's default voice for every line. |
| empty | A GifOS store speech app instead of Kokoro in this process. |
|
| A mirror with the Hugging Face layout for the Kokoro weights. The pinned revision and hashes still apply. |
| empty | HTTP stand-ins for speech and captions (testing). This process calls them; the page does not. |
|
| Seated meetings at once. A join over the cap is refused; a scheduled join waits. |
|
| Stage B. More than 1 makes this process a supervisor and runs each Meet Bot in its own child process and Chromium. Worker 0 keeps the bot name and |
| cap / workers, rounded up | Rooms per worker. |
Tools
Meeting tools (this server):
Tool | Arguments | Returns |
|
|
|
|
| The host password the server made for that admin room. Only when the user asks to see it. |
|
| The bot joins every meeting with the user's credentials GIF (subscription or pass). Read once, kept in memory, put only into the bot's browser; never logged or returned. |
|
| The bot joins now and starts transcribing; in an admin room it signs in as host (with the given password, or the one the server made). |
|
| The bot joins someone else's GifOS meeting now. |
|
| Blocks until a line addressed to the bot arrives in a meeting joined with |
|
| Meet Bot's hand, microphone and camera, or the gap when the app lacks the method. |
|
| Meeting Bot records the room. Everyone sees ⏺ recording on the bot while it is on. |
|
| Stops recording if on, saves the file under |
|
| The meeting archive on disk: folders, recording segment paths, transcripts. |
GifOS 0.9.26 meeting tools (from gifos-mcp-core). Each acts as the bot's own seat with that seat's rights; in a
room with a host, the host-only ones need sign_in_as_host first:
Tool | Arguments | Returns |
|
| Signs the bot in as the host (Admin > Sign in). A given password is used once, never stored or returned; omitted, the one the server made for that room. The bot's browser forgets the room's host key when it leaves. |
|
| Shares the agenda in the meeting's Agenda tab, with timekeeping. Refused if one exists unless |
|
| Moves the agenda on (the first call starts item 1) and restarts its clock. |
|
| The items, |
|
| Apps the bot can run in the meeting for everyone; run one by name or app id; stop the one it started. |
|
| Runs and drives Take Turns: who is up now and next, the time left, the order. Take Turns asks the person whose turn it is onto the stage on their own page; it never turns a camera or microphone on. |
|
| Who is on the stage; step the bot on or off; as host, allow or disallow a person (ids from |
Shared tools (from gifos-mcp-core, the same in gifos-broadcast-mcp):
Tool | Arguments | Returns |
|
| Returns as soon as there is a line after |
|
| The lines after |
|
| Plain text, one |
|
| Meet Bot says the line out loud now (Kokoro). |
|
| Sets how the bot looks: the name on its tile and its picture (GIF, PNG, JPEG or WebP, at most 256 KB). Both are kept in |
|
| A chat line as the bot (up to 2000 characters). |
|
| Who is here; a PNG of the bot's page. |
|
| Stop or restart note-taking. |
|
| Saves the transcript, then the bot leaves. Other people stay. |
|
| Stores the join order, including the room password, in |
| see the schemas | Join orders. No passwords in results. |
| — | State, people, line counts, capacity. No passwords. |
|
| Connector events, including |
The resource gifos://meeting/{id}/transcript is the live transcript as newline-delimited JSON; subscribe for
notifications/resources/updated.
Guard a room (a welcome bot for an open room)
The bot can hold a GifOS room as its admin, so nobody else can take the room or change its password, and keep the room the way you set it. It needs GifOS 0.9.26 or newer.
An open room (anyone with the link joins) is held by capture: the bot loads a GifOS credentials file (the subscription GIF from Settings > Subscription, on the $5 or $10 plan, or a staff pass) and takes the room with the page's own "Make me admin". From then on only the bot can set the room's password.
A room with a host (
mode: "admin") is held by signing in with itshost_password.
The policy:
field | default | what the bot does |
|
|
|
|
| Presses Blur guests when the page offers it to the bot. |
|
| The welcome the lead bot posts in chat for newcomers (batched: an open room's chat allows one line per 10 s). |
|
| Sibling order (below). |
| none | A module that talks with people (below). |
Your own welcome. The welcome is yours to set; the default is only a neutral start. Through the tool, an agent sets it from a plain request such as "greet people with ...":
{ "tool": "guard_room", "arguments": { "link": "https://gifos.app/meet/<room>", "credentials": "/path/to/credentials.gif",
"greet": "Hi {names}! Today we are practising chess openings. Ask anything." } }In a guard config file it is the same field: "greet": "Hi {names}! ...", or "greet": false for none. Text
without {names} is ignored and the default is used. Change it by calling guard_room again, or by editing the file and
restarting the service.
Removing someone is setting a password: everyone inside keeps it and the removed person does not get it. GifOS keeps no ban list (a person can change browsers), so a room held with no password removes nobody. To remove people, hold the room with a password.
Siblings. Run the same bot (same GIFOS_BOT_NAME, GIFOS_BOT_PASSWORD and credentials file) on two or more
computers, with GIFOS_BOT_SIBLING=1 and a different rank on each. All of them are the room's admin
at once. With a subscription file, the one holding its meeting ticket leads (greets, answers people); when its seat
is gone, the next one takes the ticket back before the hold can lapse, rank 0 first. With a pass (the staff pass),
every sibling in the room keeps a ticket; the lowest rank present leads, and the next leads as soon as its seat goes. With a room nobody holds, rank N waits N minutes
before taking it, so siblings never race.
Talking with people. handler names a module that exports onMessage(message, room). The lead bot calls it for
every chat or spoken line a person sends in the room: message is { text, from, kind, at }, and room.sendChat(text)
or room.say(text) answers. examples/guard/claude-handler.mjs wires it to Claude
with the Anthropic SDK. Without a handler, you are the brain: wait_lines and send_chat work in a guarded room like
in any other.
Start it either from your assistant with the guard_room tool (guard_status, stop_guard), or when the server
starts: set GIFOS_GUARD_CONFIG to a file like examples/guard/welcome-room.json
(paths in it are relative to the file). examples/guard/gifos-meet-guard.service
runs it as a systemd user service that restarts on failure.
The credentials file is read once and its bytes go only into the bot's own browser. It is never logged, returned or
sent anywhere else. Keep it chmod 600: whoever holds it holds the plan.
Meeting archive
Each meeting the bot joins gets a folder that survives restarts: <home>/meetings/<date>-<room>-<meeting_id>/ with meta.json, recording-001.webm, recording-002.webm, … (one per segment, in order), transcript.json and transcript.md. The transcript is rewritten every 30 seconds while the meeting is live. On end_meeting, leave_meeting or a clean shutdown the last segment and transcript are saved; after a crash the folder is marked interrupted on the next start and keeps every segment already saved. list_past_meetings and get_past_meeting find them. Recording defaults on because the Meeting Bot always shows the ⏺ recording indicator to everyone; set GIFOS_ALWAYS_RECORD=0 where that is not wanted.
Example: a 5 PM meeting
The user says: "Set up a meeting with Alice and Bob at 5 PM, take notes, and send me a summary."
Grok Bot calls
create_meeting({ name: "Demo", start: "2026-10-20T17:00", timezone: "America/Los_Angeles", room_password: "<made up>" })and gets the link andinvite.Grok Bot sends
invite.textto Alice and Bob from the user's mail, after the user approves.Grok Bot calls
schedule_meeting({ link, room_password, start }). The bot joins at 16:59.During the meeting Grok Bot loops on
wait_linesfor notes. To have the bot answer when someone says its name, passtalk: trueonstart_meetingorjoin_meetingand loop onwait_for_speech. Turning the microphone on and transcribing does not make the bot answer. talk:true does. Ato_botquestion is answered withsaywhen you want words of your own.Afterwards Grok Bot calls
end_meeting, readsget_transcript, writes the summary and, with the user's approval, sends it.
Privacy and security
Everything runs locally. The browser, the bot, one shared speech-to-text engine, and the transcripts are all on your machine. Media goes peer to peer between participants. GifOS's relay only helps peers find each other.
Consent is visible. A GifOS meeting is always written down, and every participant's header always shows 📝 Transcribing, also when the call is calm. The bot is a tile labelled 🤖 bot for as long as it is in the meeting.
mutestops the bot writing the meeting down;end_meetingtakes it out.The bot never uses your microphone or camera. It joins with no camera, Meeting Bot never transcribes its own machine's microphone, and its browser is fed a silent fake microphone anyway.
Only one secret. The bot name and password derive Meeting Bot's secret admin meeting, which can command the bot from another device (Meeting Bot's CONTROL mode). Keep
GIFOS_MCP_HOME/bot.jsonprivate (it is mode 0600), or pass the pair through environment variables. Anyone with the pair can command the bot.Meeting links are capabilities. Anyone with a link can join that meeting, so share links only with the people you invite.
Transcripts are stored in
GIFOS_MCP_HOME/meetings.json(mode 0600) so they survive restarts. Delete the file to forget them. It is written to a temp file then renamed, so a save cut short keeps the last good file; a file that cannot be read at start is kept asmeetings.json.bad-<ms>(mode 0600, logged) and not overwritten. Delete any*.bad-*file too (abot.json.bad-*holds an old bot password). A join whose save fails (disk nearly full) still holds its seat and reads its captions; the failure is logged and the next save writes it. The same holds forschedule.json: a clock tick whose save fails still seats, waits and ends its orders, logs the failure once until a save works, and the next save writes their phases. Anend_meeting(or a clock leave) whose saves fail still reports the leave, raisesmeeting.left, and keeps the meeting ended and its orderleft_earlyorendedin memory, so no tick seats the bot again. Ajoin_meetingwith a password whoseschedule.jsonsave fails still reports the join and raisesmeeting.joined; its order (with the room password) is keptlivein memory and the next save writes it. Amute,unmuteorget_transcriptwhosemeetings.jsonsave fails still answers with what the bot did (muted, listening, the transcript); memory keeps it and the next save writes it. A transcript line whose append totranscripts/<id>.jsonlfails keeps every caption line of that snapshot (and itsline.*event),send_chatandsaystill report what Meet Bot sent, and the kept lines are written in order at the next append that works. A file whose last line was torn is ended before the next line.No model, no key. There is no language model in this server and no model URL or API key is read. The assistant that calls the tools writes every word the bot says, except a meeting joined with
talk: true: that hands Meet Botrespond_to_commandandspeak, both on, so it answers a line addressed to it.MeetingBot.setVoicereceives{ respond_to_command: false, speak: false }on every join first, and never the oldconversation_voice,llm,tts, orsttfields. Turning the microphone on and transcribing does not make the bot answer. talk:true does. With talk left off, the bot does not answer.No outgoing messages. The server never sends email, calendar invites or anything else. Grok Bot does that through your own connectors, and you approve each send. Follow-up after the meeting is Grok Bot's job.
HTTP mode binds to 127.0.0.1, checks the
Hostheader (DNS-rebinding protection), and can require a bearer token.
Troubleshooting
Symptom | Fix |
| That GifOS is too old. Set |
| The agenda, app and stage tools need GifOS 0.9.26. |
The bot is in the room but nobody hears it (a | This computer's network blocks the direct connections a meeting needs. GifOS 0.9.26 bridges such parts of a meeting over TURN; see Networks that block UDP. |
| Another server (or a Meeting Bot window) uses the same name and password. Give this one its own |
| Somebody has to speak with their mic on. The first transcription downloads the Whisper model (about 77 MB). |
| A download was cut or a mirror served other bytes. The file was removed; start again. |
| Install Google Chrome, or run |
A scheduled join did not happen | The server was not running, or the machine was asleep. |
The store install of Offline Captions stops at "That file isn't a GifOS app" | Chrome unpacks the 13 MB app into blob storage in its profile; a full or small disk under |
Anything else |
|
The e2e runner (test/e2e/run.js) serves a local site unless GIFOS_URL or E2E_GIFOS_URL is already set; then it uses that site and does not start its own.
Networks that block UDP
A meeting's sound and video go peer to peer. On a network that drops UDP (some offices, some sandboxed
computers), a GifOS 0.9.25 page cannot reach the people outside it: the bot sits in the room unheard and
get_meeting_state returns a warning. GifOS 0.9.26 joins such parts of a meeting over TURN; a TURN server
on TCP or TLS port 443 is what reaches a network that blocks all UDP. This server needs no setting for it:
the bot's browser uses whatever the GifOS site offers.
Testing instructions for marketplace reviewers
1. Unit tests (no network, about a minute).
git clone https://github.com/nwcnwc/gifos-meet-mcp.git && cd gifos-meet-mcp
npm install --ignore-scripts
npm testThey run every tool over a real MCP client/server pair with a fake bot, the --http transport through the real
binary, the worker supervisor, and the real Meeting Bot app bundle in a local page, which checks that the bot
answers nothing on its own and speaks exactly the line say gives it.
2. Try it live. Add the plugin (or the .mcp.json above) to Grok Bot, then ask "Create a GifOS meeting
called Demo and start it." Open the link in Chrome on another computer or phone, turn your mic on and say
something. Ask "What did I just say?" (Grok Bot uses wait_lines or get_transcript), then "Say hello in
the meeting." and "End the meeting." The first start downloads the Meeting Bot app, the Whisper model
(about 77 MB) and the Kokoro voice (about 92 MB).
3. Full end-to-end test against a local GifOS (what the maintainers run; needs a GifOS relay, which the gifos-app checkout's site uses by default).
git clone --branch release/0.9.26 --single-branch https://github.com/nwcnwc/gifos-app.git ../gifos-app
mkdir -p .e2e/tmp && TMPDIR=$PWD/.e2e/tmp GIFOS_APP_DIR=../gifos-app npm run test:e2e:whisperIt serves the GifOS checkout on 127.0.0.1:19510, spawns this server over stdio, creates a room the host runs,
lets the bot join, has a second headless browser ("Alice") speak a recorded sentence, and checks that Whisper
wrote her words, that the bot's spoken reply reaches Alice, the agenda, Take Turns, the stage, chat, mute and
end. E2E_STT=synthetic npm run test:e2e swaps Whisper and Kokoro for stand-ins.
License
MIT License. Copyright (c) 2026 Crowd Concepts, Inc. See LICENSE. GifOS, Meeting Bot and Kokoro are separate projects with their own licenses.
Available Tools
10 toolscreate_meetingCreate a GifOS meetingA
Creates a new GifOS meeting link. Nothing joins yet: share the link (for example in a calendar invite the user approves), then call start_meeting at meeting time. start_time is stored as given, for your own scheduling; this server does not schedule anything.
Inputs: topic (required), start_time.
end_meetingEnd the meeting for the botA
Saves the transcript, then the bot leaves. Other participants can stay; GifOS meetings have no owner who can close them for everyone.
Inputs: meeting_id (required).
get_transcriptGet the meeting transcriptA
Returns the transcript as plain text, one "speaker: words" line per caption. Works while the meeting is live and after end_meeting.
Inputs: meeting_id (required).
join_meetingJoin an existing GifOS meeting by linkA
The Meeting Bot joins a GifOS meeting someone else created (a /run.html#v=… or /meet/… link) and starts transcribing. Returns a meeting_id for the other tools.
Inputs: link (required), topic, password.
list_meetingsList meetingsA
Meetings this server created or joined, newest first, with their state (scheduled, live, ended).
Inputs: no named parameters.
muteMute the bot (stop listening)A
Stops the bot transcribing this meeting; the transcribing chip goes away. The bot never sends audio, so this is the only kind of mute it has.
Inputs: meeting_id (required).
start_meetingStart a meeting (the bot joins and transcribes)B
The headless Meeting Bot joins the meeting created with create_meeting and starts transcribing. Participants see a 🤖 bot badge and a transcribing chip.
Inputs: meeting_id (required).
statusConnector statusA
Is the headless GifOS browser up, which GifOS it uses, and which meetings the bot is in right now.
Inputs: no named parameters.
unmuteUnmute the bot (listen again)B
Turns transcription back on for this meeting.
Inputs: meeting_id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 10 tools
Each tool targets a distinct action, and the descriptions actively disambiguate the subtle create_meeting vs start_meeting vs join_meeting distinction (create only makes a link, start joins your own, join handles someone else's). mute/unmute and share_content/get_transcript are obviously separable. No two tools appear to do the same thing.
The set is dominated by a clean snake_case verb_noun pattern (list_meetings, create_meeting, start_meeting, join_meeting, share_content, get_transcript, end_meeting). The single-word tools mute, unmute, and status are minor deviations from that pattern but remain clear and readable.
Ten tools is well within the ideal range and each one covers a real stage of the meeting-bot lifecycle. Nothing feels padded or redundant; the surface is tightly scoped to the server's purpose.
The lifecycle is largely covered: create, start, join, list, mute/unmute, share, retrieve transcript, end, and status. Minor gaps remain (e.g. no tool to fetch or delete a single meeting, and no way to remove/inspect an ended meeting beyond the transcript), but core workflows are usable end to end.
Maintenance
Related MCP Connectors
Krisp MCP server for ChatGPT, Claude and any AI agent: list meetings, get meeting notes and transcript, list action items, share meeting, change meeting access, add meeting to folder, update action item and tag meeting in your own Krisp account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Krisp yourself; Cotlet does not store your password and you need no Krisp API key. About the official Krisp API: Krisp has no public REST API (checked 22 Oct 2026): its integrations page answers "Not right now". It offers an official MCP server and a Webhook API on the Core and Advanced plans. Setup and FAQ: https://cotlet.dev/integrations/krisp-api-mcp-server
Otter.ai MCP server for ChatGPT, Claude and any AI agent: search transcripts, export transcript, share conversation, add highlight, upload audio and list action items in your own Otter.ai account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to Otter.ai yourself; Cotlet does not store your password and you need no Otter.ai API key. About the official Otter.ai API: Yes, but narrowly (checked 16 Oct 2026). Otter.ai has an official hosted MCP server with three tools (user info, search, fetch) that only read, and a public REST API available to Enterprise workspaces that reads conversations, transcripts, action items, insights, outlines, audio, channels and the workspace, and imports a recording from a file URL. Setup and FAQ: https://cotlet.dev/integrations/otter-api-mcp-server
Real-time YouTube transcripts, comments, channels & video search MCP. Local npx or hosted OAuth.
MCP server for RiverScript, an AI transcription platform - fetches transcripts shared via a link.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables local MCP clients to interact with xAI Grok through OAuth PKCE, supporting chat, X search, image/video generation, TTS, and transcription.97 npm3MIT
- FlicenseNot gradedqualityDmaintenanceAutomates Grok web interface to provide chat, web search, and conversation management via MCP, supporting multiple accounts and local/remote deployment.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-compatible agents like ChatGPT and Claude to securely access a Grok Bot workstation's folder-scoped files, shell, and Git tools over HTTPS+OAuth or local stdio, and to orchestrate specialized Grok Bot agents via a message bridge.1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to join online meetings as a silent guest, record audio locally, generate transcripts with timestamps via faster-whisper, and manage recordings through MCP tools.6MIT