Mesakem guides
An AI meeting agent that keeps working after the conversation
Mesakem joins supported Zoom, Microsoft Teams and Google Meet sessions as a visible participant, documents the conversation and creates a reviewable action summary. Instead of choosing between listening and typing, the team gets context, decisions, tasks, owners and unresolved questions after the meeting.
What is an AI meeting agent?
An AI meeting agent is software that joins a supported meeting as a participant, captures the conversation and turns it into useful work. Mesakem's agent is visible, remains subject to host admission, and produces a transcript plus a summary organized around decisions, tasks, owners and open questions.
Bring the agent into the meeting you already scheduled
The meeting remains on Zoom, Teams or Google Meet.
Connect a supported Google or Microsoft calendar, add Mesakem to an event, or provide a supported meeting link through the dashboard. Platform admission controls still apply, and the host decides whether the bot enters.
A visible meeting agent is not permission to record secretly. Teams remain responsible for participant notice, consent and internal policy requirements that apply to their use.
- Zoom, Microsoft Teams and Google Meet
- Calendar, event invite or dashboard link workflow
- Visible participant identity
- Host-controlled admission and removal
Preserve a source that can be checked
The transcript provides context when the short version is not enough.
The agent documents the conversation and creates a transcript that supports later verification. Existing recordings can also be processed through manual upload, but that separate path should not be confused with a live participant.
For important decisions, review names, figures, dates, specialist terms and commitments against the available source before wider sharing or action.
- Detailed conversation record
- Manual upload as a separate source
- Verification of sensitive facts
- No perfect-accuracy guarantee
Turn the record into an action summary
A meeting agent should do more than return a wall of text.
Mesakem separates the purpose and key topics from decisions that were actually made. It presents follow-up actions with owners and due dates when they were stated, while preserving unresolved questions and blockers.
Summary templates allow different emphasis for sales, client work, leadership, product, engineering or recurring team sessions.
- Executive context
- Decisions separated from ideas
- Tasks and owners
- Open questions and dependencies
- Templates for recurring meeting types
Continue from the dashboard, email or Telegram
Follow-up should not disappear into a one-time document.
The result remains in the Mesakem dashboard and can be delivered to configured, verified email recipients. The personal Telegram agent supports meeting answers, tasks, status updates and reminders from a linked phone workflow.
Telegram actions are scoped to the linked user's workspace and account context. Meeting content remains untrusted information; it does not independently authorize actions or bypass user permissions.
- Dashboard meeting history
- Verified email delivery
- Telegram meeting answers and tasks
- Telegram reminders and status updates
- Permission-scoped user context
Ask Claude or Codex about the results through MCP
Mesakem has a documented read-only MCP implementation. Confirm availability for your account and environment before following the configuration steps.
In the documented configuration, after signing in through Mesakem, a user can connect Claude or Codex and ask about summarized meetings, decisions, search results and meeting-derived tasks. The four connector tools are read-only and stay within the signed-in user's Mesakem access.
The connector does not expose audio, video or full meeting transcripts. A public REST API and outbound customer webhooks remain roadmap items and should not be represented as currently available.
- Read-only MCP for Claude and Codex
- Summaries, decisions, search and meeting-derived tasks
- No audio, video or full transcripts through MCP
- Public REST API and outbound webhooks: roadmap
Questions and answers
Which meeting platforms does the Mesakem agent support?
The visible live-meeting workflow supports Zoom, Microsoft Teams and Google Meet, subject to host and organization admission policies.
Is the agent visible to participants?
Yes. Mesakem uses a visible-participant workflow and remains under the host's admission and removal controls.
What do I receive after the meeting?
You receive a detailed source record and a shorter summary organized around context, decisions, tasks, owners and open questions.
Can the Telegram agent manage follow-up?
The linked Telegram experience supports meeting answers, task creation and updates, status changes and reminders from the user's scoped workspace context.
Can Claude or Codex access my meeting audio?
Not through Mesakem's MCP connector. That connector exposes read-only summary, decision, search and meeting-derived task tools, not audio, video or full transcripts.
Stay in the conversation and keep the outcome
Invite Mesakem to a supported meeting, keep admission transparent and review the resulting decisions and tasks before sharing.
Get started