Connect an 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/mcpThe server uses Streamable HTTP and OAuth 2.1. Compatible clients discover the Meeting.ai authorization server, open the browser, and complete an authorization-code flow with PKCE.
The access token only works with Meeting.ai MCP tools.
Connect an assistant
- Add a custom connector or remote MCP server in Claude, ChatGPT, or another MCP-compatible client.
- Enter the endpoint above and start the connection.
- Sign in to Meeting.ai in the browser if you are not already signed in.
- Review the consent screen, choose the workspace the connection should start in, and select Allow access.
- Return to the assistant. It can now list its available Meeting.ai tools.
If you select Deny, no connection is created. An expired or invalid request must be started again from the assistant.
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.
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.