Skip to main content
Glama
burkecampbell

twilio-call-data-mcp

by burkecampbell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to twilio-call-data-mcp

No user-submitted related servers found.

    Related Servers

    • airspeed-mcp

      josh-sea
      F
      license
      Not graded
      quality
      D
      maintenance
      Remote MCP server that exposes Airspeed/Glyphic call data to Claude web, enabling tools to list, retrieve, and query calls, transcripts, snippets, and playbooks.
      -

    • aircall-mcp

      growth-box
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for the Aircall REST API, enabling browsing calls, transcripts, contacts, and more while keeping data local.
      21
      MIT

    • Twilio MCP Server by CData

      CDataSoftware
      A
      license
      Not graded
      quality
      D
      maintenance
      This read-only MCP Server allows you to connect to Twilio data from Claude Desktop through CData JDBC Drivers. Free (beta) read/write servers available at https://www.cdata.com/solutions/mcp
      1
      MIT

    • chatwoot-mcp

      md-riaz
      A
      license
      Not graded
      quality
      C
      maintenance
      Local Node/TypeScript MCP server for read-only Chatwoot analytics, providing tools to list accounts, scopes, cache sync status, and conversation volume metrics.
      268 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: searching calls, getting call detail, retrieving recording metadata, listing agents, getting agent activity, and aggregating summaries. There is no overlap between tools; even the two agent-related tools are clearly separated by current status versus historical activity.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun pattern (search_calls, get_call, get_recording, list_agents, get_agent_activity). The one outlier is call_summary, which drops the verb and uses a noun phrase instead of something like summarize_calls. This is a minor deviation that does not impede readability.

    Tool Count5/5

    Six tools is within the ideal 3-15 range and each tool serves a clear purpose in the call data exploration and analytics domain. The count feels well-scoped without being bloated or too thin.

    Completeness5/5

    The tool set covers the full read-only lifecycle for Twilio call data: search, retrieve details, retrieve recordings, list agents, retrieve agent activity, and generate summaries. There are no obvious gaps for the stated purpose of analyzing call data; the domain is fully represented.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources