Dialpad MCP server
Related Servers
Alternatives to Dialpad MCP server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Claude to search, create, and update contacts, deals, and support tickets in HubSpot, and to generate cross-object account summaries.10MIT
- FlicenseNot gradedqualityDmaintenanceMCP server exposing Dialpad call details, transcripts, and call initiation as tools for use in Claude Desktop and Claude Code.-
- AlicenseAqualityCmaintenanceEnables Claude and other MCP clients to place, transfer, and hang up calls, review call history and dispositions, download recordings, inject single or bulk leads into lists and campaigns, and manage GoHighLevel sub-account services through the VoIPSense Cloud API. Includes a read-only mode and tool annotations so write actions are confirmed appropriately.1317 npmMIT
- AlicenseBqualityCmaintenanceEnables Claude to manage WhatsApp templates, flows, and send messages through the WhatsApp Cloud API.3119 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables Claude to manage GoHighLevel CRM contacts, pipelines, and workflows through natural language commands.115 npmMIT
- FlicenseAqualityCmaintenanceEnables Claude Desktop to access and query RBPaaS Operation Hub data, including business KPIs, project details, resource utilization, and agent schedules.16-
TDQS
Scored across 27 tools
Most tools map cleanly to one resource+action (get_call vs get_call_transcript vs list_calls, create_stats_export vs get_stats_export pairs are obvious). The only soft overlaps are call_subscriptions versus webhooks and get_callcenter vs get_callcenter_status, but the descriptions draw clear lines between them. An agent should rarely misselect here.
Every tool uses the dialpad_ prefix plus a consistent verb_noun snake_case pattern (get_/list_/create_/update_/delete_/send_). Singular vs plural on get vs list matches the resource cardinality and stays predictable throughout.
27 tools is heavy, though the domain (users, offices, departments, call centers, calls, contacts, analytics exports, subscriptions, webhooks, SMS) is genuinely broad so nearly every tool maps to a distinct resource. Still, the surface is large enough that it exceeds a comfortable working set and could be consolidated (e.g. subscriptions/webhooks, callcenter status).
Read coverage across the platform is thorough and contacts get full CRUD plus SMS send and subscription toggling, so core workflows are supported. Gaps remain: no message/text history listing despite SMS sending, no webhook create/delete, no number assignment/management, and no write operations for users/offices/departments/call centers.