dialogbrain
Server Details
Unified inbox MCP for WhatsApp, Telegram, Email, voice — read/send messages, search, AI agents.
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- saloprj/dialogbrain-mcp
- GitHub Stars
- 0
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
232 tool updates
- Removed
agent_handoff - Removed
agent_silence - Removed
agents_activity - Removed
agents_add_file - Removed
agents_approve_draft - Removed
agents_ask - Removed
agents_create - Removed
agents_delete - Removed
agents_get - Removed
agents_list - Removed
agents_list_drafts - Removed
agents_list_files - Removed
agents_list_integrations - Removed
agents_prompt_history - Removed
agents_prompt_restore - Removed
agents_reject_draft - Removed
agents_remove_file - Removed
agents_set_integration - Removed
agents_simulate_inbound - Removed
agents_task_complete - Removed
agents_trace_get - Removed
agents_traces_list - Removed
agents_traces_stats - Removed
agents_trigger_create - Removed
agents_trigger_delete - Removed
agents_trigger_update - Removed
agents_update - Removed
agents_update_from_template - Removed
ai_filters_create - Removed
ai_filters_delete - Removed
ai_filters_list - Removed
ai_filters_test - Removed
ai_filters_update - Removed
ai_tags_add_to_thread - Removed
ai_tags_create - Removed
ai_tags_delete - Removed
ai_tags_list - Removed
ai_tags_remove_from_thread - Removed
ai_tags_update - Removed
analytics_query - Removed
android_close_app - Removed
android_current_app - Removed
android_install_apk - Removed
android_key - Removed
android_launch_app - Removed
android_list_apps - Removed
android_screenshot - Removed
android_shell - Removed
android_swipe - Removed
android_tap - Removed
android_type - Removed
android_ui_dump - Removed
artifacts_create - Removed
artifacts_export_pdf - Removed
artifacts_get - Removed
artifacts_list - Removed
artifacts_refresh - Removed
artifacts_set_access - Removed
artifacts_update - Removed
background_run - Removed
browser_attach_identity - Removed
browser_attach_meet - Removed
browser_click - Removed
browser_close - Removed
browser_console_messages - Removed
browser_drag - Removed
browser_evaluate - Removed
browser_file_upload - Removed
browser_fill - Removed
browser_fill_form - Removed
browser_handle_dialog - Removed
browser_hover - Removed
browser_navigate_back - Removed
browser_network_requests - Removed
browser_open - Removed
browser_press_key - Removed
browser_resize - Removed
browser_select_option - Removed
browser_snapshot - Removed
browser_tabs - Removed
browser_take_screenshot - Removed
browser_type - Removed
browser_wait_for - Removed
calendar_check_availability - Removed
calendar_create_event - Removed
calendar_delete_event - Removed
calendar_list_events - Removed
calendar_update_event - Removed
calls_agent_duel - Removed
calls_dispatch_translator - Removed
calls_get_transcript - Removed
calls_hangup - Removed
calls_list_active - Removed
calls_list_history - Removed
calls_make - Removed
calls_meet_browser - Removed
calls_mute_translation_tts - Removed
calls_send_to_meet - Removed
calls_send_to_telegram_call - Removed
calls_set_translation_language - Removed
calls_set_translation_languages - Removed
calls_wait - Removed
channels_connect_telegram_bot - Removed
collections_add_file - Removed
collections_assign_agent - Removed
collections_create - Removed
collections_delete - Removed
collections_list - Removed
collections_list_files - Removed
collections_remove_file - Removed
collections_unassign_agent - Removed
contacts_add_channel - Removed
contacts_capture_lead - Removed
contacts_discover - Removed
contacts_find - Removed
contacts_profile - Removed
contacts_research - Removed
contacts_sync - Removed
contacts_update - Removed
documents_create - Removed
feedback_save - Removed
files_delete - Removed
files_get_base64 - Removed
files_info - Removed
files_ingest - Removed
files_read - Removed
files_upload - Removed
folders_create - Removed
folders_delete - Removed
group_add - Removed
group_add_member - Removed
group_admins - Removed
group_create - Removed
group_get_invite_link - Removed
group_join - Removed
group_leave - Removed
group_list - Removed
group_preview_messages - Removed
group_promote_admin - Removed
group_scan - Removed
group_search - Removed
images_generate - Removed
images_search - Removed
instagram_list_media - Removed
instagram_publish_media - Removed
instagram_update_media - Removed
integrations_add_endpoints - Removed
integrations_capture_session - Removed
integrations_get_endpoints - Removed
integrations_list - Removed
integrations_remove_endpoints - Removed
integrations_set_auth - Removed
job_complete - Removed
job_escalate - Removed
job_read_context - Removed
job_update_context - Removed
kg_find_entity - Removed
kg_get_relationships - Removed
knowledge_query - Removed
linkedin_add_comment - Removed
linkedin_get_company - Removed
linkedin_get_profile - Removed
linkedin_invite - Removed
linkedin_list_connections - Removed
linkedin_list_invitations_sent - Removed
linkedin_list_reactions - Removed
linkedin_raw_request - Removed
linkedin_search - Removed
linkedin_search_filters - Removed
linkedin_update_profile - Removed
messages_delete - Removed
messages_edit - Removed
messages_forward - Removed
messages_read_history - Removed
messages_send - Removed
messages_send_email - Removed
notes_delete - Removed
notes_recall - Removed
notes_save - Removed
notes_search - Removed
owners_add - Removed
owners_list - Removed
owners_remove - Removed
present_status - Removed
present_tab - Removed
prompts_get - Removed
prompts_list - Removed
prompts_prompt_history - Removed
prompts_prompt_restore - Removed
prompts_update - Removed
reminder_cancel - Removed
reminder_list - Removed
reminder_set - Removed
search_files - Removed
search_links - Removed
search_messages - Removed
search_threads - Removed
system_sleep - Removed
tasks_create - Removed
tasks_delete - Removed
tasks_list - Removed
tasks_update - Removed
threads_delete - Removed
threads_update - Removed
videos_generate - Removed
vision_query - Removed
web__local_search - Removed
web_fetch - Removed
web_research - Removed
web_search - Removed
webhooks_configure_enrichment - Removed
widgets_create - Removed
widgets_delete - Removed
widgets_get - Removed
widgets_get_embed_code - Removed
widgets_list - Removed
widgets_update - Removed
workbench_run_python - Removed
workspace_current - Removed
workspace_list - Removed
workspace_switch - Removed
workspace_update - Removed
x_publish_post - Removed
youtube_delete_comment - Removed
youtube_delete_video - Removed
youtube_list_comments - Removed
youtube_list_videos - Removed
youtube_moderate_comment - Removed
youtube_post_comment_reply - Removed
youtube_update_video - Removed
youtube_upload_video - Removed
youtube_video_query
1 tool update
- Changed
agents_update3 fields changed- changed
Input schema / properties / voice_engine / descriptionPrevious value: -"Voice execution engine: 'pipeline' (default — Deepgram/Gladia STT + LLM + TTS) or 'openai_realtime' (OpenAI Realtime API v2v; requires the workspace to have a BYOK OpenAI key connected — the worker falls back to 'pipeline' and logs why if the key is missing). OMIT to leave unchanged."New value: +"Voice execution engine: 'pipeline' (default — Deepgram/Gladia STT + LLM + TTS), 'openai_realtime' (OpenAI Realtime API v2v; requires the workspace to have a BYOK OpenAI key connected — the worker falls back to 'pipeline' and logs why if the key is missing), or 'gemini_realtime' (Gemini 2.0 Flash with real-time API). OMIT to leave unchanged." - changed
Input schema / properties / voice_engine / enumPrevious value: -[ - "pipeline", - "openai_realtime" -]New value: +[ + "pipeline", + "openai_realtime", + "gemini_realtime" +] - added
Input schema / properties / voice_v2v_transcriptsAdded value: +{ + "description": "Enable live transcripts for voice-to-voice engines (default true). OMIT to leave unchanged.", + "type": "boolean" +}
1 tool update
- Changed
agents_update1 field changed- added
Input schema / properties / voice_engineAdded value: +{ + "description": "Voice execution engine: 'pipeline' (default — Deepgram/Gladia STT + LLM + TTS) or 'openai_realtime' (OpenAI Realtime API v2v; requires the workspace to have a BYOK OpenAI key connected — the worker falls back to 'pipeline' and logs why if the key is missing). OMIT to leave unchanged.", + "enum": [ + "pipeline", + "openai_realtime" + ], + "type": "string" +}
1 tool update
- Changed
browser_select_option2 fields changed- changed
Input schema / properties / label / anyOfPrevious value: -[ - { - "type": "string" - }, - { - "items": {}, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } +] - changed
Input schema / properties / value / anyOfPrevious value: -[ - { - "type": "string" - }, - { - "items": {}, - "type": "array" - }, - { - "type": "null" - } -]New value: +[ + { + "type": "string" + }, + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } +]
1 tool update
- Changed
agents_trigger_create1 field changed- changed
Input schema / properties / conditions / descriptionPrevious value: -"Trigger conditions (JSON). Supported fields for incoming_message:\n- keywords: [\"pricing\",\"demo\"] — message must contain keyword(s) (free, no LLM cost)\n- keyword_match: \"any\" (default, OR) or \"all\" (AND)\n- channel_types: [\"telegram\",\"whatsapp\",\"livechat_voice\",\"twilio_voice\",\"telegram_voice\",\"voice\",...] — filter by channel. For voice, use EITHER the three per-channel keys (scoped) OR \"voice\" alone (wildcard matching all three) — mixing them is redundant. Per-channel keys: \"livechat_voice\" (web widget), \"twilio_voice\" (PSTN inbound), \"telegram_voice\" (Telegram p2p calls)\n- context_types: [\"dm\",\"group\",\"channel\",\"livechat\"] — filter by chat type\n- group_mode: \"mentions_only\" or \"questions\" — for group chats\n- channel_account_ids: [\"123\"] — restrict to specific accounts\n- folder_ids: [5,10] — restrict to threads in folders\n- ai_tag_ids: [1,2] — restrict to threads with AI tags\n- ai_filter_ids: [1,2] — semantic intent filters (message matched via embedding similarity, works in noisy groups)\n- ai_filter_mode: \"any\" (default, OR) or \"all\" (AND) — how multiple AI filters combine\n- ai_filters: [{id: 1}, {name: \"...\", description: \"...\"}] — shorthand: reference existing by id or create inline (calls Voyage embedding API). If a filter with the same name already exists, it is reused by id. Prefer referencing existing filters by id when available. Use ai_filters.create + ai_filters.test for fine-tuning before assigning.\n- contact_states: [\"active\"] — filter by contact state\n- cooldown_seconds: 30 — min gap between runs per thread\n- max_runs_per_thread_per_hour: 5 — rate limit\n\nSupported fields for job_completed (proactive callback when a delegated job finishes):\n- source_agent_id: <int> — fire only when this agent's job completed\n- source_agent_slug: <str> — alternate to source_agent_id\n- job_type: \"agentic_session\" — match a specific job type (default: any)\n- outcome: [\"completed\"] | [\"escalated\"] | [\"completed\",\"escalated\"] — default [\"completed\"]\n- min_duration_seconds: <int> — skip very-short jobs (noise filter)\n- thread_filter: {thread_ids: [<int>...]} — restrict to specific threads\n\nSupported fields for calendar_event (fires N minutes before a Google Calendar event starts):\n- window_minutes_before: <int 1-1440> — REQUIRED, fire when an event starts within this window\n- channel_account_ids: [<int>...] — restrict to specific calendar accounts (default: all)\n- keywords: [\"standup\"] — word-boundary match on event title\n- prepare_meet_join: true — pre-invite pool bots to the event (enables unattended Meet join)\n\nGeneric run-mode fields (incoming_message AND calendar_event):\n- run_mode: \"text\" (default, normal agent run) or \"voice\" (deterministically join the meeting/call resolved from the event or message — requires send_mode=auto)\n- voice: {speak_first: <bool — greet immediately vs stay silent until addressed>, vision_mode: \"off\"|\"on_demand\"|\"continuous_0_3fps\"}"New value: +"Trigger conditions (JSON). Supported fields for incoming_message:\n- keywords: [\"pricing\",\"demo\"] — message must contain keyword(s) (free, no LLM cost)\n- keyword_match: \"any\" (default, OR) or \"all\" (AND)\n- channel_types: [\"telegram\",\"whatsapp\",\"livechat_voice\",\"twilio_voice\",\"telegram_voice\",\"voice\",...] — filter by channel. For voice, use EITHER the three per-channel keys (scoped) OR \"voice\" alone (wildcard matching all three) — mixing them is redundant. Per-channel keys: \"livechat_voice\" (web widget), \"twilio_voice\" (PSTN inbound), \"telegram_voice\" (Telegram p2p calls)\n- context_types: [\"dm\",\"group\",\"channel\",\"livechat\"] — filter by chat type\n- group_mode: \"mentions_only\" or \"questions\" — for group chats\n- channel_account_ids: [\"123\"] — restrict to specific accounts\n- folder_ids: [5,10] — restrict to threads in folders\n- ai_tag_ids: [1,2] — restrict to threads with AI tags\n- ai_filter_ids: [1,2] — semantic intent filters (message matched via embedding similarity, works in noisy groups)\n- ai_filter_mode: \"any\" (default, OR) or \"all\" (AND) — how multiple AI filters combine\n- ai_filters: [{id: 1}, {name: \"...\", description: \"...\"}] — shorthand: reference existing by id or create inline (calls Voyage embedding API). If a filter with the same name already exists, it is reused by id. Prefer referencing existing filters by id when available. Use ai_filters.create + ai_filters.test for fine-tuning before assigning.\n- contact_states: [\"active\"] — filter by contact state\n- cooldown_seconds: 30 — min gap between runs per thread\n- max_runs_per_thread_per_hour: 5 — rate limit\n- answer_delay_s: 15 — voice pickup only (incoming_call, or incoming_message scoped to a voice channel). Ring the human's own devices this long before the agent answers; if they pick up, the agent stands down. 0/absent = answer immediately. Honoured on WhatsApp and Telegram 1:1 — other voice channels have nothing ringing to wait for and still answer at once.\n\nSupported fields for job_completed (proactive callback when a delegated job finishes):\n- source_agent_id: <int> — fire only when this agent's job completed\n- source_agent_slug: <str> — alternate to source_agent_id\n- job_type: \"agentic_session\" — match a specific job type (default: any)\n- outcome: [\"completed\"] | [\"escalated\"] | [\"completed\",\"escalated\"] — default [\"completed\"]\n- min_duration_seconds: <int> — skip very-short jobs (noise filter)\n- thread_filter: {thread_ids: [<int>...]} — restrict to specific threads\n\nSupported fields for calendar_event (fires N minutes before a Google Calendar event starts):\n- window_minutes_before: <int 1-1440> — REQUIRED, fire when an event starts within this window\n- channel_account_ids: [<int>...] — restrict to specific calendar accounts (default: all)\n- keywords: [\"standup\"] — word-boundary match on event title\n- prepare_meet_join: true — pre-invite pool bots to the event (enables unattended Meet join)\n\nGeneric run-mode fields (incoming_message AND calendar_event):\n- run_mode: \"text\" (default, normal agent run) or \"voice\" (deterministically join the meeting/call resolved from the event or message — requires send_mode=auto)\n- voice: {speak_first: <bool — greet immediately vs stay silent until addressed>, vision_mode: \"off\"|\"on_demand\"|\"continuous_0_3fps\"}"
1 tool update
- Added
present_status
1 tool update
- Changed
calls_list_history4 fields changed- changed
Input schema / properties / channel / descriptionPrevious value: -"Filter by message-level channel of the call thread: 'telegram' (1:1 voice or group call sub-thread), 'twilio_voice', 'meet_voice', 'livechat_voice'. OMIT to include all voice channels."New value: +"Filter by message-level channel of the call thread: 'telegram' (1:1 voice or group call sub-thread), 'twilio_voice', 'meet_voice', 'livechat_voice', 'whatsapp' (native WhatsApp calls — these coalesce into the contact's messaging thread). OMIT to include all voice channels." - changed
Input schema / properties / channel / enumPrevious value: -[ - "telegram", - "twilio_voice", - "meet_voice", - "livechat_voice" -]New value: +[ + "telegram", + "twilio_voice", + "meet_voice", + "livechat_voice", + "whatsapp" +] - changed
Input schema / properties / source / descriptionPrevious value: -"Filter by voice_sessions.source: 'telegram' (1:1 + group), 'twilio' (PSTN), 'meet' (Google Meet bot), 'livechat' (in-app voice), 'android' (Android device). OMIT to include all sources."New value: +"Filter by voice_sessions.source: 'telegram' (1:1 + group), 'whatsapp' (native WhatsApp voice), 'twilio' (PSTN), 'meet' (Google Meet bot), 'livechat' (in-app voice), 'android' (Android device). OMIT to include all sources." - changed
Input schema / properties / source / enumPrevious value: -[ - "telegram", - "twilio", - "meet", - "livechat", - "android" -]New value: +[ + "telegram", + "twilio", + "meet", + "livechat", + "android", + "whatsapp" +]
5 tool updates
- Changed
agents_create2 fields changed- added
Input schema / properties / prompt_textAdded value: +{ + "description": "Only with `template`: the agent's persona/instructions, stored inline on the agent (drives how it replies). No separate prompts tool needed.", + "type": "string" +} - added
Input schema / properties / templateAdded value: +{ + "description": "Optional template slug to instantiate the agent + its built-in trigger from (deterministic). Use 'dm-auto-reply' for the customer DM auto-reply agent (incoming DM trigger, draft mode). When set, the trigger comes from the template — you don't need agents.trigger_create. OMIT to create a plain agent (no template).", + "enum": [ + "dm-auto-reply" + ], + "type": "string" +}
- Changed
calls_make3 fields changed- changed
Input schema / properties / channel / descriptionPrevious value: -"Voice transport: 'twilio' (phone via PSTN — requires phone_number in E.164) or 'telegram' (MTProto 1:1 call — requires telegram_user_id, NOT a phone number or thread_id) or 'android' (Android device voice call — requires phone_number in E.164). OMIT to use the current conversation's channel (e.g. a Telegram DM → a Telegram call to that contact)."New value: +"Voice transport: 'twilio' (phone via PSTN — requires phone_number in E.164), 'telegram' (MTProto 1:1 call — requires telegram_user_id, NOT a phone number or thread_id), 'maxru' (Max.ru voice call — requires maxru_user_id), 'android' (Android device voice call — requires phone_number in E.164), or 'whatsapp' (WhatsApp Web voice bridge — requires phone_number in E.164; single-tenant dev only). OMIT to auto-select based on the current thread (e.g. inside a Telegram DM → uses 'telegram')." - changed
Input schema / properties / channel / enumPrevious value: -[ - "twilio", - "telegram", - "android" -]New value: +[ + "twilio", + "telegram", + "maxru", + "android", + "whatsapp" +] - added
Input schema / properties / maxru_user_idAdded value: +{ + "description": "Destination Max.ru user/chat ID. Required when channel='maxru'.", + "type": "string" +}
- Added
owners_add - Added
owners_list - Added
owners_remove
6 tool updates
- Added
group_admins - Changed
group_join2 fields changed- removed
Input schema / properties / enable_auto_reply / defaultRemoved value: -true - changed
Input schema / properties / enable_auto_reply / descriptionPrevious value: -"Enable AI auto-reply drafts for messages in this group. Drafts can be reviewed and sent manually. Default: true."New value: +"Enable AI auto-reply drafts for messages in this group. Drafts can be reviewed and sent manually. Default: false (large public groups would otherwise generate drafts for every incoming message)."
- Added
group_leave - Changed
group_preview_messages1 field changed- added
Input schema / properties / full_textAdded value: +{ + "description": "Return untruncated message text. OMIT for 150-char previews (keeps large batches consumable).", + "type": "boolean" +}
- Changed
group_search1 field changed- changed
Input schema / properties / keywords / descriptionPrevious value: -"Search keywords or phrase (e.g. 'crypto trading signals')"New value: +"Search keywords or phrase (e.g. 'crypto trading signals'). A list of keywords is also accepted and joined with spaces."
- Changed
search_threads1 field changed- added
Input schema / properties / offsetAdded value: +{ + "description": "Number of threads to skip (for pagination, default: 0)", + "minimum": 0, + "type": "integer" +}
3 tool updates
- Changed
calls_dispatch_translator3 fields changed- added
Input schema / properties / source_languageAdded value: +{ + "description": "The meeting's spoken language (ISO code, e.g. 'en', 'ru'). When set, speech recognition runs in that language's dedicated mode for better accuracy. Omit when participants may speak multiple languages (autodetect). Google Meet + native meetings.", + "type": "string" +} - added
Input schema / properties / tts_providerAdded value: +{ + "description": "Translator VOICE provider (cartesia, openai, yandex, deepgram, ...). Omit for the workspace default translation voice. Google Meet + native new meetings.", + "type": "string" +} - added
Input schema / properties / tts_voiceAdded value: +{ + "description": "Specific voice id for tts_provider (e.g. 'alena', 'nova'). Omit for the provider default.", + "type": "string" +}
- Changed
calls_send_to_meet3 fields changed- added
Input schema / properties / source_languageAdded value: +{ + "description": "Spoken language of the meeting itself (any ISO code, e.g. 'en', 'ru', 'zh'). When set, speech recognition runs in that language's dedicated mode for better accuracy. OMIT when participants may speak multiple languages — recognition then autodetects. Independent of translation_mode; improves plain transcription too.", + "type": "string" +} - added
Input schema / properties / tts_providerAdded value: +{ + "description": "Translator VOICE provider (the TTS the translator speaks with): cartesia, openai, yandex, deepgram, ... Only with translation_mode=true. OMIT for the workspace default translation voice.", + "type": "string" +} - added
Input schema / properties / tts_voiceAdded value: +{ + "description": "Specific voice id for tts_provider (e.g. 'alena' for yandex, 'nova' for openai). OMIT for the provider's default voice.", + "type": "string" +}
- Added
workspace_update
1 tool update
- Changed
agents_update4 fields changed- changed
Input schema / properties / voice_stt_language / descriptionPrevious value: -"STT language hint. 'multi' (default) enables code-switching; singletons like 'en', 'ru', 'es' give higher accuracy when the caller language is known. Use 'multi' for bilingual callers. IMPORTANT: 'en' runs on Flux (fastest, eager end-of-turn); 'multi' and every other language run on Nova-3 (slightly slower, no eager EOT). Some languages — notably Thai ('th'), Vietnamese ('vi'), Indonesian ('id'), Tagalog ('tl') — are NOT in Nova-3's 'multi' auto-detect set, so a Thai/Vietnamese/etc. caller MUST be given the explicit language code here (e.g. 'th') or transcription is garbage. OMIT to leave the STT language unchanged."New value: +"STT language code, validated against the SELECTED voice_stt_provider. 'multi' (default) enables autodetect / code-switching on either provider; a singleton like 'en', 'ru', 'uz' gives higher accuracy when the caller language is known. Deepgram provider: 'en' runs on Flux (fastest, eager end-of-turn); 'multi' and every other language run on Nova-3. Some languages — notably Thai ('th'), Vietnamese ('vi'), Indonesian ('id'), Tagalog ('tl') — are NOT in Nova-3's 'multi' auto-detect set, so those callers MUST be given an explicit code. Gladia provider: use its codes (e.g. 'uz' Uzbek, 'kk' Kazakh, 'az' Azerbaijani, 'tg' Tajik) — these are NOT valid under Deepgram. The enum below lists the union of both providers' codes; a code invalid for the chosen provider is rejected on save. OMIT to leave the STT language unchanged." - changed
Input schema / properties / voice_stt_language / enumPrevious value: -[ - "multi", - "en", - "ru", - "es", - "fr", - "de", - "pt", - "it", - "nl", - "hi", - "ja", - "ko", - "zh", - "th", - "vi", - "id", - "ms", - "tl", - "ar", - "tr", - "uk", - "pl" -]New value: +[ + "af", + "am", + "ar", + "ar-AE", + "ar-DZ", + "ar-EG", + "ar-IQ", + "ar-IR", + "ar-JO", + "ar-KW", + "ar-LB", + "ar-MA", + "ar-PS", + "ar-QA", + "ar-SA", + "ar-SD", + "ar-SY", + "ar-TD", + "ar-TN", + "as", + "ast", + "az", + "ba", + "be", + "bg", + "bn", + "bo", + "br", + "bs", + "ca", + "ceb", + "cs", + "cy", + "da", + "da-DK", + "de", + "de-CH", + "el", + "en", + "en-AU", + "en-GB", + "en-IN", + "en-NZ", + "en-US", + "es", + "es-419", + "et", + "eu", + "fa", + "ff", + "fi", + "fo", + "fr", + "fr-CA", + "fy", + "ga", + "gd", + "gl", + "gu", + "ha", + "haw", + "he", + "hi", + "hr", + "ht", + "hu", + "hy", + "id", + "ig", + "ilo", + "is", + "it", + "ja", + "jv", + "ka", + "kk", + "km", + "kn", + "ko", + "ko-KR", + "la", + "lb", + "lg", + "ln", + "lo", + "lt", + "lv", + "mg", + "mi", + "mk", + "ml", + "mn", + "mo", + "mr", + "ms", + "mt", + "multi", + "my", + "ne", + "nl", + "nl-BE", + "nn", + "no", + "oc", + "or", + "pa", + "pl", + "ps", + "pt", + "pt-BR", + "pt-PT", + "ro", + "ru", + "sa", + "sd", + "si", + "sk", + "sl", + "sn", + "so", + "sq", + "sr", + "ss", + "su", + "sv", + "sv-SE", + "sw", + "ta", + "te", + "tg", + "th", + "th-TH", + "tk", + "tl", + "tn", + "tr", + "tt", + "uk", + "ur", + "uz", + "vi", + "wo", + "xh", + "yi", + "yo", + "zh", + "zh-CN", + "zh-HK", + "zh-Hans", + "zh-Hant", + "zh-TW", + "zu" +] - changed
Input schema / properties / voice_stt_model / descriptionPrevious value: -"Speech-to-text model: 'flux' (alias for flux-general-en), 'flux-general-en' (English Flux, LLM-powered end-of-turn), 'flux-general-multi' (multilingual Flux), or 'nova-3' (silence-based fallback). Flux variants are more responsive; nova-3 is the fallback when your Deepgram plan lacks Flux. OMIT to leave the STT model unchanged."New value: +"Speech-to-text model (Deepgram provider only): 'flux' (alias for flux-general-en), 'flux-general-en' (English Flux, LLM-powered end-of-turn), 'flux-general-multi' (multilingual Flux), or 'nova-3' (silence-based fallback). Flux variants are more responsive; nova-3 is the fallback when your Deepgram plan lacks Flux. Ignored when voice_stt_provider='gladia' (Gladia has a single model). OMIT to leave the STT model unchanged." - added
Input schema / properties / voice_stt_providerAdded value: +{ + "description": "Speech-to-text provider. 'deepgram' (default) runs Nova-3 / Flux and preserves existing behaviour. 'gladia' routes to Gladia streaming STT (solaria-1), which is Deepgram-class latency and covers ~115 languages Deepgram does NOT — including Uzbek ('uz'), Kazakh ('kk'), Azerbaijani ('az'), Tajik ('tg'). Pick 'gladia' when the caller's language is outside Deepgram's coverage, then set voice_stt_language to that language's code. The provider also decides which language codes voice_stt_language accepts. OMIT to leave the STT provider unchanged.", + "enum": [ + "deepgram", + "gladia" + ], + "type": "string" +}
2 tool updates
- Changed
agents_trigger_create2 fields changed- changed
Input schema / properties / trigger_type / descriptionPrevious value: -"Type of trigger: 'incoming_message', 'incoming_call', 'schedule', 'webhook', 'event', 'blockchain_event', 'job_completed', or 'calendar_event'"New value: +"Type of trigger: 'incoming_message', 'incoming_call', 'schedule', 'webhook', 'event', 'blockchain_event', 'job_completed', 'calendar_event', or 'lead_captured'" - changed
Input schema / properties / trigger_type / enumPrevious value: -[ - "incoming_message", - "incoming_call", - "schedule", - "webhook", - "event", - "blockchain_event", - "job_completed", - "calendar_event" -]New value: +[ + "incoming_message", + "incoming_call", + "schedule", + "webhook", + "event", + "blockchain_event", + "job_completed", + "calendar_event", + "lead_captured" +]
- Changed
agents_trigger_update1 field changed- changed
Input schema / properties / trigger_type / enumPrevious value: -[ - "incoming_message", - "incoming_call", - "schedule", - "webhook", - "event", - "blockchain_event", - "job_completed", - "calendar_event" -]New value: +[ + "incoming_message", + "incoming_call", + "schedule", + "webhook", + "event", + "blockchain_event", + "job_completed", + "calendar_event", + "lead_captured" +]
6 tool updates
- Changed
agents_update1 field changed- added
Input schema / properties / default_calendar_idAdded value: +{ + "description": "Default Google calendar_id applied at the TOOL layer whenever this agent calls a calendar tool without an explicit calendar_id (e.g. 'c_...@group.calendar.google.com'). Use for agents whose bookings must always land on one dedicated calendar — a prompt-only rule is advisory and the model occasionally drops the param. An explicit calendar_id in a tool call still wins. Pass an empty string to clear (falls back to 'primary'). OMIT to leave unchanged.", + "type": "string" +}
- Changed
calendar_check_availability2 fields changed- removed
Input schema / properties / calendar_id / defaultRemoved value: -"primary" - changed
Input schema / properties / calendar_id / descriptionPrevious value: -"Calendar ID to check. Defaults to primary calendar."New value: +"Calendar ID to check. OMIT to use the agent's configured default calendar (or primary)."
- Changed
calendar_create_event2 fields changed- removed
Input schema / properties / calendar_id / defaultRemoved value: -"primary" - changed
Input schema / properties / calendar_id / descriptionPrevious value: -"Calendar ID to create event in. Defaults to primary calendar."New value: +"Calendar ID to create the event in. OMIT to use the agent's configured default calendar (or primary)."
- Changed
calendar_delete_event2 fields changed- removed
Input schema / properties / calendar_id / defaultRemoved value: -"primary" - changed
Input schema / properties / calendar_id / descriptionPrevious value: -"Calendar ID containing the event. Defaults to primary."New value: +"Calendar ID containing the event. OMIT to use the agent's configured default calendar (or primary)."
- Changed
calendar_list_events2 fields changed- removed
Input schema / properties / calendar_id / defaultRemoved value: -"primary" - changed
Input schema / properties / calendar_id / descriptionPrevious value: -"Calendar ID to list events from. Defaults to primary calendar."New value: +"Calendar ID to list events from. OMIT to use the agent's configured default calendar (or primary)."
- Changed
calendar_update_event2 fields changed- removed
Input schema / properties / calendar_id / defaultRemoved value: -"primary" - changed
Input schema / properties / calendar_id / descriptionPrevious value: -"Calendar ID containing the event. Defaults to primary."New value: +"Calendar ID containing the event. OMIT to use the agent's configured default calendar (or primary)."
2 tool updates
- Changed
widgets_create1 field changed- added
Input schema / properties / allow_voiceAdded value: +{ + "description": "Master switch for voice — set true to show the mic so visitors can talk to the agent. Everything else voice-related is inert until this is on. The mic also needs a voice-capable agent in the workspace: one with an enabled incoming_call trigger. OMIT to leave voice off (the default).", + "type": "boolean" +}
- Changed
widgets_update3 fields changed- added
Input schema / properties / allow_voiceAdded value: +{ + "description": "Master switch for voice on this widget — set true to show the mic and let visitors talk to the agent. Everything else voice-related (greeting, button label, STT/TTS from the agent's own config) is inert until this is on. The mic also needs a voice-capable agent in the workspace: one with an enabled incoming_call trigger. OMIT to leave the setting unchanged.", + "type": "boolean" +} - added
Input schema / properties / max_voice_duration_secondsAdded value: +{ + "description": "Hard cap on a single voice call from this widget, in seconds (default 300). OMIT to leave the cap unchanged.", + "type": "integer" +} - changed
Input schema / properties / voice_greeting / descriptionPrevious value: -"Spoken opening line when a visitor starts a voice call through this widget. Played via TTS before the AI model runs. Empty string disables the greeting."New value: +"Spoken opening line when a visitor starts a voice call through this widget. Played via TTS before the AI model runs. Empty string disables the greeting. Requires allow_voice=true to be audible."
1 tool update
- Changed
agents_ask1 field changed- changed
Input schema / properties / background / descriptionPrevious value: -"Run detached from this MCP connection. Returns immediately with status='started'; the run survives client timeouts and disconnects (up to 15 min). Poll agents.traces_list for the outcome. Use for runs expected to exceed ~2 minutes — a synchronous call is cancelled when the MCP request dies."New value: +"Run detached from this MCP connection. Returns immediately with status='started'; the run survives client timeouts and disconnects (up to 15 min). Poll agents.traces_list for the outcome. Use for runs expected to exceed ~2 minutes — a synchronous call is cancelled when the MCP request dies. OMIT to run synchronously and get the answer in this call (the default)."
1 tool update
- Changed
agents_ask1 field changed- added
Input schema / properties / backgroundAdded value: +{ + "description": "Run detached from this MCP connection. Returns immediately with status='started'; the run survives client timeouts and disconnects (up to 15 min). Poll agents.traces_list for the outcome. Use for runs expected to exceed ~2 minutes — a synchronous call is cancelled when the MCP request dies.", + "type": "boolean" +}
25 tool updates
- Changed
agents_create1 field changed- changed
Input schema / properties / model / enumPrevious value: -[ - "deepseek-chat", - "deepseek-reasoner", - "gpt-4.1", - "gpt-4.1-mini", - "gpt-4.1-nano", - "gpt-4o", - "claude-haiku-4-5-20251001", - "claude-sonnet-4-6", - "claude-opus-4-6", - "kimi-k2.6" -]New value: +[ + "deepseek-chat", + "deepseek-reasoner", + "gpt-4.1", + "gpt-4.1-mini", + "gpt-4.1-nano", + "gpt-4o", + "claude-haiku-4-5-20251001", + "claude-sonnet-4-6", + "claude-sonnet-5", + "claude-opus-4-6", + "kimi-k2.6" +]
- Changed
agents_update1 field changed- changed
Input schema / properties / model / enumPrevious value: -[ - "deepseek-chat", - "deepseek-reasoner", - "gpt-4.1", - "gpt-4.1-mini", - "gpt-4.1-nano", - "gpt-4o", - "claude-haiku-4-5-20251001", - "claude-sonnet-4-6", - "claude-opus-4-6", - "kimi-k2.6" -]New value: +[ + "deepseek-chat", + "deepseek-reasoner", + "gpt-4.1", + "gpt-4.1-mini", + "gpt-4.1-nano", + "gpt-4o", + "claude-haiku-4-5-20251001", + "claude-sonnet-4-6", + "claude-sonnet-5", + "claude-opus-4-6", + "kimi-k2.6" +]
- Added
browser_attach_identity - Added
browser_attach_meet - Added
browser_click - Added
browser_close - Added
browser_console_messages - Added
browser_drag - Added
browser_evaluate - Added
browser_file_upload - Added
browser_fill - Added
browser_fill_form - Added
browser_handle_dialog - Added
browser_hover - Added
browser_navigate_back - Added
browser_network_requests - Added
browser_open - Added
browser_press_key - Added
browser_resize - Added
browser_select_option - Added
browser_snapshot - Added
browser_tabs - Added
browser_take_screenshot - Added
browser_type - Added
browser_wait_for
23 tool updates
- Removed
browser_attach_identity - Removed
browser_attach_meet - Removed
browser_click - Removed
browser_close - Removed
browser_console_messages - Removed
browser_drag - Removed
browser_evaluate - Removed
browser_file_upload - Removed
browser_fill - Removed
browser_fill_form - Removed
browser_handle_dialog - Removed
browser_hover - Removed
browser_navigate_back - Removed
browser_network_requests - Removed
browser_open - Removed
browser_press_key - Removed
browser_resize - Removed
browser_select_option - Removed
browser_snapshot - Removed
browser_tabs - Removed
browser_take_screenshot - Removed
browser_type - Removed
browser_wait_for
1 tool update
- Changed
integrations_add_endpoints1 field changed- changed
Input schema / properties / name / descriptionPrevious value: -"Display name when creating a new integration (defaults to the host)."New value: +"Display name when creating a new integration. OMIT to default to the host."
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
WhatsApp CRM for AI agents: search contacts, read chats, manage the sales pipeline, send messages.
Phone, SMS & email for AI agents — one remote MCP endpoint, OAuth login, zero install.
AI agent platform: manage leads, conversations, bots, calendar and CRM via MCP.
Run WhatsApp and Telegram AI assistants: projects, prompts, leads, chats, analytics.
Related MCP Servers
- AlicenseBqualityCmaintenanceMCP server for Gmail shared inboxes and WhatsApp — read, reply, search, and organize your team's email from Claude, ChatGPT, or Cursor. 47 tools covering email threads, WhatsApp messaging, boards, contacts, knowledge base, analytics, and automations.471501MIT

SendAPI MCP Serverofficial
AlicenseAqualityBmaintenanceEnables any MCP-compatible AI agent to send WhatsApp messages, SMS, OTP codes, and email through a single REST API.18MIT- AlicenseNot gradedqualityAmaintenanceLets AI agents search and read your personal Telegram and WhatsApp conversations through a self-hosted, read-only MCP server backed by a single SQLite file.AGPL 3.0
- AlicenseNot gradedqualityAmaintenanceMCP server for a local-first messaging workspace that integrates Google Messages, WhatsApp, and Signal. It enables reading, sending, searching messages, and managing conversations through MCP tools.52-
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
Most tools have clearly distinct purposes within their categories, aided by detailed descriptions. However, some overlapping functionalities (e.g., `web_search` vs. `web__local_search`, `agents_ask` vs. `agents_simulate_inbound`) could cause minor confusion for an agent, preventing a perfect score.
The naming convention is predominantly snake_case with a consistent `noun_verb` pattern. However, the use of a double underscore in `web__local_search` (vs. `web_search`) is an outlier that breaks the pattern, and a few verbs are less descriptive (e.g., `process`, `run` are absent here, but the overall pattern is good).
With 165 tools, the server is oversized for a typical MCP server. While the tools are well-organized into domains, the sheer volume overwhelms an agent's ability to efficiently select the right tool, exceeding the recommended 3-15 range by a wide margin.
The tool surface covers a vast range of functionalities including agents, messaging, calls, browser automation, knowledge management, and integrations with LinkedIn, YouTube, and calendars. Minor gaps exist (e.g., no tool for managing YouTube channel settings or advanced web scraping), but the core workflows are well-supported.