CapyAgent Meet MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WHISPER_MODEL | No | faster-whisper model to use for transcription. | small |
| CAPY_MEET_HOME | No | Where recordings are stored: recordings/<id>/ | ~/.capy-meet |
| WHISPER_DEVICE | No | Device to use for transcription (e.g. cpu or cuda). | cpu |
| WHISPER_LANGUAGE | No | Language for transcription. If unset, it is detected automatically. | |
| CAPY_MEET_NO_SCOPE | No | Set to 1 to disable running each recording in its own systemd scope. | |
| MAX_MEETING_SECONDS | No | Maximum recording length in seconds. | 21600 |
| WHISPER_COMPUTE_TYPE | No | Compute type for faster-whisper. | int8 |
| CAPY_MEET_DISPLAY_NAME | No | The bot's display name in a meeting, if not provided at call time. | Запись встречи |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| join_meetingA | Зайти в онлайн-встречу молча (микрофон и камера выключены) и начать запись. |
| meeting_statusB | Состояние записи: в звонке ли бот, растёт ли файл, есть ли звук в последних 20 секундах, сколько минут записано, идёт ли расшифровка. |
| leave_meetingA | Выйти из встречи, закончить запись и запустить локальную расшифровку. Расшифровка идёт в фоне; готовый текст отдаёт get_transcript. |
| get_transcriptB | Расшифровка встречи с таймкодами [ЧЧ:ММ:СС] и путь к WAV. Длинный текст отдаётся частями: следующий кусок с offset=next_offset. |
| list_meetingsC | Последние записи: id, платформа, ссылка, когда, фаза, длительность. |
| transcribe_recordingA | Заново расшифровать готовую запись: если расшифровка упала или процесс записи умер, а WAV остался. Идёт в фоне, результат в get_transcript. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool maps to a clear lifecycle action: joining, checking status, leaving, listing, and fetching transcripts. There is slight overlap between transcribe_recording and leave_meeting since both can trigger transcription, but the descriptions distinguish a normal finish from a retry after failure.
Most tools follow a clear verb_noun pattern: join_meeting, leave_meeting, get_transcript, list_meetings, transcribe_recording. meeting_status breaks the pattern by using a noun phrase instead of an imperative verb, creating a minor inconsistency.
Six tools is well-scoped for a meeting recording and transcription server. Each tool serves a necessary function without redundancy or bloat.
The toolset covers the full workflow: join a meeting, monitor recording status, leave and trigger transcription, retrieve transcripts, list past meetings, and re-transcribe failed recordings. There are no obvious dead ends for the stated purpose.