Connect Meeting.ai through MCP

Connect your assistant to Meeting.ai through its hosted MCP server. You need a Meeting.ai account with at least one workspace.

Server details

Use this MCP endpoint:

https://mcp.meeting.ai/mcp

The server uses Streamable HTTP and browser-based OAuth 2.1. There is no API key to paste. Use the URL above in your client, then sign in to Meeting.ai and approve access to a workspace.

Chat assistants

Claude

Open Customize › Connectors › + › Add custom connector, paste the server URL, and add it. Select Connect to sign in. On Team and Enterprise plans, an owner first adds the URL under Organization settings › Connectors; members then connect their own accounts. Claude's connector guide has the current screens.

ChatGPT

Enable developer mode, then open Settings › Apps › Create (or Workspace settings › Apps › Create if you manage the workspace). Paste the URL, choose OAuth, and select Scan Tools. Complete the Meeting.ai sign-in, create the app, and select it in a chat. Plan and admin permissions affect who can create a custom app and whether it can use write actions. See ChatGPT's custom app guide.

Grok Bot

Open grok.com/connectors, choose New Connector › Custom, paste the URL, and sign in. A Grok Business or Enterprise admin must provision the connector before team members can connect. See Grok's connector guide.

Personal and coding agents

OpenClaw

Save the server as Streamable HTTP with OAuth, then log in:

openclaw mcp set meeting-ai '{"url":"https://mcp.meeting.ai/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login meeting-ai

See OpenClaw's MCP OAuth guide.

Hermes Agent

Add this entry to ~/.hermes/config.yaml, then run hermes mcp login meeting-ai in a terminal:

mcp_servers:
  meeting-ai:
    url: "https://mcp.meeting.ai/mcp"
    auth: oauth

See Hermes Agent's MCP guide.

Claude Code

claude mcp add --transport http meeting-ai https://mcp.meeting.ai/mcp

Run /mcp inside Claude Code, select meeting-ai, and authenticate in the browser. See Claude Code's MCP guide.

Cursor

Add this remote server to ~/.cursor/mcp.json (or your project's .cursor/mcp.json), then complete OAuth when Cursor prompts:

{"mcpServers":{"meeting-ai":{"url":"https://mcp.meeting.ai/mcp"}}}

See Cursor's MCP guide.

OpenCode

Add the server to opencode.json, then run opencode mcp auth meeting-ai:

{"mcp":{"meeting-ai":{"type":"remote","url":"https://mcp.meeting.ai/mcp"}}}

See OpenCode's MCP guide.

What the connection can do

The consent screen is the source of truth for access. It explains that the assistant can work with meetings, notes, transcripts, contacts, Drive files, and workspaces. It can also create or update meeting content, export files, and generate Visual Notes, images, or audio. Some operations may use Coins.

Tools use the connection's active workspace by default. The assistant can list and switch to another workspace that your Meeting.ai account can access. If you select Deny, no connection is created; start again from the assistant.

Manage or revoke access

Open Meeting.ai and go to Settings › MCP & CLI. Under Connected MCP Client, you can see the connected app, its active workspace, when it connected, and when it was last used.

Select Revoke to disconnect it. Revocation takes effect immediately, so the next tool call is refused. Start the OAuth connection again if you want to restore access later.

Browse the Meeting.ai MCP repository on GitHub for the server and its source documentation.