Meeting recording
Record meetings from Chrome and store them in your profile or a project, with permissions, clips and 30-day deletion.
- Category: Meetings and productivity
- Status: Available
- Requirements: The ArduMaker Meetings Chrome extension, linked to the account; ArduMaker Meetings enabled for the account or company; To save into a project: level
aportarin the Recordings section - MCP tools (Read only):
listar_grabaciones,ver_grabacion,ver_fotograma_grabacion,ver_recorte_grabacion - MCP tools (Write or modify):
editar_grabacion,crear_recorte_grabacion - MCP tools (Destructive):
eliminar_grabacion,mover_grabacion,eliminar_recorte_grabacion
What can you do with it?
The Chrome extension records the meeting (audio and, when possible, video) and uploads it to ArduMaker, where it is stored, rebuilt, transcribed and summarized. It is not a calendar meeting: it is the recording.
- Store each recording in the private profile or in a project.
- Rename it, move it between profile and projects, or delete it.
- Play it and see which audio and video ranges really exist.
- Request clips in MP4 or MP3: a section, removed parts, zoom or pixelated areas.
When should you use it?
- To not depend on someone's notes after a client call.
- To record a tutorial (
tutorialmode) and keep it as project context.
How does it work in ArduMaker?
- The extension is linked to the account from the web with a narrow permission: it only sees destinations and uploads recordings; it does not read tasks, files or payments.
- When starting, the recorder declares having informed the participants; without that declaration the recording is not created.
- Uploading is chunked and resumable. Repeating a part with the same content succeeds; with different content, it is rejected.
- When sealed, a separate process rebuilds it, verifying each part, and queues it for transcription.
| State | Values |
|---|---|
capture_state | recording, ended, interrupted |
upload_state | pending, partial, complete, blocked |
processing_state | waiting, processing, ready, failed, blocked |
Finishing recording is not the same as finishing uploading or being transcribed: they are three separate states.
What actually changes?
- Moving a recording does not copy it: it keeps its id, media and transcript, and from then on the destination's permissions apply. It is recorded in each project's history.
- Deleting it removes it from everywhere at once; its media, transcript and summary are purged after 30 days.
- Clips expire after 7 days and are deleted along with their file.
Diagram
- Chrome extension: records and uploads in parts
- Sealing: manifest of what was recorded
- Recording worker: rebuilds each track
- Transcript and summary: with the company's AI key
- Ready: playback, search and clips
Expected result
The recording appears in the profile's or project's recordings, with its duration, states, audio and video coverage and, once ready, its transcript and summary.
Errors and troubleshooting
| Type | Cause |
|---|---|
meetings_not_enabled | ArduMaker Meetings is not enabled for that account. |
consent_required | Informing the participants was not declared. |
meeting_not_found | It does not exist, was deleted or cannot be seen (all three respond the same). |
meeting_forbidden | It can be seen but not managed. |
cross_company | A move was attempted between projects that share no company. |
- If you cannot jump to a minute, the recording was rebuilt without the server's video tool: it plays straight through.
- Whoever created a project recording has no special privilege: losing the role means losing the recording.
MCP access
An MCP agent sees and manages recordings of the projects in its scope and its owner's private profile, but never creates a recording or sees another person's profile.
- Read:
listar_grabaciones,ver_grabacion,ver_fotograma_grabacionandver_recorte_grabacion. - Write:
editar_grabacionandcrear_recorte_grabacion(simulates first withconfirmar=False). - Destructive:
mover_grabacion(changes who sees it; shows the audience first),eliminar_grabacionandeliminar_recorte_grabacion. The first two require explicit confirmation.
Full reference for each tool: /mcp/docs.