AI Assistants (MCP)
Connect Claude Desktop, Claude Code, Cursor, or any MCP client to Meetily.
The Model Context Protocol (MCP) lets an AI client like Claude Desktop, Claude Code, or Cursor drive Meetily directly: read meetings and transcripts, control recording, manage summaries and jobs. meetily-pro mcp is a small local server that talks over stdio and wraps the same gateway HTTP API used by every other Agent API client, so it inherits the Pro license gate and the same per-route scopes.
The Meetily app must be running with Integrations enabled so the gateway is up. If the app is not running, the tool list still loads from a built-in manifest, so your client can still see and describe every tool, but each tool call returns a clear "gateway unreachable" error instead of hanging.
What it exposes
The server registers 34 tools in total. By default it advertises 29 of them; the 5 webhook tools are gated behind a flag and stay hidden unless you turn it on. It never registers a tool that deletes a meeting or a pairing, no matter how it's configured. See the tools, resources and prompts, and security pages for the full picture.
Install and connect
Register the server with your MCP client and verify the connection.
Tools
The full list of tools the server registers, by scope.
Resources and prompts
MCP resources and prompt templates exposed alongside the tools.
Security
Scopes, tokens, and what the server refuses to do.
Reads and summarizes, never deletes
A connected assistant can read your meetings and transcripts and write summaries, but the destructive delete operations are never exposed as tools, on any config.
The one-command CLI install is the least-privilege way to connect: it mints a scoped per-client token, Read and Record by default (add --write for Write, never Delete or Admin), and stores it with restrictive permissions. See Limitations and roadmap for what that means. The in-app Integrations panel is an alternative that can additionally grant Delete.
Last updated on