Skip to main content
Glama
dialgoodian

clawdcall-mcp

by dialgoodian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to clawdcall-mcp

No user-submitted related servers found.

    Related Servers

    • ClawCall MCP Server by ClawCall-Dev

      ClawCall MCP Serverofficial

      ClawCall-Dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to make real outbound phone calls to US/Canada numbers, handle conversations, and return transcripts and recordings via the Model Context Protocol.
      7
      MIT

    • agentline-mcp

      jgottlieb84
      A
      license
      A
      quality
      C
      maintenance
      Gives AI agents phone numbers, email, SMS, and voice calls as MCP tools, enabling them to provision numbers, capture 2FA codes, send messages, and make calls.
      15
      MIT

    • Twilio MCP Server

      projectservan8n
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with all Twilio APIs through the Model Context Protocol. Supports SMS, voice, messaging, and other Twilio services with secure authentication and configurable API filtering.
      -

    • Lark MCP Server

      junyuan-qi
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI models to send messages to Lark users and manage calendar events (list, create, add attendees) through the Model Context Protocol.
      18 npm
      6
      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.9/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: two are sequential OTP signup steps, one places a call, and one fetches a transcript. There is no real overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: send_, verify_, place_, get_. The naming style is uniform and predictable.

    Tool Count5/5

    Four tools is a well-scoped count for a focused server. Each tool earns its place in the signup-and-call workflow without unnecessary bloat or thinness.

    Completeness4/5

    The signup OTP flow, outbound call placement, and transcript retrieval form a coherent end-to-end workflow. Minor gaps exist, such as call status, cancellation, or listing, but agents can work around them for the core use case.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources