AI AGENTS AND MCP

Bring your meetings into the agents you already use.

Livi is AI native, so Claude, ChatGPT, Codex, and any compatible MCP client can work with your meetings on day one. Search what was said, find the work that is still open, and keep the next meeting moving.

Production MCP endpointhttps://livingmeeting.com/api/mcp

OAuth 2.0

What action items are still open from our recent project meetings?Find the meeting where we decided on the launch date and summarize that decision.Create a project update meeting next Tuesday with risks, milestones, and owners on the agenda.

WHAT YOUR AGENT CAN DO

Useful context in. Real meeting work out.

Find the conversation

Search meeting titles, tags, and saved transcript text, then open the exact agenda, summary, or artifact you need.

Understand what changed

Keep speaker attribution intact and separate decisions, open questions, and action items from the rest of the conversation.

Keep the work moving

Create a meeting, update its time, or revise its agenda when you ask. Read and write tools stay clearly separated.

CONNECT ONCE

Your workspace stays yours.

Add LivingMeeting. Choose it from your AI client's app directory, or add the production MCP endpoint as a custom connection.

Approve access. Sign in to LivingMeeting and approve the workspace shown on the consent screen.

Ask naturally. The agent selects a read tool or shows the change it intends to make.

Project configuration

Claude Code and Codex can load the same remote server from a checked-in MCP configuration.

{
  "mcpServers": {
    "livingmeeting": {
      "type": "http",
      "url": "https://livingmeeting.com/api/mcp"
    }
  }
}

THE SAME MEETING, WHEREVER YOU WORK

The agent sees the record your team made together.

MCP exposes saved workspace data, not a hidden audio feed. Live audio remains inside the meeting experience and saved transcript entries become available through authenticated tools.

A LivingMeeting room with participants, agenda, and shared work

FULL TOOL SET

Clear reads. Deliberate changes.

Every request is authenticated and scoped to the workspace you approved.

ToolPurposeAccess

list_meetingsBrowse recent meetings by status or projectRead

get_meetingOpen a meeting with its agenda, people, and action itemsRead

get_agendaRead agenda topics, completion state, and summariesRead

get_transcriptRead saved transcript lines with speaker namesRead

get_summaryRead topic summaries and accepted action itemsRead

search_meetingsFind meetings by title, tag, or transcript textRead

get_artifactsRead charts, notes, and filled meeting templatesRead

list_action_itemsReview open or completed work across meetingsRead

list_pinned_itemsRead items saved to the workspace libraryRead

create_meetingCreate a scheduled LivingMeeting recordWrite

update_meetingChange a meeting title or scheduled timeWrite

set_agendaReplace a meeting agenda with an updated listWrite

delete_meetingPermanently delete a meetingDelete

PERMISSIONS AND PRIVACY

You stay in control.

Workspace scoped. The connection cannot read a different LivingMeeting workspace.
Explicit write tools. Creating, changing, or deleting data uses a separate tool call from reading it.
No password sharing. OAuth connects your account without putting a LivingMeeting password in a prompt or config file.
Revocable. Disconnect the integration or rotate a workspace API key from LivingMeeting settings.

Questions

Do I need an API key?

No for supported app and connector flows. Sign in through OAuth. Workspace API keys remain available for manual development setups that need them.

Can an agent hear live meeting audio?

No. The MCP server exposes the saved meeting record. It does not provide a hidden live audio stream.

Can an agent change or delete meetings?

Yes, through clearly separate write and delete tools. LivingMeeting performs a change only when the client calls the matching tool for your authenticated workspace.