MCP (Model Context Protocol)
Let an AI assistant like Claude work directly with your meetings, safely and on your machine.
The Model Context Protocol (MCP) is the standard an AI assistant uses to reach tools and data. Meetily ships a local MCP server, so an assistant like Claude Desktop, Claude Code, or Cursor can work with your meetings directly: read transcripts and summaries, control recording, and run jobs. Everything stays on your machine.
Instead of copy-pasting a transcript into a chat, your assistant reads the meeting itself, and only with the permissions you grant.
Connect in one command
meetily-pro mcp installThen restart your AI client. That registers meetily-pro mcp (a small local stdio server that wraps the same gateway API) with your client, without touching any other server you already have.
Reads and summarizes, never deletes
A connected assistant can read your meetings and write summaries, control recording, and run jobs. It can never delete a meeting or a pairing: those are not exposed as tools, in any configuration.
Open the guide
In this section
Install and connect
Register the server with your MCP client and verify the connection.
Tools
The 34 tools the server registers, by scope (29 shown by default).
Resources and prompts
The meetily:// resources and the canned prompt templates.
Security
Scopes, tokens, read-only mode, and what the server refuses to do.
The one-command install is already the scoped, least-privilege path: it mints a per-client token limited to Read and Record by default (add --write for Write, never Delete or Admin), and your client config never sees the loopback admin token. The in-app Integrations panel is an alternative that can additionally grant Delete. See Limitations and roadmap.
Last updated on