MCP server
Connect an MCP-compatible AI assistant to a running Meetily desktop app: tools, resources, prompts, and the security model behind them.
meetily:// is not meetilypro://
The MCP resource scheme meetily:// (meetily://meetings, meetily://meeting/{id}, and so on) is unrelated to meetilypro://, the OS-level deep-link scheme gated by its own deeplink_enabled setting. Don't conflate the two - one addresses MCP resources inside a running server, the other is a system link handler.
meetily-pro mcp runs a local stdio Model Context Protocol server that lets an MCP-compatible assistant (Claude Desktop, Claude Code, Cursor, and similar clients) drive a running Meetily desktop app: read meetings and transcripts, control recording, manage summaries and jobs, and more.
It is a thin wrapper around the same Gateway HTTP API the meetily-pro CLI uses - see meetily-pro CLI. It never touches the database directly, so it inherits the Gateway's Pro license gate and per-route scopes for free.
Requirements
The Meetily desktop app must be running with Integrations enabled before tools can reach the Gateway on loopback (127.0.0.1:8420). Follow Enable & connect, then use the AI Assistants (MCP) panel in Settings > Integrations to register an assistant, choose its permissions, mint its token, and write its client configuration.
If the app isn't running, tools/list still works from the committed embedded catalog, but tool calls return a clear "Gateway unreachable" error instead of hanging.
meetily-pro mcp install is different: it is an offline handoff, not an installer. It contacts no Gateway, mints no token, and writes no client configuration. It prints a configuration template and directions for completing the connection in the app.
Check your assistant's data handling
The MCP server gives your assistant access to meeting content, and the assistant may send transcripts and summaries it reads to its own AI provider. Connect only an assistant you trust with your meetings, and check that provider's privacy policy before granting access.
Quick start
Turn on the Automation API in Settings > Integrations. If this is your first time, follow Enable & connect to turn on Integrations.
Open AI Assistants (MCP), choose Connect beside your detected assistant, select its permissions, then choose Connect in the sheet.
Turn on Allow for the newly connected assistant in the AI Assistants (MCP) list, then restart the assistant so it loads the connection.
If a tool call fails, check that Automation API and the assistant's Allow switch are on, then restart the assistant.
What it exposes
Tools
The server builds its tool catalog from a committed embedded OpenAPI snapshot plus the authored TOOL_META catalog. It exposes exactly 33 tools: 15 ordinary read views, 16 mutation tools, and 2 bounded waits. By authorization floor, that is 20 Read-scoped, 9 Write-scoped, and 4 Record-scoped tools. The 5 webhook tools are gated off by default, leaving 28; app-managed connections do not enable them. Token scopes and serve flags further filter the list.
Get the exact session list from tools/list
tools/list shows the tools available to this assistant with its permissions; it is authoritative for the current session.
Representative tools by category:
whoami, list_meetings, get_meeting, get_transcript, get_summary, export_meeting, search_transcripts, get_config, list_jobs, get_job, list_devices, list_models, get_recording_state, list_webhooks, list_webhook_deliveries.
rename_meeting, set_summary, regenerate_summary, set_speaker_labels, submit_diarization, cancel_job, pause_job, resume_job, retry_job, start_recording, stop_recording, pause_recording, resume_recording.
wait_for_job, wait_for_recording - each resolves on the underlying event or a bounded timeout (default 30s, capped at 600s), so neither one blocks open-ended.
The webhook tools (list_webhooks, list_webhook_deliveries, create_webhook, delete_webhook, test_webhook) are hidden unless --allow-webhooks is set for a manually configured MCP launch. The flag only enables otherwise eligible tools; it cannot override token scopes or --read-only. App-managed connections do not enable webhook tools.
A newly connected assistant defaults to read only
Read is always on in the app's connection sheet. Record, Write, and Delete are separate opt-in permissions. The token minted by the app determines which eligible tools appear.
Destructive deletes are never tools
Meeting deletion is excluded from the MCP catalog, and pairing revocation has no Gateway route. delete_webhook is available when webhook tools are enabled because it removes only a caller-owned subscription; it is not a Delete-scoped meeting operation. Each registered tool also carries MCP annotation hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint).
Read-only and degraded modes
meetily-pro mcp --read-only--read-only is enforced twice: mutation tools are hidden from tools/list, and calls to them are refused by ID. Token scopes filter the list independently.
If the startup scope probe is degraded, the server advertises the Read-scoped surface rather than treating every operation as read-only. With --allow-webhooks, Read-scoped webhook mutations can therefore appear; the Gateway remains authoritative when a call is made.
Resources
URI-addressable read views under the meetily:// scheme:
meetily://meetings- all meetingsmeetily://meeting/{id}meetily://transcript/{id}meetily://summary/{id}
Prompts
Two built-in prompts, each taking a meeting_id and referencing that meeting's transcript resource:
summarize_meetingextract_action_items
Commands
| Command | What it does |
|---|---|
meetily-pro mcp | Serve over stdio, filtered by the resolved token's scopes. |
meetily-pro mcp --read-only | Additionally hide mutation tools from tools/list and refuse them at call time. |
meetily-pro mcp --allow-webhooks | Enable eligible webhook tools for a manually configured MCP launch; app-managed connections do not offer them. |
meetily-pro mcp install [--config <path>] [--name <name>] [--record] [--write] | Print an offline configuration handoff; it mints no credential and writes no client configuration. --config, --record, and --write are accepted but inert; --name changes only the printed template key. |
meetily-pro mcp doctor | Probe the Gateway with the CLI's resolved credential and report reachability, license tier, and scopes. A bare invocation does not diagnose the app-managed assistant's separate token. |
Security model
- The server reaches meeting data only through Gateway HTTP routes, so it inherits the Pro license gate and per-route scopes rather than re-implementing either.
tools/listis filtered to the resolved token's scopes; a degraded scope probe fails safe to the Read-scoped surface.--read-onlyis enforced in both places that matter: what's advertised intools/list, and what's allowed when a tool is called.--allow-webhooksonly removes the extra webhook gate. It cannot grant a scope or bypass--read-only.
Last updated on